Skip to main content

API and Event Messaging

The RTGS.global platform is an ISO 20022 and FIX Standard compatible API and event-based model. ISO 20022 and FIX Standard formats and messaging are used as much as possible across the platform, but in instances where messaging standards do not cater for RTGS.global product services, the below standards are followed:

  1. Accepted conventions relating to RESTful APIs and HTTP webhooks are adhered to
  2. Payloads are in JSON format and follow the appropriate ISO 20022 or FIX Standard message, where possible
  3. If there is no suitable ISO 20022 or FIX Standard message, the relevant data dictionary is used for all values in the payload or query string, where possible

Instances where platform messaging diverges from messaging standards are outlined below. Where the format is aligned, the structure, hierarchy, and field parameters of the platform message follow the ISO or FIX message exactly.

FeatureFunctionMessageTypeCompatibility
FX QuotesQuote RequestAPI Request Body / Event35 = RUses a subset of required fields
FX QuotesQuoteAPI Request Body / Event35 = SUses a subset of required fields
FX QuotesNew Order SingleAPI Request Body / Event35 = DUses a subset of required fields
FX QuotesExecution ReportAPI Request Body / Event35 = 8Uses a subset of required fields
Link & SettleInitiateAPI Request BodyProprietaryUses parts of the pacs.009 message format; some required fields are outside of the ISO 20022 data dictionary; only one transaction is accepted per request (CreditTransferTransactionInformation is [1..1])
Link & SettleCancelAPI Request BodyProprietaryAll fields are taken from the ISO data dictionary, except LinkIdentifiers
Link & SettleStatus UpdateEventpacs.002Message format aligned to ISO 20022
Link & SettleNotification of Cr/DrEventcamt.054Message format aligned to ISO 20022
FI to FI Customer Credit TransferInitiateAPI Request Bodypacs.008Only one transaction is accepted per request (CreditTransferTransactionInformation is [1..1])
FI to FI Customer Credit TransferValidateAPI Request Bodypacs.008Only one transaction is accepted per request (CreditTransferTransactionInformation is [1..1])
FI to FI Customer Credit TransferStatus UpdateEventpacs.002Message format aligned to ISO 20022
FI to FI Customer Credit TransferFI to FI Customer Transfer RequestEventpacs.008Only one transaction is accepted per request (CreditTransferTransactionInformation is [1..1])
FI to FI Customer Credit TransferNotification of Cr/DrEventcamt.054Message format aligned to ISO 20022
Payment Status ReportInitiateAPI Request Bodypacs.002Message format aligned to ISO 20022
Payment Status ReportReceiveEventpacs.002Message format aligned to ISO 20022
Get BalancesRequestRESTful HTTP APIQuery string parameters are taken from the ISO 20022 data dictionary
Get BalancesResponseRESTful HTTP APIcamt.052Message format aligned to ISO 20022
Get TransactionsRequestRESTful HTTP APIQuery string parameters are taken from the ISO 20022 data dictionary
Get TransactionsResponseRESTful HTTP APIcamt.006Message format aligned to ISO 20022
Get AccountsRequestRESTful HTTP APIQuery string parameters are taken from the ISO 20022 data dictionary
Get AccountsResponseRESTful HTTP APIProprietarySynchronous response parameters are taken from the ISO 20022 data dictionary
Get ParticipantsRequestRESTful HTTP APIQuery string parameters are taken from the ISO 20022 data dictionary
Get ParticipantsResponseRESTful HTTP APIProprietarySynchronous response parameters are taken from the ISO 20022 data dictionary
Get RelationshipsRequestRESTful HTTP APIQuery string parameters are taken from the ISO 20022 data dictionary
Get RelationshipsResponseRESTful HTTP APIProprietarySynchronous response parameters are taken from the ISO 20022 data dictionary
FundsDefundAPI Request Bodypacs.009Only one transaction is accepted per request
FundsStatus UpdateEventpacs.002Message format aligned to ISO 20022
FundsNotification of DebitEventcamt.054Message format aligned to ISO 20022

At Least Once Delivery

The RTGS.global Gateway provides durable delivery and guarantees at least once message delivery. This should be considered when integrating with the Gateway. Participants should use patterns such as idempotent consumers, the inbox pattern, or simple deduplication within the consumer.

To support these patterns, all messages delivered from the RTGS.global Gateway include an ISO 20022 GroupHeader with an accompanying message identifier. This identifier should be used for deduplication.