ACSP, ACCC and RJCT are payment transaction status codes. G000 to G006 are status reason codes, reported alongside a status to say why a payment is in that state. Both sets are published by the ISO 20022 Registration Authority in the ISO 20022 External Code Sets, and both are free to download.
Source for every definition on this page
Definitions below are quoted verbatim from the ISO 20022 External Code Sets, published and maintained by the ISO 20022 Registration Authority. Status codes come from the code set ExternalPaymentTransactionStatus1Code; reason codes come from ExternalStatusReason1Code.
These report where an instruction stands. A bank reports one of them per transaction in an ISO 20022 payment status report.
| Code | Definition published by ISO 20022 |
|---|---|
RCVD |
“Payment instruction has been received.” |
PDNG |
“Payment instruction is pending. Further checks and status update will be performed.” |
ACSP |
“All preceding checks such as technical validation and customer profile were successful and therefore the payment instruction has been accepted for execution.” The payment has been accepted, and settlement is in progress. |
ACWP |
“Payment instruction included in the credit transfer is accepted without being posted to the creditor customer’s account.” |
ACSC |
“Settlement completed. Usage : this can be used by a Market Infrastructure reporting to Infrastructure Participant or an Account Servicer to Account Owner to report that the transaction account entry has been completed. Warning : this status is provided for transaction status reasons, not for financial information. It can only be used after bilateral agreement” |
ACCC |
“Settlement on the creditor’s account has been completed.” The payment has been successfully credited to the beneficiary's account. |
RJCT |
“Payment instruction has been rejected.” The code set does not record why. A reason is carried separately, in a status reason code. |
The code set holds more codes than the seven above, including codes used for cheques, for verification of payee and for cancellations. The published file is the complete list. See the full code set.
A reason code is reported next to a status code and qualifies it, which is why these are usually written as a pair, for example ACSP/G000 or ACSP/G004. The definitions distinguish an FI to FI customer credit transfer from a financial institution credit transfer with cover, and are quoted in full below.
G000G001G002G003G004G005G006Status and reason codes travel in the ISO 20022 payment status report message, pacs.002 (FIToFIPaymentStatusReport). ISO describes that message as usable for the status of a credit transfer or direct debit instruction, in domestic and in cross-border scenarios. The message definitions and their schemas are published by ISO 20022. ISO 20022 message definitions.
The definitions above belong to ISO 20022 and are open. They are most often met in the context of Swift* gpi*, a service that Swift* provides to financial institutions. Its own pages are the authority on what that service does and on who may use it.
This page is a glossary of published code definitions. It is not a status service, it is not affiliated with Swift*, and it does not reproduce data from the Swift* gpi* Tracker.