Rejection codes
How to know the rejection error
In the case of rejected transactions, you can find out the reason for rejection from the error_details field.
This field includes several elements with information about the reason why the issuing bank rejected the transaction.
{
"error_code":"05",
"error_description":"Transaction has been declined.",
"error_code_scheme":"59",
"error_description_scheme":"Suspected Fraud",
"error_unified":"SUSPECTED FRAUD"
}
It is possible that the error_unified is set to null. This can happen if the error returned by the issuing bank/brand (VISA, Mastercard,...) is not documented on their side and therefore does not have an associated code in Paylands.
| List of errors | Description |
|---|---|
| INVALID_MERCHANT | The trade sent is not valid (possibly the tpv has been deactivated by the acquirer) |
| UNSPECIFIED_REFUSAL | Generic rejection code. Generally means that the user has no funds on the card |
| EXPIRED_CARD | |
| SUSPECTED_FRAUD | |
| PIN_TRIES_EXCEEDED | In a 3DS authentication, the user has exceeded the maximum number of attempts to enter the PIN |
| INVALID_CARD_NUMBER | Incorrect card number |
| CVV_FAILURE | |
| AUTHENTICATION_FAILURE | The user has not been able to complete the 3DS correctly |
| DUPLICATED_OPERATION | |
| INSUFFICIENT_FUNDS | Insufficient balance. Some card issuers mask this error as UNSPECIFIED_REFUSAL |
| INVALID_EXPIRE_DATE | |
| CLOSED_ACCOUNT | The bank account associated to the card has been terminated |
| INVALID_AMOUNT | The card does not support a transaction for the given amount |
| CARD_LOST_OR_STOLEN | |
| INVALID_CURRENCY | The card does not support the currency used |
| EXCEEDS_AMOUNT_MAX_LIMIT | |
| RESTRICTED_CARD | |
| TIMEOUT | |
| FORMAT_ERROR | |
| INVALID_TRANSACTION_DATE | |
| INVALID_TRANSACTION | |
| PICK_UP_CARD | |
| INVALID_PIN | |
| TRANSACTION_NOT_ALLOWED_FOR_CARD | |
| SECURITY_VIOLATION | |
| CARD_STILL_NOT_OPERATIONAL | |
| CARD_NOT_SUPPORTED_BY_THE_SYSTEM | |
| INVALID_SESSION | Session token error |
| NOT_ACCEPTED_REFUND | |
| PIN_REQUIRED | PIN_REQUIRED - User PIN entry required |
In the case of merchants with multi-acquiring services, rejected transactions will include an error_details field including information on the reason for rejection and a unified error code bringing together the equivalent error codes among the different acquirers.
| error_code | Error code returned by the issuer |
| error_description | Descriptive text associated to the error_code |
| error_code_scheme | Error code returned by the schemes(VISA, MC, ...) |
| error_description_scheme | Descriptive text associated to the error_code_scheme |
| error_unified | Text string associated with the error_code_scheme field. In case of multi-acquirers, this field will contain the same value for the same reason for rejection among the different acquirers |
It is possible that the error_code_scheme field contains two error codes separated by a comma. The second one refers to the fact that the card brand rejected the transaction but gave additional info on how to proceed depending on the following codes:
| 01 | Additional information required |
| 02 | Retry later |
| 03 | Do not retry |
| 21 | Payment cancelled |
If the card was Mastercard, the transaction can be reattempted after 30 days. In the case of VISA, the transaction cannot be reattempted.