Response codes
Use Checkout's response codes to determine the status of your transactions.
HTTP status codes
The RESTful Checkout API uses conventional HTTP status codes to describe the success or failure of requests
| Response code | Description |
|---|---|
| 200 | Request successfully processed. |
| 307 | Temporary redirect. |
| 400 | Bad request. Request failed because of missing or invalid parameters. Also returned if the payment failed, for example, if the acquirer declined the transaction. |
| 403 | Authentication details are valid but do not provide enough permissions to access the requested resource. |
| 404 | The requested resource or endpoint cannot be found, that is, the endpoint or URL does not exist. This can also be caused by typos or wrong IDs, for example, GET /v1/payments/{id} where no payment with {id} exists. |
Result codes
The result codes are part of the response body's JSON (field result) containing a code and a description explaining the code.
| Result code | Description |
|---|---|
| 000.000.000 | Transaction succeeded |
| 000.100.110 | Request successfully processed in Merchant in Integrator Test Mode |
| 000.200.000 | transaction pending |
| 000.200.100 | Successfully created checkout (indicates that the session is now open) |
| 100.396.101 | Cancelled by user |
| 100.396.104 | Uncertain status - probably cancelled by user |
| 200.300.404 | invalid or missing parameter |
| 600.200.400 | Unsupported Payment Type (only DB is allowed as a payment type) |
| 600.200.500 | Invalid payment data. You are not configured for this currency of sub type |
| 800.100.152 | Transaction declined by authorization system |
| 800.900.201 | Unknown channel (entity ID in payment request is incorrect) |
| 800.900.300 | Invalid authentication information (authentication password is incorrect) |
Updated 23 days ago