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. FX Provision

Onboarding PSPs

PreviousAccessing Instant Payment SystemsNextObligations & Compliance

Last updated 8 months ago

This page relates only to third-party FX Providers.

For Source PSPs that provide their own FX, a different process applies. See Payment setup for PSPs who provide their own FX for details.

For a specific Nexus payment, the FXP is effectively trading with the Source PSP by selling them the Destination Currency. This means the Source PSP is a corporate customer of the FXP. The FXP therefore has a regulatory obligation to complete due diligence (Know Your Business, KYB) on a PSP before it provides FX conversion to that PSP.

Once the FXP has completed due diligence on a PSP, it must inform Nexus (via the Nexus administration portal or Nexus APIs) that it is willing to provide FX to that PSP.

When generating quotes in response to the GET /quotes/ API, Nexus will only provide quotes from the FXPs that have approved the PSP.

Streamlining the PSP onboarding process

FXPs must accept the Wolfsberg (CBBDQ) from PSPs.

The Wolfsberg CBDDQ is a standardised questionnaire that can be used for due diligence by FXPs on PSPs (and by SAPs on FXPs). It ensures that a PSP only needs to complete the questionnaire once (and keep it up to date), rather than dealing with a bespoke application form for every FXP. From the FXP's side, the questionnaire ensures that each PSP provides the same information in a consistent structure.

Streamlining the PSP onboarding process in this way is important to ensure the FX market in Nexus is competitive. It is best if each PSP in an IPS is onboarded with each of the FXPs that provide FX in the PSP’s home currency. This means a PSP may wish to apply to be onboarded with multiple FXPs, and each FXP may wish to onboard multiple PSPs.

If every FXP imposes a different KYC/KYB process upon PSPs, the cost to a PSP of onboarding with an FXP would be higher, which could:

  • discourage FXPs from onboarding smaller PSPs as the benefits of doing so (potential additional payment flows) may not outweigh the costs of the due diligence process;

  • discourage PSPs from onboarding with multiple FXPs, as the benefit of doing so (more competitive rates) may not outweigh the costs of onboarding with additional FXPs.

Mandatory use of the Wolfsberg CBDDQ will help to streamline this process.

As Nexus scales, other ways to streamline the PSP-FXP onboarding and due diligence process will be explored, including possible digitalization of the process for a PSP to apply to onboard with an FXP. This may include the possibility of a repository for relevant information (such as the Wolfsberg Questionnaire and relevant evidence such as incorporation certificates) that can be accessed (with the PSP’s permission) by FXPs.

Correspondent Banking Due Diligence Questionnaire