Errors
Plutu provides a list of error codes and messages for troubleshooting payment integration issues.
Plutu uses HTTP response status codes to indicate the success or failure of an API request. In general: Codes in the 2xx range indicate success. Codes in the 4xx range indicate an error that failed given the information provided (e.g., a required parameter was omitted, etc.). Codes in the 5xx range indicate an error with Plutu's servers (these are rare).
Some 4xx errors that could be handled programmatically (e.g., an invalid gateway) include an error code—a short string with a brief explanation—as a value for code. Below is a list of possible error codes that can be returned.
200
401 -403 -404 -422 -429
500- 502 -503 - 504 - Server Error
200 - OK
indicates that the request has succeeded, and everything works as expected.
400 - Bad Request
indicates that the server cannot or will not process the request.
401 - Unauthorized
indicates that the client request has not been completed because it lacks valid authentication credentials for the requested resource. An invalid access token/API key was provided.
403 - Forbidden
indicates that the server understands the request but refuses to authorize it. API key doesn't have permission to perform the request.
404 - Not Found
The requested resource doesn't exist.
422 - Un-processable Entity
Invalid fields will result in a 422 Unprocessable Entity response.
429 - Too Many Requests
indicates the user has sent too many requests in a given amount of time.
500, 502, 503, 504 - Server Errors
Something went wrong on Plutu's end. (These are rare).
REVIEWING ERRORS
To monitor your integration and review errors, Plutu logs every API request your integration makes, whether it was successful or failed. You can access the logs section of the Dashboard under Gateways to review these errors.
General Errors
General errors are a type of error that can occur when using a payment gateway integration. They are not specific to any particular endpoint or gateway and can be caused by a variety of issues such as incorrect input data, network connectivity problems, or errors with the integration itself. It's important to review these errors and understand their root cause in order to address them and ensure the smooth functioning of your payment gateway integration.
Sadad Errors
The following errors, as well as General Errors, can be returned.
Adfali Errors
The following errors, as well as General Errors, can be returned.
Local Bank Cards
There are no errors for Local Bank Cards, Only the General Errors can be returned
Lightbox Errors
On the checkout page (Lightbox), service providers may return error messages that are not specific to Plutu API. Here is an explanation for those error messages.
T-Lync Errors
There are no errors for T-Lync, Only the General Errors can be returned
MPGS Errors
The following errors, as well as General Errors, can be returned.
Last updated