Nexus uses a standard
pacs.002payment status message. Nexus will perform some minor transformation (changing the instructing and instructed agents) when forwarding the message from the Destination PSP to the Source PSP.
The status codes use a subset of the
ExternalPaymentTransactionStatus1Codefrom the ISO20022.org external code sets. Status codes used in the Nexus
pacs.002are as follows:
PACS.002 TRANSACTION STATUS CODE
REASONS FOR USE
Accepted Settlement Completed Creditor Account
Destination PSP is happy to accept the payment. (Payment did not trigger alert against sanctions lists, OR a previous alert has been identified to be a false positive)
Destination PSP should immediately credit the recipient’s account
Accepted Without Posting
Payment instruction included in the credit transfer is accepted without being posted to the creditor customer’s account.
Destination PSP holds funds and tries to resolve sanctions alert within the time permitted in the Nexus rulebook.
The Destination PSP is unable or willing to accept the payment. (Possible reasons: account closed or does not exist; D-PSP considers payment to be suspicious; the D-PSP previously replied with ACWP but cannot resolve the sanctions alert within the permitted Nexus SLA)
No further action, unless it follows an earlier pacs.002 with status ACWP.
If RJCT follows an earlier ACWP, the
Destination PSP should THEN send
A payment transaction previously reported with status 'ACWP' is blocked, for example, funds will neither be posted to the Creditor's account, nor be returned to the Debtor. Used when the Destination PSP believes that the payment is illicit and should be reported to authorities.
Freeze the funds. File a suspicious activity report to the authorities.
Used by a PSP when acting as Settlement Account Provider for a specific payment.
Detailed usage guidelines for the pacs.008 will be shared here over the next few months.
Last modified 2mo ago