UPU-IP API Documentation
The Web Service Interface is exposed to business partners to allow them to exchange postal payment related messages via the UPU Interconnection Platform (UPU-IP). Business partners are organizations that use a national system and wish to connect this system to the UPU-IP by developing a WS client.
External payment networks, non-designated operators (DOs), money transfer operators, etc. can also exchange payment messages through the UPU-IP.
Security - Message Level Security
The UPU-IP API is secured using Message Level Security (MLS). Security credentials and claims are encapsulated with every message providing end-to-end security independent of the transport protocol.
Web service request and response messages to and from the UPU-IP are digitally signed and encrypted. By using x.509 certificates, authenticity is ensured while the use of digital signatures at the application level ensures the non-repudiation of messages. MLS also has the advantage that the message may be routed through intermediary systems without loss of security.
Web Service endpoint (MLS)
Web Service endpoint exposes WSDL file to generate a Web Service proxy client.
Web Service endpoint at the URL: http://hubws.ptc.post/ExternalService.svc
The URL above is the current production environment endpoint. The URL for test environment endpoint is: http://hubws.preprod.upu.org/ExternalService.svc
Security - Transport Level Security
Transport Level Security (TLS) is an evolved version of Secure Socket Layer (SSL). Using x.509 certificate, TLS ensures end-to-end security of data sent between applications, avoiding possible eavesdropping or alteration of the content being transported.
Web Service endpoint (TLS)
Web Service endpoint exposes WSDL file to generate a Web Service proxy client.
Web Service endpoint at the URL: https://hubws-tls.ptc.post/ExternalService.svc
The URL above is the current production environment endpoint. The URL for test environment endpoint is: https://hubws-tls.preprod.upu.org/ExternalService.svc