![[ECRYPT]](https://files.readme.io/a033422-Ecrypt-Logo-ecrypt.svg){kind=link}
Response Codes
Response codes tell you whether payment flow functions are successful or if something went wrong. If a payment flow fails then certain response codes will tell you what happened and help you resolve the error.
Response Codes
| HTTP Response Code | Description | More Info |
|---|---|---|
| 200 - OK | Everything worked as expected. | |
| 400 - Bad Request | The request was unacceptable, often due to missing a required parameter. | |
| 401 - Unauthorized | No valid API key provided. | |
| 402 - Request Failed | The parameters were valid but the request failed. | |
| 403 - Forbidden | The API key doesn't have permissions to perform the request. | |
| 404 - Not Found | The requested resource doesn't exist. | |
| 409 - Conflict | The request conflicts with another request (perhaps due to using the same idempotent key). | |
| 429 - Too Many Requests | Too many requests hit the API too quickly. We recommend an exponential backoff of your requests. | |
| 500, 502, 503, 504 - Server Errors | Something went wrong on PreferredPayments's end. (These are rare.) |
Updated about 1 year ago
Enhanced Data
PGP Key
Copy Page