Failed Payment Response Guide
Thailand
MasterCard and Visa Card Payments
Successful Payments
Payment Response (Code) | CAPTURED, 00 | |
Payment Reason (Code) | Success | |
Subscription Invoice Status** | Active | |
Invoice Status | Paid | |
Transaction Status | Success | |
Payment Provider Response (Description) | CAPTURED, Success 00: Approved and completed successfully | |
Payment Reason (Description) | The transaction was successful. | |
Payment Method Invalid? | Valid | |
What It Means | The transaction was successful. Payments will continue as scheduled. | |
Suggested Actions (For Integrators) | N/A | |
Suggested Actions (For Merchants) | N/A | |
Suggested Actions (For Customers) | N/A |
** Only available to integrators on subscription model.
Failed Payments - Fund Issues
Payment Response Code | INSUFFICIENT_BALANCE 51 | 61,65, N4 |
Payment Response | Insufficient_funds | limit_exceeded |
Subscription Invoice Status** | Inactive | INACTIVE |
Invoice Status | Past_Due | Past_Due |
Transaction Status | Failed | Failed |
Payment Provider Response (Description) | INSUFFICIENT BALANCE: The card you are trying to capture does not have enough balance to complete the capture 51: Insufficient funds | Limit exceeded |
Failed Payment Reason (Description) | Payment method has insufficient funds at the time of the transaction. | Transaction exceeded the customer’s payment method daily withdrawal or activity limit. |
Payment Method Status | Valid | Valid |
What It Means | At the time of the transaction, the customer did not have enough funds to cover the transaction.
Sometimes, the bank will send us this reason code when they’ve identified fraudulent activity or transactions which are outside of the customer’s regular spend pattern.
The risk rules of the customer bank are outside of our control. The vast majority of transactions that generate this response code are due to genuine insufficient funds.
Payments will stop if maximum failed attempts have been reached. | The customer or customer’s bank has imposed spend limits.
Payments will stop if maximum failed attempts have been reached. |
Suggested Actions (For Integrators) | You can retry the transaction on a later date without having to recreate the payment method, but we would suggest not retrying on the same day. | You can retry the transaction on a later date without having to recreate the payment method, but we would suggest not retrying on the same day. |
Suggested Actions (For Merchants) | You can retry the transaction on a later date, but we would suggest not retrying on the same day as it’s unlikely that the customer would have enough funds available within the same day. | You can retry the transaction on a later date, but we would suggest not retrying on the same day. |
Suggested Actions (For Customers) | Please ensure there are enough funds in your account before the due date of the next transaction. | Please increase the daily transaction limit on your account, or let the business know when another attempt can be made. |
** Only available to integrators on subscription model.
Failed Payments - Bank Issues
Payment Response Code | DECLINED_BY_ISSUER INACTIVE_OR_UNAUTHORIZED_CARD 01, 02, 03, 05, 06, 10, 13, 21, 30, 39, 42, 52, 53, 55, 63, 70, 75, 78, 79, 80, 84, 86, 87, 89, 1A, R2, Z3, 5C, 9G. |
Payment Response | customer_to_contact_bank |
Subscription Invoice Status** | Inactive |
Invoice Status | Past_Due |
Transaction Status | Failed |
Payment Provider Response (Description) | DECLINED_BY_ISSUER: Payment was declined by the issuer with no additional information provided to Xendit. Ask your customer to contact issuing bank. Alternatively, they can try using different card or other form of payment INACTIVE_OR_UNAUTHORIZED_CARD: Payment was declined by the issuer because card is not authorized for online transactions. Recommend cardholder to contact their card issuing bank to resolve the problem on online transaction. Alternatively, they can try to use a different card or other form of payment. 01: Refer to card issuer |
Failed Payment Reason (Description) | Transaction rejected by customer’s bank. Please use a different payment method or contact your issuing bank. |
Payment Method Status | Valid |
What It Means | Due to some rules that the customer’s bank applies, the transaction is rejected.
The bank could have set up rules around duplicate detection, fraud or velocity that might have triggered the rejected transaction.
Some of these rules apply when the customer has reached their spend limit for the day.
Payment stops immediately until issue is resolved. |
Suggested Actions (For Integrators) | Please confirm with the business or customer what the payment method should be.
Do not attempt to retry the transaction until the payment method token has been recreated.
Once the payment method token has been recreated, you can schedule a retry. |
Suggested Actions (For Merchants) | Ask the customer to contact their bank to ask why the transaction failed.
Until the matter is resolved between the customer and their bank, the transaction response will likely be the same, therefore we recommend that you request a different payment method. |
Suggested Actions (For Customers) | The bank has rejected the transaction. Please contact your bank for the reason as to why the transaction had failed.
This will need to be resolved first before transactions can continue to be debited from this account. Or you can provide the business with an alternate payment method. |
** Only available to integrators on subscription model.
Failed Payments - Card Issues
Payment Response Code | INVALID_CARD 12, 14, 15, 62, 82, 92 | EXPIRED_CARD, 54 | 46 |
Payment Response | Invalid_payment_method | expired_card | bank account closed |
Subscription Invoice Status** | Inactive | Inactive | Inactive |
Invoice Status | Past_Due | Past_Due | Past_Due |
Transaction Status | Failed | Failed | Failed |
Payment Provider Response (Description) | INVALID CARD:Payment was declined by the issuer because incorrect card information being provided. Recommend cardholder to review the card information and try again. Alternatively, they can try to use a different card or other form of payment. 12: Invalid transaction | The card you are trying to capture is expired. Ask your customer for a different card. | Closed amount |
Failed Payment Reason (Description) | Payment method details are invalid. Please use a different payment method. | EXPIRED CARD: The credit card has expired. Please use a different payment method. 54: Expired card | The bank account has been closed. Please use a different payment method. |
Payment Method Status | Invalidated | Invalidated | Invalidated |
What It Means | The card number is incorrect and the bank is unable to match the details to any particular account.
Payment stops immediately until issue is resolved. | Expired card. Payment stops immediately until issue is resolved.
Payment stops immediately until issue is resolved. | Applies for Visa. The account is closed. Re-validate the account number for accuracy and do no treattempt with the same PAN or token.
Payment stops immediately until issue is resolved. |
Suggested Actions (For Integrators) | Please confirm with the business or customer what the payment method should be.
Do not attempt to retry the transaction until the payment method token has been recreated.
Once the payment method token has been recreated, you can schedule a retry. | Please confirm with the business or customer what the payment method should be.
Do not attempt to retry the transaction until the payment method token has been recreated.
Once the payment method token has been recreated, you can schedule a retry. | Please confirm with the business or customer what the payment method should be.
Do not attempt to retry the transaction until the payment method token has been recreated.
Once the payment method token has been recreated, you can schedule a retry. |
Suggested Actions (For Merchants) | Do not attempt to retry the payment.
You should ask the customer for an alternative payment method.
Retrying a payment with the same payment details will yield the same failed payment response. | Do not attempt to retry the payment.
You should ask the customer for an alternative payment method. | Do not attempt to retry the payment. You should ask the customer for an alternative payment method. |
Suggested Actions (For Customers) | Please check that all details of the account provided to the business are correct (E.g. Account Name, Card Number). Or you can provide the business with an alternate payment method. | Please check that the details of the credit card (expiry date and credit card number) provided to the business are correct. Or you can provide the business with an alternate payment method. | Please check that the details of the credit card (expiry date and credit card number) provided to the business are correct. Or you can provide the business with an alternate payment method. |
Payment Response Code | STOLEN_CARD 04, 07, 41, 43 | ISSUER_SUSPECT_FRAUD FRAUD_RISK_BLOCKED AMOUNT_ABOVE_MAXIMUM_LIMIT 59, 81, 83, 88, 93 | ||
Payment Response | lost_or_stolen_card | suspected_fraud | ||
Subscription Invoice Status** | Inactive | Inactive | ||
Invoice Status | Past_Due | Past_Due | ||
Transaction Status | Failed | Failed | ||
Payment Provider Response (Description) | STOLEN_CARD: The card you are trying to capture has been marked as stolen. Ask your customer for a different card. 04: Capture card
| ISSUER_SUSPECT_FRAUD: Payment was declined by the issuer because them suspecting this payment to be fraudulent. Review the cardholder. If you believe the cardholder to be legitimate, recommend them to use a different card or other form of payment. Otherwise, avoid processing transaction from them to prevent chargeback. FRAUD_RISK_BLOCKED: Payment was declined by Xendit risk assessment. Please refer to the Fraud Risk Assessment section for more detail. Review the cardholder, as the payment was blocked by your blocklist. If you believe the cardholder to be legitimate, remove the identifier from the blocklist and ask them to try again. Otherwise, avoid processing transaction from them to prevent chargeback. AMOUNT_ABOVE_MAXIMUM_LIMIT: The amount which inputted in this request is above your maximum limit. Please send another request with amount equal to or lower than the maximum limit. Default maximum limit based on currency: 1. IDR: 200000000. 2. PHP: 700000. 59: Suspected fraud 81: Suspected fraud | ||
Failed Payment Reason (Description) | Transaction rejected by customer's bank due to the card being reported lost or stolen. Please use a different payment method or contact your issuing bank. | Transaction rejected by customer's bank due to suspected fraud on the account. Please use a different payment method or contact your issuing bank. | ||
Payment Method Status | Invalidated | Invalidated | ||
What It Means | The bank has advised that payment method provided has been reported as lost or stolen.
Payment stops immediately until issue is resolved. | The transaction is suspected to be fraudulent by the bank.
Payment stops immediately until issue is resolved. | ||
Suggested Actions (For Integrators) | Please confirm with the business or customer what the payment method should be.
Do not attempt to retry the transaction until the payment method token has been recreated.
Once the payment method token has been recreated, you can schedule a retry. | Please confirm with the business or customer what the payment method should be.
Do not attempt to retry the transaction until the payment method token has been recreated.
Once the payment method token has been recreated, you can schedule a retry. | ||
Suggested Actions (For Merchants) | Do not attempt to retry the payment.
You should ask the customer for an alternative payment method. | Do not attempt to retry the payment.
You should ask the customer for an alternative payment method. | ||
Suggested Actions (For Customers) | Please check with your banking institution on your account.
Or you can provide the business with an alternate payment method. | Please check with your banking institution on your account.
Or you can provide the business with an alternate payment method. |
** Only available to integrators on subscription model
Failed Payments - Customer Issues
Payment Response Code | 57. 58. 64. 71. 74. B1. B2. N0. N7. N8. P6 | R0, R1, R3 |
Payment Response | declined | authority_withdrawn |
Subscription Invoice Status** | Inactive | Inactive |
Invoice Status | Past_Due | Past_Due |
Transaction Status | Failed | Failed |
Payment Provider Response (Description) | 57: Transaction not permitted to cardholder | R0: Stop payment order R1: Revocation of authorization order R3: Revocation of authorization order |
Failed Payment Reason (Description) | This transaction was declined by the bank | The authority for the payment method has been withdrawn. |
Payment Method Status | Valid | Invalidated |
What It Means | General decline by the bank, that could be for different reasons:
Payments will stop if maximum failed attempts have been reached. | A stop payment has been applied by the bank on instruction from the customer.
This occurs generally when a customer does not recognize a payment on their statement and puts a block on it.
Sometimes the customer puts a stop on a recurring payment when they are in dispute with the service provider.
Payment stops immediately until issue is resolved. |
Suggested Actions (For Integrators) | Please confirm with the business or customer what the payment method should be.
Do not attempt to retry the transaction until the payment method token has been recreated.
Once the payment method token has been recreated, you can schedule a retry. | Please confirm with the business or customer what the payment method should be.
Do not attempt to retry the transaction until the payment method token has been recreated.
Once the payment method token has been recreated, you can schedule a retry. |
Suggested Actions (For Merchants) | Ask the customer to contact their bank to ask why the transaction declined.
Until the matter is resolved between the customer and their bank, the transaction response will likely be the same, therefore we recommend that you request a different payment method. | Ask the customer to provide an alternate payment method.
To reinstate the recurring authority, they will need to agree to a new Direct Debit Request with a later date than when they put a stop on the payment. |
Suggested Actions (For Customers) | The bank has declined the transaction. Please contact your bank for the reason as to why the transaction had failed.
This will need to be resolved first before transactions can continue to be debited rom this account. Or you can provide the business with an alternate payment method. | If you wish to use the same account details, please contact your bank and authorise payments to be debited by Ezypay. Or you can provide the business with an alternate payment method. |
** Only available to integrators on subscription model
Error Responses
Payment Response Code | INVALID_CVV API_VALIDATION_ERROR INVALID_JSON_FORMAT TOKEN_ALREADY_USED_ERROR AUTHENTICATION_ALREADY_USED_ERROR INVALID_TOKEN_ID_ERROR INVALID_CVN_LENGTH_ERROR AUTHENTICATION_ID_MISSING_ERROR AMOUNT_GREATER_THAN_AUTHENTICATED_ERROR INVALID_AUTHENTICATION_ID_ERROR REQUEST_FORBIDDEN_ERROR TOKEN_NOT_FOUND_ERROR AUTHENTICATION_NOT_FOUND_ERROR MID_NOT_FOUND_ERROR INVALID_PROMOTION_DETAILS CARDHOLDER_NAME_REQUIRED INSTALLMENT_BELOW_MINIMUM_AMOUNT INSTALLMENT_UNAVAILABLE AMOUNT_BELOW_MINIMUM_LIMIT INCOMPLETE_AUTHENTICATION | AUTHENTICATION_FAILED DECLINED_BY_PROCESSOR ISSUER_UNAVAILABLE PROCESSOR_ERROR PROCESSOR_TIMEOUT 25, 28, 90, 91, 94, 96, 1Z, N3, N5, Q1 |
Payment Response | ezypay_error | bank_system_error |
Subscription Invoice Status** | Inactive | Inactive |
Invoice Status | Past_Due | Past_Due |
Transaction Status | Error | Error |
Payment Provider Response (Description) | INVALID_CVV: Payment was declined by the issuer because incorrect card CVN / CVV / CSC being provided. Recommend cardholder to review the card CVV / CVN / CSC (3-4 digit code on the back of the card) and try again. Alternatively, they can try to use a different card or other form of payment. API_VALIDATION_ERROR: Inputs are failing validation. The errors field contains details about which fields are violating validation. Recommendation is to check the input and retry. INVALID_JSON_FORMAT: The request body is not valid JSON. Recommendation is to check the input and retry. TOKEN_ALREADY_USED_ERROR: The single-use token ID has already been used in a charge. Recommendation is to create charge with different token_id. AUTHENTICATION_ALREADY_USED_ERROR: The authentication ID has already been used in a charge. Recommendation is to use different authentication_id to proceed charge. INVALID_TOKEN_ID_ERROR: The token ID format is invalid. Recommendation is to check if token_id format is correct and retry. INVALID_CVN_LENGTH_ERROR: The length of CVN is invalid. For AMEX card, CVN length must be 4 digit and for the others card type it must be 3. Recommendation is to check if the CVN is already following the correct format and retry. AUTHENTICATION_ID_MISSING_ERROR: Authentication ID is required for this charge. Recommendation is to include authentication_id in the charge request. AMOUNT_GREATER_THAN_AUTHENTICATED_ERROR: Charge amount was greater than what was authenticated. Ensure the charge amount is the same as what was authenticated and retry. INVALID_AUTHENTICATION_ID_ERROR: The authentication ID format is invalid. Please check if your authentication_id is already following the correct format. REQUEST_FORBIDDEN_ERROR: API key in use does not have necessary permissions to perform the request. Please assign proper permissions for the key. Learn more here TOKEN_NOT_FOUND_ERROR: The token ID was not found in the system. Please check if you already include the correct API key in the request header. For charge, the API key you are using should be secret API key. AUTHENTICATION_NOT_FOUND_ERROR: Authenticated token with given authentication ID is not found. Please check if you already input the existing authentication_id in the request. MID_NOT_FOUND_ERROR: The MID specified in "mid_label" cannot be found. Check if you have registered this MID, or if you entered the MID label incorrectly. INVALID_PROMOTION_DETAILS: The promotion detail which inputted in this request is invalid. Please change the input or check if you have available promotion in your system or not. CARDHOLDER_NAME_REQUIRED: Please send cardholder name fields in the billing_details object in your request body. INSTALLMENT_BELOW_MINIMUM_AMOUNT: Amount is below the minimum allowed for installments. INSTALLMENT_UNAVAILABLE: Possible error messages: 1. Installments are not available for cards from this bank. Please try with a card from another bank. 2. The requested installment interval is currently not supported. Please try an installment transaction with another interval. AMOUNT_BELOW_MINIMUM_LIMIT: The amount which inputted in this request is below your minimum limit. Please send another request with amount equal to or greater than the minimum limit. Default minimum limit based on currency: 1. IDR: 5000. 2. PHP: 20." INCOMPLETE_AUTHENTICATION: The authentication_id sent cannot be used as authentication could not be completed. This usually happens when there is an issue preventing generation of the 2FA page, if the user did not complete the 3DS process, or something else happened such as a bank timeout. Please attempt the payment again, or exclude authentication_id from the Charge request if optional 3DS has been enabled for you. 19: Re-enter transaction | AUTHENTICATION FAILED: Payment was declined because transaction is not authenticated yet. Recommend cardholder to to re-authenticate the transaction with 3DS. Alternatively, they can try to use a different card, other form of payment, or contact their card issuing bank to resolve the problem on online transaction. DECLINED BY PROCESSOR: Payment was declined by the processor. Ask your customer to try again. Alternatively, they can try to use a different card or other form of payment. ISSUER UNAVAILABLE: Payment was declined by the processor because card issuer is unreachable. Recommend cardholder to contact their card issuing bank to resolve the problem on online transaction. Alternatively, they can try to use a different card or other form of payment. PROCESSOR ERROR: Payment was declined by the processor because intermittent error on processor side. Recommend cardholder to try again in a few minutes. Alternatively, they can try to use other form of payment. PROCESSOR TIMEOUT: We got timeout from our processor when requested the charge which indicated as intermittent connection problem. Advise customer to retry the transaction. 25: Unable to locate record in file 28: File temporarily not available for update or inquiry 90: Cutoff is in progress 91: Temporary system error |
Failed Payment Reason (Description) | An error occurred while processing the transaction. Please contact Ezypay support. | An error occurred while processing the transaction. Please contact Ezypay support. |
Payment Method Status | Valid | Valid |
What It Means | A configuration error on our end has likely occurred. Resolution intervention required to avoid future similar issue.
Payments will stop if maximum failed attempts have been reached. | An error has occurred while communicating with the payment provider. This could be due to a timeout issue that has caused the payment to be rejected. Ezypay will send the payment for processing again. |
Suggested Actions (For Integrators) | N/A | N/A |
Suggested Actions (For Merchants) | N/A | N/A |
Suggested Actions (For Customers) | N/A | N/A |
** Only available to integrators on subscription model.
Contact
Level 14, Vista Tower, The Intermark, No. 348 Jalan Tun Razak 50400 Kuala Lumpur
help@ezypay.com | 1800 011 147