The following table defines the HTTP response codes that can be returned to the POS that indicate the outcome of the processing of the HTTP request. In the case of HTTP 4xx/5xx error codes being returned, a JSON payload may also be returned indicating more specific error information. Standard HTTP error codes are applied (but not listed) for connection failures, etc.
HTTP Codes
HTTP Code |
Description |
Internal Code |
Description |
---|---|---|---|
200 |
Request has been successfully processed by the gateway. This does not indicate that, for example, a payment has been authorised. The ResponseCode in the payload response should be interrogated to determine the outcome of the payment. |
N/A |
N/A |
400 |
Incorrect request. |
1000 |
Incorrect request format. |
401 |
Authentication value missing. |
1001 |
Authentication value missing. |
401 |
Authentication failed. |
1002 |
Authentication failed. |
403 |
Transaction not supported. |
1013 |
Transaction not supported. |
404 |
Transaction not found. |
1012 |
Transaction not found. |
500 |
Internal server error. |
9999 |
An internal server error occurred at Opayo. |
Error Response Example
{ "ErrorResponse": { "Code": 9999, "Description": "An internal error occurred at Opayo" } }