{"title":"HTTP status codes","category":"default","creationDate":1779533780,"content":"

After submitting an API call to Adyen, you receive a response to inform you that your request was received and processed. Depending on the HTTP status code of the response, you can build logic to handle errors.<\/p>\n

Requirements<\/h2>\n\n\n\n\n\n
Requirement<\/th>\nDescription<\/th>\n<\/tr>\n<\/thead>\n
Integration type<\/strong><\/td>\nAn online payments<\/a> integration.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

HTTP responses<\/h2>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
HTTP status code<\/th>\nHTTP status message<\/th>\nDescription<\/th>\n<\/tr>\n<\/thead>\n
200<\/a><\/td>\nOK<\/td>\nRequest processed normally. The request message was successfully processed and produced a response. The response message varies, depending on the request method and the requested data.<\/td>\n<\/tr>\n
201<\/a><\/td>\nCreated<\/td>\nThe request was successful and a new resource was created.<\/td>\n<\/tr>\n
202<\/a><\/td>\nAccepted<\/td>\nThe request was accepted, but has not been processed yet. This is not a guarantee that the request will be completed.<\/td>\n<\/tr>\n
204<\/a><\/td>\nNo Content<\/td>\nThe server successfully fulfilled the request, and there is no additional content to send in the response.<\/td>\n<\/tr>\n
301<\/a><\/td>\nMoved Permanently<\/td>\nThe resource you requested moved to a different location.<\/td>\n<\/tr>\n
400<\/a><\/td>\nBad Request<\/td>\nProblem reading or understanding request. The receiving server cannot understand the request because of malformed syntax. Do not repeat the request without first modifying it. Check the request for errors, fix them, and then retry the request.<\/td>\n<\/tr>\n
401<\/a><\/td>\nUnauthorized<\/td>\nAuthentication required. You need to provide valid authentication credentials (username\/password) to access the resource.<\/td>\n<\/tr>\n
403<\/a><\/td>\nForbidden<\/td>\nInsufficient permission to process request. You do not have the appropriate user rights to access the request. Do not repeat the request.<\/td>\n<\/tr>\n
404<\/a><\/td>\nNot Found<\/td>\nFile not found. The server could not retrieve the resource you requested at the specified location. It is possible that the resource becomes available in the future. Usually, this happens when the URL you pass with the request is incorrect. You can make subsequent calls.<\/td>\n<\/tr>\n
405<\/a><\/td>\nMethod Not Allowed<\/td>\nThe target resource does not support this method.<\/td>\n<\/tr>\n
406<\/a><\/td>\nNot Acceptable<\/td>\nThe server could not produce an acceptable response.<\/td>\n<\/tr>\n
408<\/a><\/td>\nRequest Timeout<\/td>\nThe server did not receive a complete request message within a certain amount of time. You can retry the request.<\/td>\n<\/tr>\n
409<\/a><\/td>\nConflict<\/td>\nResource is locked. A conflict occurred because the request was already processed or is in progress. Identify the reason for the conflict and resolve it. You can retry the request if the API returns a transient error header with value true<\/strong><\/span>.<\/td>\n<\/tr>\n
413<\/a><\/td>\nPayload too large<\/td>\nThe body of your request was too large. The maximum request size is 10 MB. Send the request again with a size of less than 10 MB.<\/td>\n<\/tr>\n
422<\/a><\/td>\nUnprocessable Entity<\/td>\nRequest validation error. The request is well-formed (syntactically correct), but semantically incorrect: the receiving server can read the request, but cannot understand it.<\/td>\n<\/tr>\n
429<\/a><\/td>\nToo Many Requests<\/td>\nYou have sent too many requests in a short period. To handle this issue, implement a retry mechanism that uses exponential backoff<\/a> with jitter<\/a>.<\/td>\n<\/tr>\n
500<\/a><\/td>\nInternal Server Error<\/td>\nServer could not process request. The receiving server encountered an unexpected condition that prevents it from fulfilling the request. You can also receive a 500 status code when the request is incorrect, for example because of a missing or empty mandatory field.<\/td>\n<\/tr>\n
501<\/a><\/td>\nNot Implemented<\/td>\nThe server does not support the functionality required to complete the request.<\/td>\n<\/tr>\n
504<\/a><\/td>\nGateway Timeout<\/td>\nThe server, acting as a gateway or proxy, did not get a response from the upstream server in time.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Handle 200 responses<\/h2>\n

Although an HTTP response status code of 200<\/code> means that the request was submitted correctly and Adyen processed it successfully, it does not necessarily mean that the payment or modification request was successfully executed.<\/p>\n

When the payment response includes a resultCode<\/code> with a value of Refused<\/strong><\/span> or Error<\/strong><\/span>, a refusalReason<\/code> field is added. Check the refusal reason messages<\/a> to learn more about the possible issues with payment or modification requests. For example:<\/p>\n