Status Codes
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 |
Scenario Codes
The scenario code is shared across all sources. For example, 1-02-XX and 2-02-XX are both Request Validation, but on the System and 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) |
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:
- Orders: Retrieve Order Details and Order Status Callback.
- Payouts: Retrieve Payout Status and Payout Status Callback.
- P2P transactions: Retrieve P2P Transaction Status and P2P Status Callback.
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 |
|---|---|
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 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-99 | General error |
Request Validation (1-02-XX)
| statusCode | statusDescription |
|---|---|
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 |
|---|---|
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 |
|---|---|
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 |
|---|---|
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 |
Payment Participant Actions (1-08-XX)
| statusCode | statusDescription |
|---|---|
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 |
|---|---|
2-01-01 | General decline |
2-01-02 | The operation was timed out by the provider |
2-01-99 | Unknown internal error by the provider |
Request Validation (2-02-XX)
| statusCode | statusDescription |
|---|---|
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 |
3DS Checks (2-04-XX)
| statusCode | statusDescription |
|---|---|
2-04-01 | 3DS general timeout |
Antifraud (2-05-XX)
| statusCode | statusDescription |
|---|---|
2-05-01 | General fraud suspect |
2-05-02 | Compliance limitation |
2-05-03 | The amount limit has been exceeded |
2-05-04 | Email is in the blacklist |
2-05-05 | IP is in the blacklist |
2-05-06 | Cardholder is in the blacklist |
2-05-07 | Billing country is in the blacklist |
2-05-08 | Billing account is suspended |
Limits Control (2-06-XX)
| statusCode | statusDescription |
|---|---|
2-06-01 | Provider limit on the total amount of transactions has been exceeded |
Payment Processing (2-07-XX)
| statusCode | statusDescription |
|---|---|
2-07-01 | Declined by external provider |
2-07-02 | Insufficient funds on the payer's account |
2-07-03 | Cardholder limit exceeded |
2-07-04 | Received a callback from the provider with a different payment amount and (or) currency |
Payment Participant Actions (2-08-XX)
| statusCode | statusDescription |
|---|---|
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 |