BIS Innovation Hub
Nexus - Short ReportAbout the BIS Innovation Hub
  • Introduction
    • Nexus Overview
    • How to use this site
    • Overview Report
    • Terminology
  • Payment Setup
    • Key Points
    • Scope of Nexus payments
    • Steps 1-2: Country, Currency & Amount
    • Steps 3-6: Exchange Rates
    • Steps 7-9: Addressing, Proxy Resolution & Confirmation of Payee
    • Steps 10-11: Sanctions screening
    • Step 12: Ask the Sender for approval
    • Step 13-16: Set up and send the payment instruction
    • Step 17: Accept the confirmation and notify Sender
  • Addressing & Proxy Resolution
    • Key Points
    • Overview of Payment Addressing in Nexus
      • Addressing via Proxies (Aliases)
      • Addressing via Account Details
    • Address Types & Inputs
      • Address Types
      • Address Inputs
      • Financial Institution Identification
      • List of PSPs
      • Examples
    • Proxy & Account Resolution Process
      • Step 1: Sender inputs proxy or account details
      • Step 2: Proxy Resolution Messaging Sequence
      • Step 3: Account Resolution Messaging Sequence
      • Step 4: Source PSP processes the results
      • Masking of Display Names
    • Role of the Proxy Directory Operator (PDO)
      • Obligations on the Proxy Directory Operator
      • Obligations of PSPs using the Proxy Directory
      • Onboarding a Proxy Directory Operator onto Nexus
  • FX Provision
    • Key Points
    • Role of the FX Provider
    • How Third-Party FX provision works in Nexus
    • Joining Nexus as a third-party FXP
    • Accessing Instant Payment Systems
    • Onboarding PSPs
    • Obligations & Compliance
    • Revenue model for FXPs
    • Rates from Third-Party FX Providers
      • Improving rates for larger transactions
      • Improving rates for specific PSPs
    • Quotes
    • Managing Liquidity
  • Payment Processing
    • Key Points
    • Accounts & Relationships
    • Maximum value of a Nexus payment
    • Payment Flow (Happy Path)
      • Detailed Flow in Source Country (Sending)
      • Detailed Flow in Destination Country (Receiving)
      • Booking flow for Source PSPs
      • Notifying FXPs of completed payments
    • Validations, Duplicates & Fraud
    • Time critical vs non-time critical payments
    • Special Scenarios
    • Payment setup for PSPs who provide their own FX
    • Unsuccessful Payments (Exceptions)
      • Rejects
      • Recall Requests
      • Returns
      • Investigation & Enquiry
      • Disputes
      • Reconciliation reports
    • Fees
    • Role and responsibilities of the Instant Payment System Operator (IPSO)
    • Ensuring settlement certainty
    • Annex: 4-step vs 5-step Processes in Domestic Clearing and Settlement
    • Annex: Sponsoring PSPs and Sponsored Entities
  • Settlement Access Provision
    • Key Points
    • Role of the Settlement Access Provider (SAP)
    • Joining Nexus as an SAP
    • SAP onboarding of FXPs (or foreign PSPs)
    • Costs and Revenue for SAPs
    • Obligations on the SAP
    • Processing payments as an SAP
      • Payment Process for the Source SAP
      • Payment Process for the Destination SAP
      • How the Destination IPS initiates the payment via the Destination SAP
    • Managing Liquidity as an SAP
  • Messaging & Translation
    • Key Points
    • General Usage of ISO 20022
      • Adherence to CPMI Harmonised ISO 20022 Data Requirements
    • Compatibility with Instant Payments Plus (IP+)
    • Message transformation by Nexus
    • Specific Message Elements
    • Purpose Codes
    • Message Guidelines (Excel)
    • MESSAGE acmt.023 Identification Verification Request
    • MESSAGE acmt.024 Identification Verification Report
    • MESSAGE: pacs.008 FI to FI Customer Credit Transfer
      • pacs.008 Differences from CPMI Harmonisation Requirements
    • MESSAGE pacs.002 Payment Status Report
      • pacs.002 Differences from CPMI/CBPR+ Guidelines
    • MESSAGE: pacs.004 Payment Return (Not yet supported)
    • MESSAGE: camt.054 Bank to Customer Debit Credit Notification
    • Translation To/From Domestic Message Formats
    • Translating To/From ISO 20022 Codes
  • APIs
    • Overview
    • Countries
    • Currencies
    • Address Types and Inputs
    • Financial Institutions
    • Fees and Amounts
    • Intermediary Agents (SAPs)
    • Quotes
    • ISO 20022 Messages
  • About
    • Contact the Nexus Team
  • LEGAL
    • Terms and Conditions of Use
    • Privacy Notice
    • Cookies Notice
Powered by GitBook
On this page
Export as PDF
  1. APIs

ISO 20022 Messages

PreviousQuotesNextContact the Nexus Team

Last updated 1 month ago

ISO 20022 messages are submitted to Nexus via asynchronous API.

The ISO 20022 XML message itself will be included in full in the message body.

The Source IPSO will also define an endpoint to which Nexus should send the resulting response (ie when submitting acmt.023, the Source IPSO must also define the acmt024Endpoint to which Nexus should send the acmt.024 response).

  • POSTSubmit ISO 20022 acmt.023 message (Proxy or Account Resolution Request)
  • POSTSubmit ISO 20022 pacs.008 message (FI to FI Customer Credit Transfer - the core Nexus payment instruction)

Submit ISO 20022 acmt.023 message (Proxy or Account Resolution Request)

post

This endpoint accepts an ISO 20022 acmt.023 message in XML format. The message must be prepared according to the Nexus Message Usage Guidelines.

Query parameters
acmt024Endpointstring · uriRequired

An API URL exposed by the Source IPSO where the acmt.024 response (which contains underlying account details) should be sent.

Body
stringOptionalExample: [Full XML of the acmt.023 request]
Responses
200
Successful response
application/xml
ResponsestringExample: [Full XML of the acmt.024 response]
post
POST /iso20022/acmt023 HTTP/1.1
Host: localhost:3000
Content-Type: application/xml
Accept: */*
Content-Length: 36

"[Full XML of the acmt.023 request]"
200

Successful response

<?xml version="1.0"?>
<object>[Full XML of the acmt.024 response]</object>

Submit ISO 20022 pacs.008 message (FI to FI Customer Credit Transfer - the core Nexus payment instruction)

post

This endpoint accepts an ISO 20022 pacs.008 message in XML format. The message must be prepared according to the Nexus Message Usage Guidelines.

Query parameters
pacs002Endpointstring · uriRequired

An API endpoint exposed by the Source IPSO where the pacs.002 response (Payment Status Report) should be sent.

Body
stringOptionalExample: [Full XML of the pacs.008 request]
Responses
200
Successful response
application/xml
ResponsestringExample: [Full XML of the pacs.002 response]
post
POST /iso20022/pacs008 HTTP/1.1
Host: localhost:3000
Content-Type: application/xml
Accept: */*
Content-Length: 36

"[Full XML of the pacs.008 request]"
200

Successful response

<?xml version="1.0"?>
<object>[Full XML of the pacs.002 response]</object>