Time critical vs non-time critical payments

A payment can be time critical when the use case requires near-instant confirmation of rejection, for example when paying in-store, or non-time critical, for example when using Nexus for bill payments.

Whether a payment is time-critical or not is flagged using the pacs.008 Instruction Priority element(/Document/FIToFICstmrCdtTrf/CdtTrfTxInf/PmtTpInf/InstrPrty/).

In general the Source PSP should set the Instruction Priority, based on what it knows about the type of payment that is being initiated. For example, payments to a retail business, or initiated by scanning a QR code, are more likely to be time sensitive. If the Sender is asked to select the priority, they should be informed of the implications of their choice.

Time-critical payments

Time-critical payments must only be accepted by the Destination PSP when the Destination PSP is (a) able to perform real-time sanction screening, AND (b) if the screening is OK, the Destination PSP is able to credit the recipient in real time.

• The Source PSP should set the pacs.008 Instruction Priority to HIGH

• Within the timeout SLA of the Destination IPS, the Destination PSP must process the payment and return a pacs.002 with one of the following status codes:

  • ACCC – accepted and credited to recipient

  • RJCT – rejected

  • BLCK - funds blocked and will not be returned (due to suspicious or illicit activity)

• The pacs.002 will flow from the Destination PSP to Destination IPS, to Nexus, to the Source IPS and finally to the Source PSP.

• (Note: The Source SAP may only respond with ACCC or RJCT.)

Non-time critical payments

• The Source PSP should set the pacs.008 Instruction Priority to NORM (pacs.008 element /Document/FIToFICstmrCdtTrf/CdtTrfTxInf/PmtTpInf/InstrPrty/ ) when the payment is non-time-critical.

• Within the technical timeout SLA of the Destination IPS, the Destination PSP must process the payment and send back a pacs.002 with one of the following status codes:

  • ACCC – accepted and credited to recipient

  • RJCT – rejected

  • BLCK – funds blocked and will not be returned (due to suspicious or illicit activity)

  • ACWP – accepted without posting to the Recipient’s account

• The pacs.002 will flow from the Destination PSP to Destination IPS, to Nexus, to the Source IPS and finally to the Source PSP.

• (Note: The Source SAP may only respond with ACCC or RJCT.)

Note that the Destination PSP must still respond with one of the above status codes within the timeout of the Destination IPS (typically 30 seconds or less), to ensure the Sender has certainty about the status of the payment.

If the Destination PSP responds with the status code ACWP, the Destination IPS must still complete the transfer between the Destination SAP and Destination PSP, but the Destination PSP will not immediately credit funds to the Recipient.

Following up on an ACWP response

When the Destination PSP responds with ACWP, the Destination IPS will process the payment in the same way it would an ACCC, and send a confirmation to Nexus. From Nexus's perspective, all payment processing through the IPSs is now complete. But further steps are required to update the Sender on the final status of the payment.

After the Destination PSP responds with ACWP, then within the time limit set in the Nexus Scheme Rulebook, the Destination PSP must respond with:

• ACCC (Accepted and Credited to Creditor Account) – funds now credited to the recipient

• BLCK (Blocked) – funds blocked and will not be returned (due to suspicious or illicit activity)

• ACWC (Accepted with Changes) with status reason code (StsRsnInf/Rsn/Cd) RUTA (Return upon Unable To Apply) - in this case, the Destination PSP was not able to reach a definitive answer within the time limit specified in the Nexus Scheme Rulebook. The Destination PSP must initiate a new Nexus payment to return the funds to the Source PSP

The Nexus Scheme Rulebook defines the maximum time in which an ACWP payment must be credited to the Recipient, blocked or returned.