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
  2. Overview of Payment Addressing in Nexus

Addressing via Proxies (Aliases)

In many countries with instant payment systems (IPSs), payments can be addressed using “proxies” (or “aliases") in place of Account Identifications. A proxy (or alias) is any string of text that can be linked to a specific bank account. Commonly accepted proxies include:

  • Mobile phone numbers

  • Email addresses

  • National ID numbers

  • Company incorporation numbers

Nexus allows cross-border payments to be addressed using proxies. In principle, any proxy that is valid for domestic payments should also be valid for Nexus payments. (This is dependent on the relevant proxy service provider being onboarded and connected to Nexus.)

This guide assumes that each Instant Payment System has one – and only one – corresponding proxy directory. This is the case in most countries. However, in the euro area and the USA there may be multiple IPSs and multiple (often competing) proxy directories. This raises a number of complications that will be addressed in a future phase of development.

Different countries support different types of proxies. The table below shows some examples.

Explainer: Example proxy schemes

COUNTRY

PROXY SCHEME

PROXIES

NOTES

Australia

PayId

  • Phone number

  • Email

  • Registered business number

Addressing service provided by IPS operator (the New Payments Platform).

India

Unified Payments Interface (UPI)

  • Mobile number

  • Virtual Payment Address (UPI ID),

  • Aadhaar ID (non-mandatory national identity number)

UPI ID has the format name@BankName or mobilenumber@BankName. Only the bank is able to map the name element to a specific account; the IPS operator does not have this information.

Indonesia

BI-FAST

  • Mobile Number

  • Email Address

Malaysia

DuitNow

  • Mobile phone number

  • Business registration number

  • National ID number

  • Passport Number

  • Army Number / Police Number

The majority of account holders have linked their phone number to an account.

Philippines

InstaPay

  • Mobile Number

  • Email Address

Singapore

PayNow

  • Mobile phone number

  • Unique Entity Number for corporations

  • National ID number

  • Virtual payment address

Significant adoption. Also used for payments from individuals to smaller businesses and some larger e-commerce sites (eg Shopee)

Sweden

Swish

  • Mobile phone number

High adoption: the majority of Swedish adults are registered with Swish

Thailand

PromptPay

  • Mobile Number

  • National ID

  • Biller Id

  • Corporate Tax Id

  • Ewallet ID

UK

PayM

  • Mobile phone number

Service was shut down in March 2023 due to poor adoption

PreviousOverview of Payment Addressing in NexusNextAddressing via Account Details

Last updated 10 months ago