VPN Integration

For gateways hosted on AWS, GCP, on-premise, or other non-Azure environments, the integration journey has four stages:

1. Register

A contact in your organisation will have provided your organisation's details to the RTGS.global onboarding team. This includes information such as your legal entity name and the geographical region your organisation will connect to.

2. Connect

You will need to create a VPN client to route traffic to RTGS.global's VPN server. You must also host a containerised digital signatures module (RTGS.global Signing) to create and verify signatures. See Deployment.

3. Integrate

Integration is achieved by extending your organisation's systems to consume the RESTful APIs and asynchronous CloudEvents exposed by the RTGS.global API. See Integrating with the RTGS.global API.

4. Technical Certification

All integration steps are first completed in the RTGS.global sandbox environment. Once RTGS.global confirms that all functional and non-functional requirements have been met via an approved test exit report, the integration is technically certified. This certification is a dependency for the onboarding team to plan your switch to the production network.