Go to top of page

Build your B2G interface

To interact with the PPSR using the B2G channel you need to develop your own unique client interface.

Before building your system see the B2G interface versioning page and then select the relevant versioning documents for the technical specifications. You need to implement:

  • namespaces
  • endpoints
  • fault codes
  • date and time considerations
  • change B2G password.

Simple Object Access Protocol (SOAP)

PPSR uses SOAP to provide request/response message exchanges between PPSR and client systems. The PPSR B2G channel uses SOAP 1.1, SOAP 1.2 and SOAP HTTP binding.

Services that involve sending or receiving files can use the SOAP Message Transmission Optimisation Mechanism (MTOM).

SOAP also provides for the XML-based exchange of structured information between systems. The W3C SOAP online manual provides all the information about SOAP.


Transport layer security (TLS) is the only supported protocol between the PPSR B2G servers and your B2G servers. TLS is used to encrypt all PPSR messages because you cannot use your client certificate for authentication.

Web Service Description Language

All messages you send to the PPSR need to comply with the Web Service Description Language (WSDL). WSDL is used by many development tools to generate code for web services.

Technical support

The National Service Centre (NSC) can help with technical assistance but does not provide support for interface development. See contact us.

Request access to Discovery

Discovery is a replica of the PPSR. You can use it to test all the functions you needed for your B2G interface. Go to Request B2G access for Discovery