Token.io passes the raw bank payment status in the transfer and payment initiation responses for Payments v1 and Payments v2 in the following fields:
The vast majority of banks return either the abbreviated or long ISO 20022 payment status codes.
Mapping to Token.io's payment statuses is bank-dependent as the final status is not standardised across banks.
The following diagram shows where the ISO 20022 payment status codes are returned within the payment flow:
The payment status codes are described in more detail here:
| Code | Name | Description |
|---|---|---|
| ACSC | AcceptedSettlementCompleted | Settlement on the debtor’s account has been completed. This status is sent by the debtor bank to confirm settlement on the debtor account prior to payment execution. |
| ACCC | AcceptedCreditSettlementCompleted | Settlement on the creditor's account has been completed. This status is sent by the creditor bank to confirm the settlement on the creditor’s account. |
| ACCP | AcceptedCustomerProfile | The preceding technical validation and customer profile checks have been successful. This status is sent by any bank in the payment flow to confirm acceptance prior to technical validation. |
| ACSP | AcceptedSettlementInProcess | All preceding checks, such as technical validation and customer profile were successful and payment initiation has been accepted for execution. This status is sent by any bank in the payment flow to confirm the payment is accepted following successful completion of technical validations. |
| ACTC | AcceptedTechnicalValidation | Authentication and syntactical and semantical validations have been successful. This status is sent by any bank in the payment flow to the previous bank to confirm the payment has been accepted following successful completion of technical validations. |
| ACWC | AcceptedWithChange | The instruction has been accepted but a change will be made, such as date or remittance not sent. This status is sent by any bank in the payment flow to the previous bank to confirm the payment has been accepted following the amendments. |
| ACWP | AcceptedWithoutPosting | The payment instruction included in the credit transfer has been accepted without being posted to the creditor customer’s account. This status is sent by the creditor bank to the previous bank in the payment flow to confirm the acceptance of payment without settlement on the creditor’s account. |
| ACFC | AcceptedFundsChecked | The preceding check of technical validation and customer profile have been successful and the automatic funds check was positive. This status is sent by any bank in the payment flow to the previous bank to confirm the payment has been accepted following the amendments. |
| RCVD | Received | Payment initiation has been received by the bank. This status is sent by any bank to the previous bank in the payment flow as confirmation that their payment initiation request has been received by the payment engine. |
| PART | PartiallyAccepted | A number of transactions have been accepted, but some transactions have not yet achieved 'accepted' status. This code is only used for bulk payments, where reporting is performed against the entire file. |
| PATC | PartiallyAcceptedTechnicalCorrect | The payment initiation needs multiple authentications, where some but not yet all have been performed. Syntactical and semantical validations have been successful. |
| PDNG | Pending | The payment initiation or individual transaction included in the payment initiation is pending. Further checks and a status update will be performed. This status is sent by any bank in the payment flow to the previous bank as an interim status while other validations are performed. |
| RJCT | Rejected | Payment initiation or an individual transaction included in the payment initiation has been rejected. This status is sent by any bank in the payment flow to inform the previous bank that their payment initiation has been rejected. |
| CANC | Cancelled | Payment initiation has been canceled before execution. |
If you have any feedback about the developer documentation, please contact devdocs@token.io