Getting Connected
Connect to the RTGS.global network by deploying components from the Microsoft Azure marketplace
Key Component Overview
Every participant is required to have an active connection through their local jurisdiction. Participant connectivity is handled by two key components:
Network Connector
The network connector is a deployment package that sets up the required VNet peering between the Participant Gateway and RTGS.global as a secure connection.
Participant Gateway
The Participant Gateway provides API endpoints and event notification hooks.
You can connect via:
Gateway Emulator allows you to try out and get experience of our API and responses, before the Integration phase of onboarding. The RTGS.global emulator APIs are provided in a Docker image which can be run on a host environment of your choice.
For access to our Sandbox and Production environments, you need to host your own gateway through an active azure subscription. For more information on deploying the required components, see advanced deployment.
Last updated
