HTTP Status Codes
This table lists the HTTP response codes that may be returned by the Checkout API, along with explanations and suggested actions.
🟠 400
Bad Request
The request cannot be processed due to incorrect syntax or missing fields.
Verify that all required parameters are included and correctly formatted.
🟠 401
Unauthorized
The access token is missing, invalid, or expired.
Generate a valid token and ensure it is sent in the Authorization header.
🟠 403
Forbidden
Access is denied for this IP or authentication data.
Check that the project is active, properly configured, and that your IP is whitelisted.
🟣 404
Not Found
The requested resource does not exist.
Verify the endpoint URL and resource identifiers (e.g., checkoutId).
⚪ 405
Method Not Allowed
The HTTP method (GET, POST, etc.) is not allowed for this endpoint.
Ensure the request method matches the specification.
🟡 409
Conflict
A conflict occurred (e.g., duplicate data or invalid state transition).
Review your request logic to prevent duplicates or invalid state changes.
🟠 415
Unsupported Media Type
The request body format is invalid.
Make sure the Content-Type header is application/json and the payload is valid JSON.
🟠 422
Unprocessable Entity
The request format is valid, but data content is logically inconsistent.
Validate the semantic correctness of your parameters (e.g., amount, currency).
🟡 429
Too Many Requests
Too many requests were sent in a short time.
Implement retry logic with exponential backoff and consider rate-limiting.
🔴 500
Internal Server Error
An unexpected system error occurred.
Retry after a few seconds; if it persists, contact technical support with logs.
🔴 503
Service Unavailable
The service is temporarily unavailable due to overload or maintenance.
Wait a few minutes and retry. Check system status or contact support if ongoing.
Last updated