Error handling
When processing transactions on our platform, you will face the task to handle possible errors. Depending on your request, you might encounter errors related to:
Missing/wrong properties in your request,
Wrong API endpoint your request is sent to,
A potential technical issue on our platform.
To help you understand and handle these errors, we walk through the most common ones and provide our recommendations.
HTTP response codes
Our API uses standard HTTP response codes to provide high-level feedback regarding your request to our system.
HTTP Response Code Ranges
Understanding the significance of HTTP response codes is crucial for effective interaction with the API. Below, you can explore the different response code ranges and their implications:
2xx range : Successful responses, indicating that we were able to process your the request.
4xx range : Client error responses, signifying issues with your request. These are generally fixable by you.
5xx range : Server error responses, indicating a problem on our side or with one of the 3rd parties involved in processing your request.
A request returning a response in the 2xx range, could have resulted in a declined request. For example, authorization declines being returned by the card issuer, are considered successfully processed by us. It is important to always check the responseCode returned inside the response body of any 2xx response..
HTTP Response Code overview
The Acquiring API can return one of the following HTTP response codes:
HTTP response code |
Meaning |
Description |
|---|---|---|
200 |
Successful |
Your request was processed correctly. |
201 |
Created |
Your request was processed correctly, and a new resource was created. The URI of this created resource is returned in the Location header of the response. |
204 |
No content |
Your request was processed correctly, but no response is returned. |
400 |
Bad request |
Your request is not correct and cannot be processed. Please correct the mistake and try again. |
401 |
Unauthorized |
You do not have sufficient permissions to perform this request. |
403 |
Forbidden |
You are trying to do something that is not allowed. |
404 |
Not found |
The object you were trying to access could not be found on the server. |
405 |
Method Not Allowed |
You are using an HTTP Method (POST, PUT, GET, DELETE) that isn't allowed for that endpoint. |
409 |
Conflict |
Your request resulted in a conflict. Either you submitted a duplicate request or you are trying to do an action that is not possible due to the object status. |
500 |
Internal server error |
Something went wrong on our end. |
502 |
Bad gateway |
We were unable to process a message from a downstream system. |
503 |
Service unavailable |
The service that you're trying to reach is temporarily unavailable. Please try again later. |
Make sure your application can handle HTTP error codes not included in this list.