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
  • Benefits of using proxies instead of account details
  • Where proxy services are unavailable
Export as PDF
  1. Addressing & Proxy Resolution

Overview of Payment Addressing in Nexus

Nexus allows payments to be addressed using any details that are valid in the Recipient’s country. These could include:

  • International Bank Account Numbers (IBAN) (where used)

  • Account Identification (account numbers) alongside a Financial Institution Identification (such as BIC or a non-BIC Clearing System Member Id)

  • Proxies such as mobile phone number, email address or company registration number.

Nexus maintains a record of which payment address types are available in each country and provides this information to PSPs through the GET /countries/{countryCode}/addressTypes API operation.

Nexus will not provide its own proxy service or proxy format; users cannot register with Nexus to create a global “Nexus ID’.

Nexus does not maintain its own directory of proxies and associated accounts.

Benefits of using proxies instead of account details

Proxies are the preferred way to address Nexus payments, as they are more user friendly and easier to enter on a mobile device. But Nexus will always support IBAN (where accepted) and Account Identifiers as well.

For Senders and Recipients of Nexus payments, the use of proxies improves the user experience:

  • Easier to share details: It is usually easier for the Recipient to share (for example) a phone number or email address than either (a) a Financial Institution Identification and Account Identification, or (b) an International Bank Account Number (which can be 20-32 characters).

  • Reduces sharing of sensitive data: A payment can be addressed to the Recipient without the Recipient having to share sensitive personal details, such as their home address, or reveal where they hold their accounts.

  • Provides confirmation of payee: Proxy directories typically provide some way of confirming the identity of the payee, for example, by returning the real verified name of the account holder (as provided by the account holder’s PSP). This helps to give the Sender confidence that they are sending funds to the correct account, as well providing a defence against fraud.

Where proxy services are unavailable

Proxy directories are not available in all countries or payment communities. Whether or not a proxy service is available, Nexus still allows payments to be addressed using IBAN (where accepted) and/or Account Identifications.

A country that does not have a proxy directory domestically is still permitted to send Nexus payments using the proxies available in the Destination Country.

PreviousKey PointsNextAddressing via Proxies (Aliases)

Last updated 8 months ago