List of error codes, states and sub-states.
List of codes states and sub-states.
A list of codes states and sub-states and their descriptions will be listed below in Table 1.
These states and sub-states are returned in the response to the pay method.
Table 1 - List of codes states and sub-states
| States | Sub-states | Final | Description |
|---|---|---|---|
| 0 | 0 | No | New. Status in which payments are inserted into the database |
| 0 | 1 | No | Ready for processing. Preparing for processing and transferring to the queue |
| 0 | 2 | No | Provider identification. Identification of the provider according to the directions of Payment Processing |
| 0 | 3,4 | No | Fraud-control. Fraud-control status, if the control system is enabled, payments are added to this status |
| 0 | 5 | No | Confirmation. Status in which payments are loaded to the cabinet via the “Control room - Loading payments” section. Payments will be in it until the user confirms the processing (the “Carry out all pending” button) |
| 0 | 6 | No | Provider is not specified. This status includes payments for services for which the direction of payment is not defined. |
| 0 | 7 | No | Timeout. Status, in which payments will fall for the time specified in the service settings as a deferral of payments. |
| 0 | 8 | No | Pending. Payment status in case the “Use pending” setting is enabled at the provider. Will be in it until manual processed |
| 0 | 9 | No | Pending confirmation. This status is assigned to a payment received from an external gateway (external) with the 'delayed' flag. The payment remains in this status until the external system sends its confirmation |
| 0 | 11 | No | Remuneration is not set. This status includes payments for services that are not added to the remuneration profile. |
| 10 | Any | No | Payment blocked (as a result of application of Fraud monitoring rules) |
| 20 | 1 | No | Ready to be written off |
| 20 | 2 | No | Preliminary verification, in process |
| 20 | 3 | No | Preliminary verification, unknown. The verification ended with an ambiguous error. After the global timeout period (1 day) expires, the operation is moved to the 'Processing' status (40) with the 'Error' substatus (4) to release the reserved funds, and then transitions to the final status |
| 20 | 4 | No | Insufficient funds in the account |
| 30 | No | Preliminary payment verification | |
| 30 | 1 | No | Ready for pre-verification (by pre-verification modules) |
| 30 | 2 | No | Preliminary verification, in processing |
| 30 | 3 | No | Preliminary verification, unknown. The verification ended with an ambiguous error. After the global timeout period (1 day) expires, the operation is moved to the 'Processing' status (40) with the 'Error' substatus (4) to release the reserved funds, and then transitions to the final status 'Error' with the substatus 'Rejected by provider' (5) |
| 30 | 4 | No | This status is assigned to operations that failed the preliminary verification module check, provided that the 'Manual control' option is enabled for the module. The operation remains in this status either until the global timeout period (5 days) expires or until it is manually moved to another status. After the timeout expires, the operation is first moved by the gateways to the 'Processing' status (40) with the substatus 'Error' (4) to return the reserve to the agent, and then to the final status 'Error' with the substatus 'Rejected by provider' (5). Manually, the operation can be transferred to the 'Processing' status (40) with the substatus 'Ready for processing' (0) — in which case the operation will proceed with processing — or to the 'Verification' status (30) with the substatus 'Blocked. Canceled' (5) |
| 30 | 5 | No | Payments can be transferred to this status only manually from the “Processing” status (40) of the "Blocked. Canceled" (4). Payments in this status are first transferred by gateways to the “Processing” status (40) of the “Error” substatus (4) to return the reserve to the agent, and then to the final ‘Error’ status of the “Rejected at provider” substatus (5). |
| 40 | 1 | No | Ready for processing |
| 40 | 2,3 | No | Processing |
| 40 | 4,5,6,7 | No | Processing error |
| 40 | 8 | No | A response from an external vendor is pending |
| 40 | 9 | No | Waiting for confirmation from the external system |
| 40 | 10 | No | Waiting for missing attributes required to complete the processing (for operations in burst status) |
| 60 | Yes | Successful implementation status (final) | |
| 80 | Yes | Error status (final) | |
| 80 | 1,2,3 | Yes | Payment canceled manually |
| 80 | 4 | Yes | Insufficient funds in the account |
| 80 | 5 | Yes | Processing error |
| 80 | 6,7,8 | Yes | Another mistake |
| 80 | 9 | Yes | Refund |
| -1 | 0 | No | Error of inserting operation into database (not final) |
| -2 | 0 | Yes | Payment not found at status check (final) |
| 0 | 0 | No | New. Status in which payments are inserted into the database |
List of error codes.
Error codes from this list are returned in the response to the pay method in the code field.
Table 2 - List of error codes
| Error code | Description |
|---|---|
| -100 | Duplicate attributes transferred |
| -2 | Payment Instrument Error |
| 1,2 | Incorrect number |
| 3 | Amount out of acceptable range |
| 4 | Provider's server is unavailable |
| 5 | Authorization error |
| 6 | The operator's server is unavailable |
| 7 | General provider error |
| 8 | Lack of funds |
| 9 | Incorrect processing parameters |
| 10 | Fatal provider error |
| 30 | Insufficient funds to add payment |
| 33 | Service is not available for this merchant |
| 50 | Duplicate attributes transferred |
List of error codes.
Error codes from this list are returned in the response to the pay method in the code field.
Table 2 - List of error codes of the service attribute in the advanced request
Error codes in query responses using the advanced method
Table 3 - List of error codes
| Error code | Description |
|---|---|
| 0 | Successful |
| 1 | No data on the specified details found |
| 2 | Prohibition of payment for the specified number by the service provider |
| 3 | Unable to parse the vendor's response. Try again later |
| 4 | Online requests are not implemented for this service |
| 5 | No arrears |
| 6 | One of the arguments is missing or incorrect |
| 7 | There are too many items for the specified search conditions. Refine the query parameters |
| 8 | No records were found for the specified search terms. Change the search terms |
| 9 | Some error with text description. The text description is returned in the message element:<input key="message" value="It is necessary to perform card recovery"/> |
| 10 | Failed to perform the check. Independently decide whether to continue or stop processing the payment |
| 11 | Payment is not possible due to lack of personal data from the operator |
| 100 | Insufficient funds on the balance to complete the request |