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. Payment Processing
  2. Payment Flow (Happy Path)

Detailed Flow in Destination Country (Receiving)

PreviousDetailed Flow in Source Country (Sending)NextBooking flow for Source PSPs

Last updated 8 months ago

The Destination Country processing flow is shown below:

The Destination Country payment process follows the following steps:

1

The Destination Nexus Gateway sends the Nexus pacs.008 to the Destination IPS.

The Destination IPS may need to convert this message into its local format before forwarding this to the Destination SAP.

No reservations need to be made at this stage.

2

The Destination IPS sends the payment instruction to the Destination SAP

The IPS is free to decide on the format of the payment message for the interaction towards the D-SAP and the D-PSP.

If ISO 20022 is not used domestically, the IPS will need to translate from the Nexus pacs.008 to the domestic payment instruction format.

3

The Destination SAP confirms that the FX Provider has sufficient funds with them, and applies sanctions screening and compliance checks if required.

If the Destination SAP is happy to proceed with the payment, it will debit the FXP’s account with them by the amount of the payment. If the Destination SAP is not able to validate the payment, the Destination SAP can reject the transaction.

The D-SAP either submits the payment instruction message to the Destination IPS, effectively giving the IPS the instruction to make payment to the Destination PSP or rejects the transaction.

4

5

The Destination IPS forwards the payment message to the Destination PSP for validation.

6

The Destination PSP will apply sanctions screening and compliance checks before deciding whether to accept the payment.

If the Destination PSP is happy to accept the payment they will then return a payment status message accepting the payment instruction.

7

8

5-step settlement only In case of a confirmation and successful settlement, the D-IPS will confirm settlement to the Destination PSP.

9

In case of a confirmation and successful settlement, the D-IPS will confirm settlement to the Destination SAP.

10

The Destination PSP credits the Creditor Account. The D-PSP should inform the Creditor of the arrival of funds, according to the local scheme requirements.

11

In case of a confirmation and successful settlement, the D-IPS will confirm settlement to the Destination Nexus Gateway.

The Destination IPS, upon receiving the validated instruction from the Destination SAP, either settles the transaction () or ensures settlement (by reserving the pre-funded balance of the Destination PSP or otherwise in a 5-step settlement process).

See also

only Upon confirmation of the Destination PSP, the D-IPS will settle the transaction.

The Destination IPS must use the Nexus pacs.002 payment status report format to confirm the transaction to the Nexus Gateway. See for details on the format.

Time critical vs non-time critical payments
Messaging & Translation
4-step settlement process
5-step settlement
Destination Country processing flow (Receiving)