This page describes the possible error codes you may encounter with your transactions. Some of these error messages are only returned if for specific integrations.
Error message not always available
Please note some special errors do not contain any detailed error message. Whenever available, we return a human-readable error message.
Probably the most common error of all, your transaction was declined. This can have various reasons. Please refer to the error message for more details.
3DS 2.0 requires this transaction to do a 3D Secure authentication to complete the authorization. Please note that this error will only be returned if you are processing transactions with 3DS 2.
An unknown error occurred. This should not be returned. If you encounter such an error, please contact us and provide the
transactionId of that transaction.
merchantId is not authorized to access this API endpoint.
The performed action cannot be done for this specific
transactionId. For example, if you try to settle an already settled transaction.
transactionId you are trying to process cannot be found. Either it is inexistent or it belongs to a different
The syntax of your JSON payload is wrong.
JSON payload contains an unrecognized property.
A property with the JSON payload has a wrong format.
We return this error when there is no specific error code available related to your request. For example when using
GET instead of
We return this error when there was an error on our side.
The card is expired.
The card number is invalid.
The card is blocked.
merchantId does not support this card brand.
The token is invalid.
The card security code is invalid.
You are trying to use a
refno that was used previously. Please try again with a unique
We return this error if at least 20 wrong tokens were used in the past 15 minutes.
merchantId seems to have a setup issue. Please contact us for more details.
The sign value is wrong. This error message is part of our Legacy APIs and is no longer returned in newer integrations.
Updated about a month ago