Skip to content
Last updated

Payment Statuses

Payment statuses indicate the current state of a payment as it moves through initiation, authorization, and settlement. They follow the ISO 20022 transaction status codes and are returned by the payment endpoints and included in webhook event payloads.

Use payment statuses to track the lifecycle of single and bulk payments, determine whether a payment requires further action (e.g. additional authorization), and react to status changes in real time via events.

See Webhooks for more information about subscribing to events.

Payment Statuses:

StatusNameDescription
AcccAcceptedSettlementCompletedSettlement on the creditor's account has been completed.
AccpAcceptedCustomerProfilePreceding check of technical validation was successful. Customer profile check was also successful.
AcscAcceptedSettlementCompletedSettlement on the debtor’s account has been completed.
AcspAcceptedSettlementInProcessAll preceding checks such as technical validation and customer profile were successful and therefore the payment initiation has been accepted for execution.
ActcAcceptedTechnicalValidationAuthentication and syntactical and semantical validation are successful.
AcwcAcceptedWithChangeInstruction is accepted but a change will be made; such as date or remittance not sent.
AcwpAcceptedWithoutPostingPayment instruction included in the credit transfer is accepted without being posted to the creditor customer’s account.
RcvdReceivedPayment initiation has been received by the receiving agent.
PdngPendingPayment initiation or individual transaction included in the payment initiation is pending. Further checks and status update will be performed.
RjctRejectedPayment initiation or individual transaction included in the payment initiation has been rejected.
CancCancelledPayment initiation has been cancelled before execution
AcfcAcceptedFundsCheckedPreceding check of technical validation and customer profile was successful and an automatic funds check was positive .
PatcPartiallyAcceptedTechnicalCorrect The payment initiation needs multiple authentications; where some but not yet all have been performed. Syntactical and semantical validations are successful.
PartPartiallyAcceptedA number of transactions have been accepted; whereas another number of transactions have not yet achieved 'accepted' status. Remark: This code may be used only in case of bulk payments. It is only used in a situation where all mandated authorisations have been applied; but some payments have been rejected.

Common payment flows

Single payment

When a single payment is initiated it enters RCVD. If the payment requires approval, each authorization moves it through PATC to ACTC. Once fully authorized (or if no approvers are configured), the payment is exported to the bank. A successful export sets the status to PNDG; a failure results in RJCT. The payment can be cancelled while still in RCVD.

Payment initiated

User cancels payment

No approval required

First approver authorizes

Single approver - fully authorized

Multiple approvers - awaiting next

Remaining approver authorizes

Sent to bank

Accepted

Failed

RCVDCANCACTCMultipleapprovers?PATCBankprocessingPNDGRJCT

Bulk payment

Bulk payments follow the same authorization flow as single payments, but the export can produce mixed results. If all lines succeed the bulk moves to PNDG. If all fail it moves to RJCT. On partial success, each payment line gets its own status (PNDG or RJCT) and the bulk payment itself is set to PART.

Bulk payment initiated

User cancels bulk and all lines

First approver authorizes

Single approver - fully authorized

Multiple approvers - awaiting next

Remaining approver authorizes

Sent to bank

All lines accepted

All lines rejected

Some lines accepted, some rejected

Bulk payment itself

Each accepted line

Each rejected line

RCVDCANCMultipleapprovers?ACTCPATCBankprocessingPNDGRJCTMixedoutcomePART
Note

The bulk payment stays in RCVD or PATC until all payment lines (or the bulk itself) are authorized. Cancelling a bulk payment also cancels all its payment lines.

Bank response

After a payment is exported (PNDG), the bank processes it and returns a final status. The bank may accept it (ACCP), accept it with modifications (ACWC), partially accept it (PART), or reject it outright (RJCT). Accepted payments eventually reach ACSC when settlement is completed, but can still be rejected or cancelled before that.

Bank validates and accepts

Bank rejects payment

Bank accepts some lines

Bank accepts with modifications

Settlement completed

Bank rejects after acceptance

Bank cancels before settlement

Settlement completed

Bank rejects after acceptance

PNDGACCPRJCTPARTACWCACSCCANC