Step 13-16: Set up and send the payment instruction
Now that the Sender has approved the payment, the PSP must set up the Nexus-standard pacs.008
payment instruction (or domestic equivalent) and submit it to the local IPS.
Step 13: Retrieve the Intermediary Agents (FXP’s accounts)
The PSP uses the API operation
GET /quotes/{quoteId}/intermediary-agents
to retrieve the Intermediary Agents, based on the FX Quote ID of their preferred quote. This information is used in thepacs.008
message to specify the accounts held by the FX Provider in both the Source and Destination country. Funds will be paid into the FXP's account in the Source Country and paid out of the FXP's account in the Destination Country.
Step 14: Construct the Nexus pacs.008 payment instruction
The PSP constructs the pacs.008 payment instruction: this will make use of information from the earlier responses to:
GET /quotes
The
acmt.023
proxy or account resolution requestGET /quotes/{quoteId}/intermediary-agents
The Source PSP should define whether the payment is time-critical or non-time critical by setting the Instruction Priority (
/Document/FIToFICstmrCdtTrf/CdtTrfTxInf/PmtTpInf/InstrPrty/
) as follows:NORM
: default, for all payments that are not urgent or time-critical. This flag will allow the Destination PSP extra time (to be defined in the Nexus scheme rulebook) to complete sanctions screening in the event the payment triggers an alert.HIGH
: for urgent payments and physical point-of-sale payments (eg where the customer cannot leave the store until the payment is confirmed). IfHIGH
is used, the Destination PSP must reject any payments that it cannot immediately accept. Payments markedHIGH
are more likely to be rejected if the Destination PSP does not have real-time sanctions screening systems. They will also be rejected if the payment generates a sanctions alert which the Destination PSP cannot resolve without manual intervention. This means thatHIGH
should not be used unnecessarily.
See MESSAGE: pacs.008 FI to FI Customer Credit Transfer for further details.
Step 15: Send the pacs.008
to the Source IPS
pacs.008
to the Source IPS Once the Sender has confirmed the payment, the PSP should submit the
pacs.008
payment instruction to the Source IPS (using the same secure connection that the PSP normally use to submit domestic payment instructions to the IPS).The Source IPS will process the payment and then forward it to Nexus, following the process in Payment Processing.
Checking for duplicated or fraudulent payments
In general, Nexus expects the Source PSP to ensure that any payment instructions it sends to Nexus are legitimate, non-fraudulent and compliant with all applicable regulations, and should therefore be processed. It is therefore the responsibility of the Source PSP to defend against sending fraudulent payments or payments that were sent in error.
Nexus uses the UETR (Unique End-to-End Transaction Reference) to check whether a payment is unique. Nexus will check whether a payment with the same UETR has already been processed, and will not process duplicates.
However, Nexus will not check whether similar payments with different UETRs are possible duplicates. For example, if a Source PSP sends two payments, for the exact same amount, between the same sender and recipient accounts, but with different UETRs, Nexus will assume both payments are intentional and will process both.
[ON ROADMAP] Step 16: Be ready to respond to any Requests for Information from the Destination PSP
The Request for Information process will use ISO 20022 messages to allow any PSP to request further (or corrected) information relating to an existing pacs.008
payment instruction. Relevant ISO 20022 messages exist but the process has not yet been designed in full for Nexus, and is currently on the roadmap.
If the Source PSP supports the Request for Information (RFI) service, the Source PSP should be prepared to respond to any RFIs relating to this payment. These requests could come from either of the Settlement Account Providers or the Destination PSP.
Last updated