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
  • Compliance
  • Sanctions screening
  • Minimum commitment
  • Market maker role
Export as PDF
  1. FX Provision

Obligations & Compliance

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.

The Nexus Scheme Rulebook provides detailed obligations for FX Providers. At a high level, these obligations include:

Compliance

FX Providers must comply with all applicable regulations in the jurisdiction they are based in, as well as any applicable regulations in the jurisdiction to which they are providing FX.

Sanctions screening

Unless otherwise required by a specific country’s regulatory regime, a third-party FXP is not obliged to perform sanctions screening on individual Nexus payments. The FXP’s counterparty is the Source PSP to whom they sell the Destination Currency, and the FXP does not deal with (or have information on) the Sender or Recipient.

However, when an FXP is a member of an IPS and therefore acts as SAP to themselves, the entity is responsible for screening the payment against applicable sanctions lists in their role as SAP, subject to local regulations. (See Settlement Access Provision.)

Minimum commitment

FXPs must commit to providing FX to Nexus for a certain minimum duration (to be specified in the Nexus Scheme Rulebook) and must give a period of notice if they wish to stop providing FX.

FXPs may choose to permanently withdraw from providing FX to Nexus.

The Nexus Scheme Rulebook defines the process and minimum notice period for withdrawing from the scheme.

Market maker role

In general, FX Providers are expected to play a similar role to that of a market maker; this means that they are expected to always provide a quote for the payment corridors that they provide. If they do not wish to be committed for new payments, they may set a quote that is below the rest of the market, but they should not “exit the market” by providing no quote at all.

This expectation is necessary to ensure that there is always liquidity available for Nexus payments and to avoid a situation where all FX Providers for a currency channel choose to “sit out” of the market (making payments through that channel impossible). The obligation to always quote also helps to ensure that FX rates will be dynamic and are likely to be broadly in line with other FX markets.

An exception may need to be made for FXPs who do not have the technical capacity to quote 24/7. For example, some FXPs who do not have a global presence may only be able to quote in their country’s business hours. In this case, they would be expected to always provide active rates during their business hours but would be able to “exit” the market by withdrawing all their rates at the end of the business day. Over time and as they gain experience with Nexus payment flows, such FXPs should be able to develop the ability to automate rate provision and liquidity management outside of business hours, in order to start quoting 24/5 (Mon-Fri) and ultimately 24/7 (including weekends).​

PreviousOnboarding PSPsNextRevenue model for FXPs

Last updated 7 months ago