Swift GPI Statuses
You can receive the Swift GPI status and reason codes for your payments using the Get Status API.
Please refer below for more information about the various Swift GPI status & reason codes.
GPI Statuses
| Status Code | Description |
|---|---|
| RJCT | Rejected |
| ACSP | Accepted - Settlement in Progress |
| ACCC | Accepted - Settlement Completed |
| INVA | Invalid - Data validation error |
| WARN | Warning - payment is processing but there is a non-critical issue or potential delays |
GPI Reason Codes
| Reason Code | Status | Description |
|---|---|---|
| G000 | ACSP | Payment transferred to the next GPI agent |
| G001 | ACSP | Payment transferred to a non-GPI agent |
| G002 | ACSP | Pending credit may not be same day |
| G003 | ACSP | Pending receipt of documentation from the creditor |
| G004 | ACSP | Pending receipt of funds from the previous bank |
| G005 | ACSP | Delivered to beneficiary bank as GPI |
| G006 | ACSP | Delivered to beneficiary bank as non-GPI |
| AC01 | RJCT | Account number is invalid or missing. |
| AC04 | RJCT | Account number specified has been closed on the bank of account's books. |
| AC06 | RJCT | Account specified is blocked, prohibiting posting of transactions against it. |
| BE01 | RJCT | Identification of end customer is not consistent with associated account number. (formerly CreditorConsistency). |
| NOAS | RJCT | Failed to contact beneficiary. |
| RR03 | RJCT | Specification of the creditors name and/or address needed for regulatory requirements is insufficient or missing. |
| FF07 | RJCT | Purpose is missing or invalid. |
| RC01 | RJCT | Bank identifier code specified in the message has an incorrect format (formerly IncorrectFormatForRoutingCode). |
| G004 | RJCT | Missing cover. |
| RC08 | RJCT | Routing code not valid for local clearing. |
| FOCR | RJCT | Return following a cancellation request. |
| DUPL | RJCT | Payment is a duplicate of another payment. |
| RR05 | RJCT | Regulatory or central bank reporting information missing, incomplete, or invalid. |
| AM06 | RJCT | Below limit. |
| CUST | RJCT | At request of creditor. |
| MS03 | RJCT | Reason has not been specified by agent. |
| X001 | INVA | Syntax error |
| X002 | INVA | Status originator not allowed to update the status of this payment (possibly sent out of order) |
| X003 | WARN | The transaction is already in final state (no further action is needed) |
| X004 | INVA | Unknown transaction identifier (status update may have been sent out of order) |
| X005 | WARN | Instructed amount of payment message does not match previously sent payment messages for the same transaction identifier |
| X006 | WARN | You are not allowed to send a return message |
| X007 | WARN | Payment message tracked that invalidates the status update |
| X008 | INVA | Status update sent by institution that does not participate in transaction (possibly sent out of order) |
| X009 | WARN | Debtor agent does not match previously sent payment messages for the same transaction identifier |
| X011 | INVA | Status update not allowed |
| X012 | INVA | Deducts mismatch |
| X018 | WARN | The UETR has already been used within the gpi service |
| X021 | INVA | The value in either SettlementMethod or ClearingSystem or Reject Reason Code is not allowed |
| X022 | WARN | Reject message cannot be tracked / Returns are not handled by the Tracker |
| X026 | INVA | The Tracker informing party and instructed agent of a SWIFT Go status confirmation should be a bank participating to the SWIFT Go service |
| X027 | WARN | A cover cannot be initiated on a SWIFT Go transaction |
| X040 | WARN | Settlement Method INGA is not allowed |
| X041 | WARN | Amount inconsistency detected |
| X042 | INVA | User-to-Tracker status confirmations updates or reject payment messages are not supported for a transaction in a return flow |
| X043 | WARN | A cover leg is not supported for a transaction in a return flow |
| X044 | WARN | pacs.008 messages are not allowed in a transaction in a return flow |
| X045 | WARN | Tracking of returns is not yet supported for a transaction containing cover legs |
| I001 | WARN | The transferred amount exceeds the allowed amount threshold for the currency, as per the SWIFT Go Rulebook |
| I002 | WARN | The charge code is not valid for a SWIFT Go transaction |
| I003 | WARN | Senders charges are not allowed for a SWIFT Go transaction |
| I004 | WARN | The interbank settlement amount of a SWIFT Go transaction must match that of the previous leg |
| I005 | WARN | The currency is not supported by the receiver of the SWIFT Go message |
| I006 | WARN | The beneficiary is not a SWIFT Go customer |
| I008 | WARN | Partial credit confirmation is not supported for SWIFT Go |
Updated about 2 months ago