Skip to main content
A transaction’s error_code value can be null (for successful transactions) or one of the following for failed and declined transactions.

Core failures

The system can decline or fail a transaction itself rather than a connector or payment service rejecting the transaction. When this happens, one of the following error codes can be set as the error_code value.

Connector declines

When a payment service declines or fails the transaction the following error_code values can be set based on the response received from the payment service. The original values received from the payment service are available in the raw_response_* fields of a transaction record.
The amount column in the tables below specifies the amount that can be used to simulate the error_code when using the Card simulator connector.
The Retriable? column in the tables below only applies when the payment service returns no ISO 8583 response code. When an ISO response code is present, that code determines whether the transaction is retried, and the retriable ISO response codes list supersedes this column. A transaction is also never retried when the payment service explicitly marks the attempt as non-retriable, or when the response contains a merchant_advice_code.

Connector failures

Connector capture / void / refund / payout tests