Every order, payout, and P2P transaction carries a status code that provides detailed information about the reason for its current status. Status codes follow the format X-YY-ZZ:
X-YY-ZZ
│ │ └── Result code: specific outcome within the scenario.
│ └───── Scenario code: processing stage or scenario. See Scenario Codes below.
└──────── Source code: origin of the status. See Source Codes below.
Source Codes
| Code | Source | Description |
|---|
0 | — | Global success (approve) |
1 | System | Status originated on the system side |
2 | Provider | Status originated on the payment provider side |
3 | Acquirer | Status originated on the acquirer side (bank, card issuer, payment system) |
Scenario Codes
For sources 1 (System) and 2 (Provider), the scenario code is shared: the codes 1-02-XX and 2-02-XX are both Request Validation, on the System and the Provider side respectively.
| Code | Scenario |
|---|
01 | General statuses that cannot be tied to a specific scenario |
02 | Request validation |
03 | Payment method definition |
04 | 3DS |
05 | Antifraud |
06 | Limits control |
07 | Payment processing |
08 | Payment participant actions (merchant, payer, recipient) |
09 | Card processing |
10 | Wallet errors |
11 | Payout processing |
12 | P2P transfer processing |
Acquirer status codes (source 3) use their own set of scenario codes:
| Code | Scenario |
|---|
01 | Bank processing |
02 | Card processing |
03 | Payment system processing |
04 | Acquirer processing errors |
Result code 99 is reserved for technical errors (e.g. unexpected internal error).
Success Code
| statusCode | statusDescription | Resulting Order Status |
|---|
0 | Payment successfully processed (approve) | completed |
This is the only code that does not follow the X-YY-ZZ format — it is represented as a single digit 0, not 0-00-00.
Status Codes in Responses and Callbacks
Status codes are returned as statusCode (with a human-readable statusDescription) in:
System Status Codes (1-XX-XX)
These codes indicate errors or declines that originated on the system side.
General Statuses (1-01-XX)
| statusCode | statusDescription | Retry allowed |
|---|
1-01-01 | Gateway timeout | ✅ |
1-01-02 | The payment was automatically failed due to the expiration of the predefined timeout window set by the provider for completing the transaction or for the customer to submit the required payment method data | ❌ |
1-01-03 | The payment was cancelled due to the expiration of the timeout window for the merchant's customer to submit the required payment method data on the PSP payment page | ❌ |
1-01-04 | The order was moved to need_action due to a provider response timeout | ❌ |
1-01-05 | The payment was cancelled due to the expiration of the timeout window for obtaining the final payment status from the provider | ❌ |
1-01-06 | DNS resolution failed | ✅ |
1-01-07 | Payment gateway is temporarily unavailable | ✅ |
1-01-99 | General error | ❌ |
Request Validation (1-02-XX)
| statusCode | statusDescription | Retry allowed |
|---|
1-02-01 | Payout order creation via H2H is not configured | — |
1-02-02 | Payment setting mismatch | ❌ |
1-02-03 | Required payment method fields are missing | ❌ |
1-02-04 | Missing customer identifier | ❌ |
1-02-05 | Missing saved payment method identifier | ❌ |
1-02-06 | Customer mismatch | ❌ |
1-02-07 | Required sender fields are missing | ❌ |
1-02-08 | Required recipient fields are missing | — |
1-02-10 | Customer not found | ❌ |
1-02-11 | Order type mismatch | ❌ |
1-02-12 | Shop mismatch | ❌ |
1-02-13 | Missing shop identifier | ❌ |
1-02-14 | Only one of company or shop identifier should be specified | ❌ |
1-02-15 | Payment identifier is required to order a partial refund | ❌ |
1-02-16 | Card data submission is not permitted | ❌ |
Payment Method Definition (1-03-XX)
| statusCode | statusDescription | Retry allowed |
|---|
1-03-01 | No suitable payment method found for the provided parameters | ❌ |
1-03-02 | No routing rules found for order parameters | ❌ |
1-03-03 | No cascading rules found for order parameters | ❌ |
1-03-04 | No payment settings were found for the provided alias | ❌ |
1-03-05 | Too many payment settings were found with requested alias | ❌ |
1-03-06 | The provided order parameters do not match the payment settings alias | ❌ |
1-03-07 | Routing resolved a routing rule, but it does not contain any active payment settings | ❌ |
1-03-08 | Routing resolved a routing rule, but active payment settings in this rule have exceeded their limits | ❌ |
1-03-09 | Routing resolved a routing rule, but the payment settings in this rule have no scores assigned | ❌ |
1-03-10 | Payment settings selection by routing is not enabled | ❌ |
1-03-11 | No payment settings were found after routing, and the system is configured not to use fallback to the payment page | ❌ |
1-03-12 | No payment settings found on retry and cascading is disabled | ❌ |
1-03-13 | Required routing parameters are missing and collection on payment page is disabled | ❌ |
1-03-14 | No payment settings were found after routing | ❌ |
Antifraud (1-05-XX)
| statusCode | statusDescription | Retry allowed |
|---|
1-05-01 | Declined by timeout after antifraud decision "review" | ❌ |
1-05-02 | Declined by merchant after antifraud decision "review" | ❌ |
Payment Processing (1-07-XX)
| statusCode | statusDescription | Retry allowed |
|---|
1-07-01 | Missing required parameters for the selected payment method | ✅ |
1-07-02 | The provided currency value is not supported by the payment settings | ✅ |
1-07-03 | The provided dataEntryMode value is not supported by the payment settings | ✅ |
1-07-04 | The payment settings contain several data entry modes, but none were provided in the request | ✅ |
1-07-05 | Payment setting is disabled | ✅ |
1-07-06 | The provided amount is not allowed by the payment settings | ✅ |
1-07-08 | The payer must be over 18 years old | ✅ |
1-07-09 | The provided payer country is not supported by the payment settings | ✅ |
1-07-10 | The provided MCC is not supported by the payment settings | ✅ |
1-07-11 | The customerId is required for a saved payment method | ✅ |
1-07-12 | The savedPaymentMethodId is required for a saved payment method | ✅ |
1-07-13 | Required payment setting parameter failed validation | ✅ |
1-07-14 | Exceeds the balance limits for operation | ❌ |
1-07-15 | Exceeds the balance limits for shop/MID | ❌ |
1-07-16 | The order has no payments available for capture | ❌ |
1-07-17 | The order has no payments available for cancel | ❌ |
1-07-18 | The order has no payments available for reject | ❌ |
1-07-19 | Current order status does not match the expected status for update | ❌ |
1-07-20 | Order status transition from the current status to the requested status is not allowed | ❌ |
1-07-21 | The order is in an invalid state | ❌ |
1-07-22 | Entry mode is not set for card payment settings | ❌ |
1-07-23 | More than one default payment type is configured for the shop with the requested instrument type | ❌ |
1-07-24 | No default payment types are configured for the shop with the requested instrument type | ❌ |
1-07-25 | All payment attempts have been exhausted | ❌ |
1-07-26 | Payment retries are not allowed due to the status code of the last payment. All remaining retry attempts have been canceled | ❌ |
1-07-27 | Missing required parameters for the selected payment method and data collection on payment page is disabled | ❌ |
1-07-28 | No bank transfer codes found for the payer's country | ❌ |
1-07-29 | The maximum number of allowed final status transitions has been reached | ❌ |
Payment Participant Actions (1-08-XX)
| statusCode | statusDescription | Retry allowed |
|---|
1-08-01 | Cancelled by merchant | ❌ |
1-08-02 | Cancelled by merchant's customer | ❌ |
Provider Status Codes (2-XX-XX)
These codes indicate errors or declines that originated on the payment provider side.
General Statuses (2-01-XX)
| statusCode | statusDescription | Retry allowed |
|---|
2-01-01 | General decline | ✅ |
2-01-02 | The operation was timed out by the provider | ✅ |
2-01-03 | The provider returned a validation error because the payment amount does not match the required amount multiple | ✅ |
2-01-04 | Authorization failed | ✅ |
2-01-99 | Unknown internal error by the provider | ✅ |
Request Validation (2-02-XX)
| statusCode | statusDescription | Retry allowed |
|---|
2-02-01 | Bad request by the provider | ✅ |
2-02-02 | Unauthorized by the provider | ✅ |
2-02-03 | Transaction not found | ❌ |
2-02-04 | Invalid amount input | ✅ |
2-02-05 | General validation error | ✅ |
2-02-06 | Duplicate request | ❌ |
2-02-07 | Invalid amount or currency | ✅ |
2-02-08 | The payer must be over 18 years old | ✅ |
2-02-09 | Wrong request. Invalid parameter format | ✅ |
2-02-11 | Merchant not found | ✅ |
2-02-12 | Terminal not found | ✅ |
2-02-13 | Invalid payment token | ✅ |
2-02-14 | Payment routing configuration not found | ✅ |
2-02-15 | IP address is not whitelisted | ✅ |
2-02-16 | Transaction amount below minimum limit | ✅ |
2-02-17 | Transaction amount above maximum limit | ✅ |
2-02-18 | Provider service temporary unavailable | ✅ |
2-02-19 | One or more fields have invalid data format | ✅ |
2-02-20 | One or more required parameters are missing | ✅ |
2-02-21 | Request validation failed | ✅ |
2-02-22 | Invalid request | ✅ |
2-02-23 | Invalid Credentials | — |
2-02-24 | Authorization header not found | ✅ |
2-02-25 | Invalid signature | ✅ |
2-02-26 | Expired payment token | ✅ |
2-02-27 | Insufficient permissions | ✅ |
2-02-28 | Invalid bank account | ✅ |
2-02-29 | Transaction amount below minimum limit or above maximum limit | ❌ |
2-02-30 | Transaction already exists | ❌ |
2-02-31 | The merchant account is disabled | ❌ |
2-02-32 | Invalid authorization header | ✅ |
2-02-33 | Signature type is not a supported algorithm | ✅ |
2-02-34 | Access token not found | ✅ |
2-02-35 | Daily transaction count limit exceeded | ✅ |
2-02-36 | Daily rejected transaction count limit exceeded | ✅ |
2-02-37 | Transaction expired | ❌ |
2-02-38 | Invalid currency | ❌ |
2-02-39 | Duplicate transaction | ❌ |
2-02-40 | Invalid Transaction | ❌ |
2-02-41 | Email already used by another beneficiary | ❌ |
2-02-42 | Phone already used by another beneficiary | ❌ |
Payment Method Definition (2-03-XX)
| statusCode | statusDescription | Retry allowed |
|---|
2-03-01 | Payment setting is disabled | ❌ |
2-03-02 | Payment method is not enabled or the endpoint is incorrect | ✅ |
3DS Checks (2-04-XX)
| statusCode | statusDescription | Retry allowed |
|---|
2-04-01 | 3DS general timeout | ✅ |
2-04-03 | 3DS failed | ✅ |
2-04-04 | 3DS authentication cancelled or abandoned | ✅ |
2-04-05 | 3DS authentication failed | ✅ |
Antifraud (2-05-XX)
| statusCode | statusDescription | Retry allowed |
|---|
2-05-01 | General fraud suspect | ✅ |
2-05-02 | Compliance limitation | ✅ |
2-05-03 | The amount limit has been exceeded | ✅ |
2-05-04 | Email in blacklist | ✅ |
2-05-05 | IP in blacklist | ✅ |
2-05-06 | Cardholder in blacklist | ✅ |
2-05-07 | Billing country in blacklist | ✅ |
2-05-08 | Billing account is suspended | ✅ |
2-05-09 | Security violation | ✅ |
2-05-10 | Customer in blacklist | ✅ |
2-05-11 | Risk assessment timeout | ✅ |
2-05-12 | Card number is in blacklist | ❌ |
2-05-13 | No eligible disbursement channel available | ❌ |
2-05-14 | Declined by Risk Check | ✅ |
2-05-15 | Customer in blacklist by provider | ✅ |
2-05-16 | Declined due to blacklisted attributes | ✅ |
2-05-17 | High risk detected based on the payer's email address | ✅ |
2-05-18 | Customer is blocked | ✅ |
2-05-19 | Declined by credit card risk | ✅ |
2-05-20 | Rejected due to regulatory reasons | ❌ |
2-05-21 | Rejected due to international sanction lists | ❌ |
2-05-22 | Rejected due to national sanction list | ❌ |
2-05-23 | Rejected after KYC check | ✅ |
2-05-24 | Risk detected during document information validation | ❌ |
2-05-25 | Rejected due to Politically Exposed Person (PEP) | ❌ |
2-05-26 | Failed OTP verification | ✅ |
2-05-27 | Failed biometric check | ✅ |
Limits Control (2-06-XX)
| statusCode | statusDescription | Retry allowed |
|---|
2-06-01 | Provider limit on the total amount of transactions has been exceeded | ✅ |
2-06-02 | Merchant processing limit reached | ✅ |
2-06-03 | Customer operation limit exceeded | ✅ |
2-06-04 | Beneficiary limit exceeded | ✅ |
Payment Processing (2-07-XX)
| statusCode | statusDescription | Retry allowed |
|---|
2-07-01 | Declined by external provider | ✅ |
2-07-02 | Insufficient funds on the payer's account | ✅ |
2-07-04 | Received a callback from the provider with a different payment amount and (or) currency | ❌ |
2-07-05 | Transaction rejected by provider | ✅ |
2-07-09 | Currency is not supported | ❌ |
2-07-10 | One or more parameters are invalid | ❌ |
2-07-11 | The value of one or more parameters is invalid | ❌ |
2-07-12 | Unsupported payment method | ❌ |
2-07-13 | Bank country restricted | ❌ |
2-07-14 | Acquirer Malfunction | ✅ |
2-07-15 | Deposit request expired. Create a new deposit request | ❌ |
2-07-16 | No eligible payment channel available | ✅ |
2-07-17 | External service communication error | ✅ |
2-07-18 | Country is not supported | ✅ |
2-07-19 | Transaction limit exceeded | ✅ |
2-07-20 | Payment instruments limit exceeded | ✅ |
2-07-21 | Processing Error | ✅ |
2-07-22 | No payment methods available | ✅ |
Payment Participant Actions (2-08-XX)
| statusCode | statusDescription | Retry allowed |
|---|
2-08-01 | Cancelled by merchant's customer | ❌ |
2-08-02 | Timeout occurred while waiting for the merchant's customer to confirm the required data on the provider's page | ❌ |
2-08-03 | The user did not complete the payment | ❌ |
2-08-04 | Rejected by merchant's request | ❌ |
Card Processing (2-09-XX)
| statusCode | statusDescription | Retry allowed |
|---|
2-09-01 | Invalid card number | ❌ |
2-09-02 | Invalid expiry date | ❌ |
2-09-03 | Invalid card security code | ❌ |
2-09-04 | Expired card | ❌ |
2-09-05 | Card lost/stolen | ❌ |
2-09-06 | Card BIN is blocked | ❌ |
2-09-07 | Unsupported BIN | ❌ |
2-09-08 | Unsupported card scheme | ❌ |
2-09-09 | The provider could not find a card scheme for the provided BIN value | ❌ |
2-09-10 | Card country is not supported | ❌ |
2-09-11 | Card country restricted | ❌ |
2-09-14 | Card is blocked or inactive | ❌ |
2-09-15 | Unsupported card | ❌ |
2-09-16 | PIN attempt limit exceeded | ❌ |
Wallet Errors (2-10-XX)
| statusCode | statusDescription | Retry allowed |
|---|
2-10-01 | Invalid wallet ID | ❌ |
Payout Processing (2-11-XX)
For the codes in this group, the Retry allowed column indicates whether a payout retry is allowed.
| statusCode | statusDescription | Retry allowed |
|---|
2-11-01 | Insufficient funds on the external provider's account | ❌ |
2-11-02 | Insufficient funds on the merchants's account | ✅ |
2-11-03 | Customer account not registered | ❌ |
2-11-04 | Beneficiary name doesn't match bank details | ❌ |
2-11-05 | Withdrawal expired | ❌ |
2-11-06 | Bank account blocked | ❌ |
2-11-07 | Bank account is closed | ❌ |
2-11-08 | Payout method temporary unavailable | ❌ |
Acquirer Status Codes (3-XX-XX)
These codes indicate declines that originated on the acquirer side: the bank, the card issuer, or the payment system. They are set based on the decline details reported by the provider.
Bank Processing (3-01-XX)
| statusCode | statusDescription | Retry allowed |
|---|
3-01-01 | General decline by bank | ✅ |
3-01-02 | General fraud suspect by bank | ✅ |
3-01-03 | Bank connection failed | ✅ |
3-01-04 | Bank connection timeout | ✅ |
3-01-05 | Transaction expired at bank | ✅ |
3-01-06 | Duplicate transaction | ✅ |
3-01-07 | Transaction not supported by bank | ✅ |
3-01-08 | Payment method not supported by bank | ✅ |
3-01-09 | Transaction is сancelled by customer | ❌ |
3-01-10 | Payment crediting error | ❌ |
3-01-11 | Transaction confirmation not received by credit side | ❌ |
3-01-12 | Transaction expired at internet banking login page | ❌ |
3-01-13 | Merchant’s customer failed to provide the necessary info at internet banking login page | ❌ |
3-01-14 | Сancelled by merchant’s customer at bank login page at internet banking login page | ❌ |
3-01-15 | Payment session expired | ❌ |
3-01-16 | Merchant’s customer failed to provide the necessary info at bank at account selection page | ❌ |
3-01-17 | Сancelled by merchant’s customer at account selection page at bank at account selection page | ❌ |
3-01-18 | Сancelled by merchant’s customer at confirmation page | ❌ |
3-01-19 | Merchant’s customer failed to provide the necessary info at TAC request page | ❌ |
3-01-20 | Сancelled by merchant’s customer at TAC request page | ❌ |
3-01-21 | Transaction expired at bank at confirmation page | ❌ |
3-01-22 | Merchant’s customer failed to provide the necessary info at confirmation page | ❌ |
3-01-24 | Transaction not found | ❌ |
3-01-99 | Unknown internal error by bank | — |
Card Processing (3-02-XX)
| statusCode | statusDescription | Retry allowed |
|---|
3-02-01 | Transaction declined by issuer | ✅ |
3-02-02 | Cardholder limit exceeded | ✅ |
3-02-03 | Transaction blocked by issuer | ✅ |
3-02-04 | Issuer unavailable | ✅ |
3-02-05 | Issuer limits are reached | ✅ |
3-02-06 | Transaction not permitted for cardholder | ❌ |
3-02-07 | General fraud suspect by issuer | ✅ |
3-02-08 | Issuer technical error | ✅ |
3-02-09 | Insufficient funds on the payer's account | ✅ |
3-02-10 | Card is blocked or inactive | ❌ |
3-02-11 | Card lost/stolen | ❌ |
3-02-12 | Expired card | ❌ |
3-02-13 | Invalid card security code | ❌ |
3-02-14 | Card restricted by issuer | ✅ |
3-02-15 | Invalid email | ❌ |
3-02-16 | Invalid card number | ❌ |
3-02-17 | PIN attempts limit exceeded | ❌ |
3-02-18 | The bank has requested a retry of the transaction | ✅ |
3-02-19 | 3DS failed | ✅ |
3-02-20 | 3DS general timeout | ✅ |
3-02-21 | 3DS authentication failed | ✅ |
3-02-22 | Card number in blacklist | ✅ |
3-02-23 | Email in blacklist | ✅ |
3-02-24 | Unsupported card brand | ✅ |
3-02-25 | Restricted Currency | ✅ |
3-02-26 | Phone in blacklist | ✅ |
3-02-27 | Cardholder name is invalid | ❌ |
3-02-28 | The same card is used by different customers | ✅ |
3-02-99 | Unknown internal error by the issuer | ✅ |
Payment System Processing (3-03-XX)
| statusCode | statusDescription | Retry allowed |
|---|
3-03-01 | Transaction not found | ❌ |
3-03-02 | One or more fields have invalid data format | ✅ |
3-03-03 | Invalid signature | ✅ |
3-03-04 | Transaction Timeout | ✅ |
3-03-05 | Duplicate request | ❌ |
3-03-06 | Transaction amount below minimum limit | ❌ |
3-03-07 | Transaction is сancelled by merchant’s customer | ❌ |
3-03-08 | Insufficient permissions | ❌ |
3-03-09 | Duplicate transaction | ❌ |
3-03-10 | Bank is blocked | ❌ |
3-03-98 | Payment system temporary unavailable | ✅ |
3-03-99 | Unknown internal error by the payment system | ✅ |
Acquirer Processing Errors (3-04-XX)
| statusCode | statusDescription | Retry allowed |
|---|
3-04-01 | General decline by acquirer | ❌ |
3-04-02 | General fraud suspect by acquirer | ✅ |
3-04-03 | Bad Request by acquirer | ✅ |
3-04-04 | The operation was timed out by acquirer | ✅ |
3-04-05 | Acquirer technical error | ✅ |
3-04-06 | Acquirer limits are reached | ✅ |
3-04-07 | Card country is not supported | ❌ |
3-04-08 | Unsupported card | ❌ |
3-04-09 | Unsupported bank | ❌ |
3-04-10 | Invalid card number | ❌ |
3-04-11 | Invalid expiry date | ❌ |
3-04-12 | Invalid cardholder name | ❌ |
3-04-13 | Wrong request. Invalid parameter format | ✅ |
3-04-14 | One or more parameters are invalid | ❌ |
3-04-15 | Transaction declined by Acquirer: Business Rules | ✅ |
3-04-16 | Invalid card details | ✅ |
3-04-17 | Unsupported card scheme | ✅ |