HTTP status codes

After submitting an API call to Adyen, you receive a response back to inform you that your request was received and processed. Depending on the HTTP status code of the response, you should build some logic to handle any errors that a request or the system may return.

HTTP responses

Handle 200 responses

An HTTP 200/OK response status code means that the request was submitted correctly and Adyen processed it successfully. An HTTP 200 response does not automatically mean that the payment or the modification request was successfully executed.

When the payment response includes a resultCode with a value of Refused or Error, a refusalReason field is added. Check the refusal reason messages to learn more about the possible issues of the payment or the modification request.

For example:

• You send a capture payment request.

• The response to your capture request returns HTTP 200/OK. This means:

  • We received your request.
  • We will execute a payment capture.
  • We still do not know if the capture operation will be successful or not.
  • We'll let you know in the corresponding webhook event.
• If the capture operation fails, for example, because the acquirer declines to accept the shopper's card, the payable amount for the transaction is not collected.

• Based on your settings, you'll receive a webhook message that includes the information about this capture example:

  • The  pspReference in this notification is the same as the  pspReference in the capture modification response.
  • The success field value is false, and the reason field includes a short message to explain the cause of the failure.

Handle 4xx and 5xx responses

In the following scenarios, the plataforma de pagamentos da Adyen does not accept or store submitted requests:

• The request does not pass validation.
• The request violates a security constraint.
• The request violates a configuration constraint.
• An internal error occurs on the plataforma de pagamentos da Adyen.

In these cases, you receive an error message with an error code containing a description of the problem.
In general, you should handle it as an exception.

Debugging APIs

While building your integration into the Adyen APIs, you may need to reach out to us for additional help.

If you contact our Support Team, provide the pspReference returned in the header of the API response. The pspReference is a unique ID for that specific API request, and can be used by our Support Team to identify specific API calls.

Error response fields

In case of an error, the response object contains the following fields: 

The following example shows a possible error response:

{
    "status" : 403,
    "errorCode" : "901",
    "message" : "Invalid Merchant Account",
    "errorType" : "security"
}

For the complete list of error codes and corresponding messages, see Error codes and messages.

See also

• IETF HTTP status code registry
• RFC 2616, section 6.1.1
• HTTP status codes on Wikipedia