Errors
In the course of interacting with PaymentsAI, you may encounter various error codes that indicate issues with your requests. These errors are designed to provide specific feedback about what went wrong, enabling you to quickly identify and resolve issues.
Each error code is accompanied by a detailed description, the type of error, the underlying problem, and suggested solutions to help you address the issue effectively. Understanding these error codes will ensure smoother integration and operation of your applications with PaymentsAI.
400 Bad request
HTTP Status Code | 400 |
Type | Bad request |
Problem | Your payload is incorrect (wrong data) |
Solution | In most cases, the problem is with the request itself. Please verify your payload with our OpenAPI docs |
{
"errorCode": "string",
"statusCode": 400,
"message": "Bad request",
"details": "string"
}
401 Missing auth token
HTTP Status Code | 401 |
Type | Missing auth token |
Problem | PaymentsAI can't authenticate you with the information provided |
Solution |
|
{
"errorCode": "string",
"statusCode": 401,
"message": "Missing auth token"
}
403 Forbidden access
HTTP Status Code | 403 |
Type | Forbidden access |
Problem | PaymentsAI recognizes your credentials, but you don't have permission to access this resource |
Solution | Please contact support |
{
"errorCode": "string",
"statusCode": 403,
"message": "Forbidden access"
}
413 Request Entity Too Large
HTTP Status Code | 413 |
Type | Request entity too large |
Problem | The request payload is too large for the server to process |
Solution |
|
{
"errorCode": "string",
"statusCode": 413,
"message": "Request entity too large"
}
429 Too many requests
HTTP Status Code | 429 |
Type | Too many requests |
Problem | You have sent too many requests in a given amount of time, exceeding the rate limits set by PaymentsAI |
Solution |
|
{
"errorCode": "string",
"statusCode": 429,
"message": "Too many requests"
}
500 Internal server error
HTTP Status Code | 500 |
Type | Internal server error |
Problem | An unexpected error occured on the server |
Solution | Try the request again later. If the issue persists, please contact support |
{
"errorCode": "string",
"statusCode": 500,
"message": "Internal server error"
}