| 200 | OK | The request was successfully processed and returned a response body. |
| 201 | Created | The request was successfully processed and returns the newly created entity. |
| 204 | No Content | The request was successfully processed and the response does not contain a body. |
| 400 | Bad Request | The API understood the message, but it contained invalid or incorrect data in one or more fields. For the specific error you'll need to inspect the response body. This contains a message with an explanation what went wrong. |
| 401 | Unauthorized | The provided credentials are incorrect. |
| 403 | Forbidden | You have successfully authenticated, but are not allowed to access the requested resource. |
| 404 | Not Found | The requested resource does not exist. |
| 409 | Conflict | Some resources are dependent on other resources. Refunds for example are required to be linked to a transaction. The sum of all refunds must not exceed the original transaction amount. Doing so can result in a 409 being returned. |
| 422 | Unprocessable Entity | The request body does not contain valid JSON. |
| 429 | Too Many Requests | You've made too many requests in a short amount of time. |
| 500 | Internal Server Error | This error status is returned when something went wrong on our side. |
| 503 | Service Unavailable | One or more services might not be available. This could indicate an issue with the payment method itself, or our systems. |