When you submit a payment, payment return, or payment cancellation using a POST pacs.008, pacs.004, or camt.056 request, the payment will have an associated status and response code, including a brief description. You can send a GET pacs.002 request to retrieve this information:
Payment status is given in the fitoFIPmtStsRpt.txInfAndSts.txSts field.
Response code and description is given in the fitoFIPmtStsRpt.txInfAndSts.stsRsnInf.addtlInf field.
The SEPA Credit Transfer (SCT) response codes for different payment statuses are given in the following sections.
Pending status
Initially, once you have submitted the payment request, Payments Hub sets the transaction status to PEND, until it performs the transaction settlement and an accepted or rejected status is set. In the POST pacs.008 response this appears as PENDING and in the GET pacs.002 response it is PEND.
Accepted statuses
Table: Response codes for accepted payments.
Transaction status | Status code | Status description | Status sent from |
|---|---|---|---|
ACCC | 0000 | Accepted without qualification | Payment scheme |
Rejected statuses
All rejected payments have the transaction status RJCT.
Table: Response codes for rejected payments.
Status code | Status description | Rejected by |
|---|---|---|
AC01 | Account identifier is invalid (IBAN is invalid or the account number does not exist) | Payments Hub or beneficiary bank |
AC02 | Debtor account number is invalid | Payments Hub |
AC03 | Creditor account number is invalid | Payments Hub or beneficiary bank |
AC04 | Account is closed | Payments Hub or beneficiary bank |
AC06 | Account is blocked for unspecified reason | Payments Hub (for debtor account) or beneficiary bank (for creditor account) |
AG01 | Payment type is not allowed | Payments Hub |
AG02 | Bank operation/transaction code is incorrect | Payments Hub |
AM01 | Amount is equal to zero | Payments Hub |
AM02 | Amount is more than 999,999,999.99€ | Payments Hub |
AM03 | Currency is not allowed | Payments Hub |
AM05 | Duplicate payment | Payments Hub or beneficiary bank |
AM09 | Amount has more than 2 decimals | Payments Hub |
BE04 | Creditor address is missing | Payments Hub |
BE19 | Charge bearer code is a value other than SLEV or SHAR | Payments Hub |
CNOR | Creditor’s Payment Service Provider (PSP) is not registered under this BIC in the used Clearing and Settlement Mechanism (CSM) | Payments Hub |
ERIN | Extended Remittance Information (ERI) option is not supported | Payments Hub |
FF06 | Category Purpose code is missing or invalid | Payments Hub |
FOCR | Return is due to a recall | Payments Hub or beneficiary bank |
MD07 | End customer is deceased | Payments Hub or beneficiary bank |
MS02 | Reason is not specified by the customer | Payments Hub |
MS03 | Reason is not specified by the agent | Payments Hub or beneficiary bank |
NARR |
| Payments Hub |
RC01 | PSP identifier is incorrect (such as invalid BIC) | Payments Hub or beneficiary bank |
RC05 | BIC identifier is invalid or missing. Used when the problem can be with the debtor or creditor account. | Payments Hub or beneficiary bank |
RC06 | Debtor BIC identifier is invalid or missing | Payments Hub or beneficiary bank |
RC07 | Creditor BIC identifier is invalid or missing | Payments Hub or beneficiary bank |
RR01 | Regulatory reason (missing debtor account or identifier) | Payments Hub or beneficiary bank |
RR02 | Regulatory reason (missing debtor name or address) | Payments Hub or beneficiary bank |
RR03 | Regulatory reason (missing creditor name or address) | Payments Hub or beneficiary bank |
RR04 | Regulatory reason | Payments Hub or beneficiary bank |
RR10 | Message ID includes invalid chars or more than 35 chars | Payments Hub |
TM01 | Interbank settlement date is wrong | Payments Hub |
Response
If the request is valid, you receive an HTTP 200 OK response, which means that the payment status was successfully retrieved. For further details of HTTP response codes and instructions on how to handle errors, see HTTP codes and request error handling .
In addition to the response code, the response body returns the fitoFIPmtStsRpt JSON object, which contains a pacs.002 ISO message.
The following table shows some response body elements. For details on all the response body elements, see Message field definition for pacs.002 .
Extract the value of the txInfAndSts.txSts key to see the current status of the payment.
Table: Check the payment status - Relevant response body elements.
Element | Description | Data type |
|---|---|---|
txInfAndSts.orgnlGrpInf.orgnlMsgId | Message ID you defined in the payment request message as the grpHdr.msgId field value | String |
txInfAndSts.orgnlTxId | Transaction ID you defined in the payment request message as the cdtTrfTxInf.pmtId.txId field value |
|
txInfAndSts.orgnlEndToEndId | End-to-end ID you defined in the payment request message as the cdtTrfTxInf.pmtId.endToEndId field value. If no value has been provided, NOT PROVIDED is used. | String |
txInfAndSts.txSts | Current status you wanted to check. The possible status values are based on the ISO standard. For example: ACCC (accepted) or RJTC (rejected) For more information on the status and the related codes that provide the reason for the payment acceptance or rejection, see Payment status and codes . | String |