Payment status code indicates the status of a single payment transaction.

Single Payment API supports following codes:

  • ACTC Accepted Technical Validation
  • ACSP Accepted Settlement In Process
  • ACSC Accepted Settlement Completed
  • PDNG Pending
  • RJCT Rejected

Bulk Payment API supports following codes:  

  • ACTC Accepted Technical Validation
  • ACSP Accepted Settlement In Process
  • ACSC Accepted Settlement Completed
  • PDNG Pending
  • RJCT Rejected
  • PART PartiallyAccepted



ID Equivalent ISO Code Name Description Status Scope / Notes
1 RJCT Rejected Payment initiation or individual transaction included in the payment initiation has been rejected or Payment initiation has expired. Payment will be in this state also after cancelation. Existing All payment types
2 PDNG Pending After the signing process, payment will be switched to this status in case of requestedExecutionDate in future.  Existing All payment types
3 ACTC AcceptedTechnicalValidation Authentication and syntactical and semantical validation are successful. NEW All payment types
4 ACSP AcceptedSettlementInProcess

All preceding checks such as technical validation and customer profile were successful and therefore the payment initiation has been accepted for execution. This status is reached under conditions mentioned below:

1) Payment is successfully authorized, but is internally processed.

2) In case there are multiple authorizations needed, payment stays in this state after the first authorization. 

Existing All payment types
5 ACSC AcceptedSettlementCompleted Settlement on the debtor's account has been completed. Existing All payment types
6 PART PartiallyAccepted A number of transactions have been accepted, whereas another number of transactions have not yet achieved 'accepted' status. This is a specific status for bulk payment in case some payments were unable to be processed.  NEW File level status, applicable for file payments


Single Payment Status Diagram

Bulk Payment Status Diagram 

Payment initiation

To initiate a payment, you have to call one of the initiation methods e.g. POST /v1/{payment-service}/{payment-product}*. After successful payment initiation with HTTP 201 created response your payment may enter ACTC or RJCT state. Initiated payment can be rejected due to business validation rules fault e.g. AC01 - Creditor IBAN is not valid: CZ6575000000001234567891.

    "paymentId": "EDE04525712C6C4B0FFC17D178BBB290",

    "authorizationId": "EDE04525712C6C4B0FFC17D178BBB290",
    "transactionStatus": "ACTC",


Payment order identifier

If the payment is initiated successfully, the bank server returns paymentId which is unique identifier of the payment. This identifier may be used as a parameter for checking a payment status with GET /v1/{payment-service}/{payment-product}/{paymentId}/status*

Payment submission

If the payment is initiated successfully, the payment is in ACTC state and you can let your customer authorize the payment. in order to submit the payment, you have to call PUT /v1/{payment-service}/{payment-product}/{paymentId}/authorizations/{authorizationId}* method. After your customer authorizes the payment and it is submitted, it changes its status:

  1. ACSP in case of successful payment authorization (NOTE: For bulk payment, payment stays in this status also in case of another authorization needed - Multi SCA)
  2. PDNG in case of requested execution date is in future
  3. RJCT in case of failing business validation rule

Transaction Reason Code

Transaction Reason code specifies the reason for a transaction to be rejected, returned or reversed by an instructed agent or somebody acting on behalf of an instructed agent. This reason is limited to the ISO 20022 Transaction Reason Code code-list enumeration.


    "errorCode": "FORMAT_ERROR",

    "reasonCode": "AC01",

    "additionalInformation": "Invalid IBAN (Debtor IBAN)",

    "transactionStatus": "RJCT"


The Payments API supports following codes:

  • AC01 Format of the account number specified is not correct.
  • AC04 Account number specified has been closed on the Receiver's books.
  • AG01 Transaction forbidden on this type of account.
  • AM03 Specified message amount is in a non processable currency outside of existing agreement.
  • AM04 Amount of funds available to cover specified message amount is insufficient.
  • AM05 This message appears to have been duplicated.
  • AM09 Amount received is not the amount agreed or expected.
  • AM10 Sum of instructed amounts does not equal the control sum.
  • DT01 Invalid date (e.g., wrong settlement date).
  • MS03 Reason has not been specified by agent.
  • RC01 Bank identifier code specified in the message has an incorrect format.
  • RR03 Missing creditor name or address (defined by SEPA Credit Transfer Scheme Rulebook).
  • TM01 Associated message was received after agreed processing cut-off time.


Authorization Status

  1. received
    1. After initiation payment status
  2. scaAuthenticated
    1. User is successfully signed in during authorization process
  3. unconfirmed
    1. User confirm payment in authorization portal
    2. User confirm cancellation in authorization portal
  4. finalised
    1. After calling confirmation request with one-time token. Payment could be in statuses:
      1. ACSC – success
      2. PDNG – forward payment
      3. RJCT – payment rejected by bank
  5. failed
    1. Payment authorization is cancelled by user in portal