Use-Cases
Step-by-step integration flows for common RTGS.global API tasks.
Approve an incoming relationship request from another participant on the RTGS.global network.
📦How to parse the CloudEvent envelope, base64-decode the `data_base64` field, and deserialize the RTGS.global message payload into your domain model. Run this after both signatures have been verified.
📋Check whether the target funds controller requires creditor party management, then register a creditor.
📋Check whether the target funds controller requires debtor party management, then register a debtor.
🤝Step-by-step guide to requesting a new relationship with another participant on the RTGS.global network.
💱Request an FX quote from a counterparty, then respond with a quote offer. Covers both sides of the flow.
🏦Retrieve the accounts associated with your participant, including their status, currency, and linked funds controller.
💰Retrieve the available balances of network accounts across all jurisdictions.
👥Retrieve the list of registered creditors for a given funds controller.
👥Retrieve the list of registered debtors for a given funds controller.
📊Retrieve transactions for an account, optionally filtered by date range.
💸Optionally validate, then submit a FI to FI Customer Credit Transfer (pacs.008) for settlement via the RTGS.global network.
🔗Submit a Link and Settle instruction to link and settle a payment across two RTGS.global participants.
❌Reject an incoming relationship request from another participant on the RTGS.global network.
🔏How to sign an outgoing request using the Signing API and verify the response signature.
✅How to verify the RTGS.global digital signature (`verificationmaterial`) on an incoming CloudEvent webhook. This confirms the message was genuinely produced by RTGS.global and that the payload has not been tampered with.
🔒How to verify the Svix HMAC-SHA256 delivery signature on an incoming webhook to confirm the request genuinely came from RTGS.global delivery infrastructure and is not a replay.