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 Setup

Scope of Nexus payments

PreviousKey PointsNextSteps 1-2: Country, Currency & Amount

Last updated 7 months ago

Nexus supports account-to-account payments between individuals (known as person-to-person (P2P) and consumer-to-consumer (C2C)) and businesses (B2B), or between individuals and businesses (P2B, B2P). These payments are initiated by the sender entering a proxy, such as a mobile number, or account details into the app of the Sender's PSP.

This guide does not yet cover payments that are initiated by scanning a QR code, including:

  • proxy payments, where the proxy is embedded in a QR code

  • “merchant payments”, eg payments from a customer to a retailer or other business, using dynamic QR codes at the point of sale (either physical or e-commerce).

These features will be added to Nexus in due course.

Nexus currently supports Single Instant Cross-Border Cross-Currency Payments:

“Single payment”

Nexus supports single payments only. A pacs.008 payment instruction message sent to Nexus must only contain a single transaction. Nexus will process each payment individually and PSPs will accept/reject each Nexus payment individually.

Nexus does not accept bulk/batch payment instructions. However, it is acceptable for a PSP to receive a bulk/batch payment file from its customers (or for an IPS to receive a bulk/batch payment file from its PSPs), “debulk” the file and submit the payments one-by-one as individual payments through Nexus. The Nexus Scheme Rulebook requirements will apply for these payments in full including requirements regarding transparency of fees, timelines and compliance checks. It will be the responsibility of the Source PSP (or IPS) to correlate the individual transactions (and their responses) back to the original batch/bulk file, if required.

“Instant”

Nexus processes instant payments. A domestic instant payment is defined as a payment executed end-to-end, where the funds being transferred from the account of a Sender are made available in the account of the Recipient, irrevocably, within seconds (typically within 20 seconds).

Nexus has the ability to support both time-critical and non-time-critical account-to-account payments:

  • Time-critical payments include urgent payments and point-of-sale payments (eg where the Sender is standing at the till or sat in a taxi, waiting for a payment to complete before they can leave).

  • Non-time critical payments are those payments where it is acceptable for the payment to be slightly delayed in the case that the alerts generated by compliance checks and sanctions screening cannot be resolved instantly.

Whether a payment is time-critical or non-time critical is defined in the payment message.

“Cross-Border, Cross-Currency” Nexus is designed for instant payments requiring a currency conversion, using an FX Provider. See FX Provision.

Nexus does not currently support payments to and from the same currency (even if they are in different countries)

pacs.008