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. Messaging & Translation
  2. MESSAGE: pacs.008 FI to FI Customer Credit Transfer

pacs.008 Differences from CPMI Harmonisation Requirements

In some cases, Nexus requires additional information, so elements which are defined as optional in CPMI or CBPR+ usage guidelines are mandatory in Nexus. These are specified in the table below:

ELEMENT

STATUS IN CPMI

STATUS IN CBPR+

STATUS IN NEXUS

NOTES

Acceptance Date Time (AccptncDtTm)

Does not stipulate usage

Optional

Mandatory

Defines the point in time when the payment order from the initiating party meets the processing conditions of the account servicing agent. Required for Timeout and SLA management.

Clearing System (GrpHdr/SttlmInf/ClrSys)

Optional

Optional

Mandatory

This is required to identify the domestic instant payment system operator. This is updated by Nexus to reflect the Destination IPS before the payment is sent to the Destination IPS.

Intermediary Agent 1 and 2 (IntrmyAgt1 and IntrmyAgt2)

Optional

Optional

Mandatory

These are required in Nexus to identify the Settlement Account Providers at which the FXP holds funds in both currencies.

Instruction Identification

Optional

Mandatory

Optional

UETR is the primary instruction identification used in Nexus. Instruction Identification is therefore optional.

Instructed Amount (InstdAmt)

Mandatory

Optional

Mandatory

Mandatory in line with CPMI recommendations.

Debtor Account (DbtrAcct)

Recommended

Optional

Mandatory

The Debtor Account is used to identify the account of the Debtor (Sender). This is recommended but not mandatory in CPMI, but mandatory in Nexus.

Creditor Account (CdtrAcct)

Recommended

Optional

Mandatory

The Creditor Account is used to identify the account of the Creditor. This is recommended but not mandatory in CPMI, but mandatory in Nexus.

Remittance Information (RmtInf)

Optional

Optional

Conditional Mandatory

Mandatory only in case the Source PSP uses an FXP for the currency exchange. The sub-element Additional Remittance Information (AddtlRmtInf) is mandatory (if the above condition applies) and contains the Nexus FX Quote ID, which is required for validating the FX Quote.

Exchange Rate (XchgRate)

Does not stipulate usage

Optional

Mandatory

Required to convert the amount from Source currency to Destination currency

Previous Instructing Agent 1 and 2 (PrvsInstgAgt1 and PrvsInstgAgt2)

Optional

Optional

Mandatory (on Destination leg)

These are required in Nexus to identify the Settlement Account Providers at which the FXP holds funds in both currencies.

Differences against CBPR+

There are also the following notable differences against CBPR+:

  • Nexus uses the latest version of the ISO 20022 message (pacs.008.001.11) while CBPR+ uses an older version (pacs.008.001.08)

  • Group Header Changes:

    • The Settlement Method of Nexus is defined as CLRG, but this value is removed from CPBR+ as not relevant.

  • Transaction Level Changes:

    • Service Level is limited to three repetitions in CBPR+, while this is limited to 1 in Nexus

    • CBPR+ has additional rules on the filling of postal address fields, (in line with CPMI recommendations) to maximise the granularity of postal address details. Nexus strongly recommends this approach but does not yet make it mandatory, meaning that Nexus will not reject a message that uses Address Line fields over dedicated StreetName, TownName, PostalCode elements.

PreviousMESSAGE: pacs.008 FI to FI Customer Credit TransferNextMESSAGE pacs.002 Payment Status Report

Last updated 8 months ago