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. Addressing & Proxy Resolution

Proxy & Account Resolution Process

PreviousExamplesNextStep 1: Sender inputs proxy or account details

Last updated 8 months ago

Note: Support for ISO 20022 acmt.023 and acmt.024

Nexus uses the ISO 20022 messages and for all communication related to proxy resolution or account resolution.

The remainder of this guide assumes that the IPS operator, proxy directory and member PSPs can support the acmt.023 & acmt.024 messages according to the Nexus usage guidelines. However, this is not the case in many countries.

IPSOs that do not currently support acmt.023 andacmt.024 must either:

  • translate these messages to the relevant domestic format, or

  • adapt their systems (including the proxy directory, and the systems of their member PSPs) to support these messages.

These options and the translation process are described in .

Simple Overview

The diagram below shows the proxy and account resolution process at a high level.

(The user experience in the app is shown in more detail (with visual examples) in Payment Setup).

Figure: Proxy & Account Resolution Flow Diagram (Simple Overview)

  1. A Sender can enter either the Recipient’s proxy ID or account ID into their PSP’s app

  2. The Source PSP will send this information to Nexus

  3. If the Sender provided a proxy, Nexus will connect to the relevant proxy directory and request the corresponding account details

    1. The proxy directory will return the corresponding account details.

  4. If either (a) the Sender provided an account ID, or (b) the proxy resolution response from the Proxy Directory includes the account ID, Nexus will:

    1. Check if the Destination PSP is able to accept account resolution requests.

      1. If so, Nexus will send an account resolution request to the Destination PSP

  5. Nexus will combine the information from the proxy directory and the Destination PSP (if an account resolution request was sent), and send this back to the Source PSP

  6. The Source PSP will check the information in the response:

    1. If a Display Name was provided, the Source PSP will ask the Sender to confirm that the payee is who they expect

    2. If no Display Name is provided, the Sender will be advised to proceed with the payment at their own risk

    3. If no other information is provided (such as the full name on the account), then the Source PSP will need to ask the Sender to provide this information so that the Source PSP can perform compliance and sanctions screening checks on the Recipient.

The rest of this section covers those steps in more detail.

acmt.023
acmt.024
Messaging & Translation
High level flow diagram showing the proxy and account resolution process in Nexus