Failed Payment Responses
When a payment fails, Ezypay will advise what the failed payment reason is against the customer's account. These failed payment response codes/reasons are provided by Ezypay's banking partner.
To help understand what each failed payment response code means and what actions are required to resolve a failed payment, below are the links to the failed payment response guides, per country and payment method.
The guides will provide a breakdown of the following and with explanation on what each columns are meant for.
Columns in failed response table | Description | Fields in API / webhook |
|---|---|---|
Payment Response Code | This is the response code return by payment provider when a transaction failed. |
|
Payment Response | Generic failed payment reason for easy understanding what happened and what the next cause of action will be. Should be used to build any logic around the failed payment handling process in the application. |
|
Subscription Invoice Status | Highlight what happened to the future invoice of a subscription, whether it will still continue billing (Active) or the billing is stopped (inactive). Note: Only applicable to integrators on subscription model. | Webhook Event: “ |
Invoice Status | Invoice status returned by Ezypay |
|
Transaction Status | Transaction status returned by Ezypay |
|
Payment Provider Response | A descriptive explanation on the “Payment Response Code” field. Provide a more drill down explanation on what happened at the payment provider. |
|
Payment Response Description | A descriptive explanation on the “Payment Response” field. A generic description on what could possibly happened and suggested actions. |
|
Payment Method Status | A more detail explanation on what the responses mean and what could be the possible reasons for failed payments. Highlight on how Ezypay can deal with it. |
True: Inactive |
What it Means | A more detail explanation on what the responses mean and what could be the possible reasons for failed payments. Highlight on how Ezypay can deal with it. | N/A |
Suggested Actions (For Integrators) | Some suggestion on what should be done by the integrators if they received the failed payment response. | N/A |
Suggested Actions (For Merchants) | Some suggestion on what should be done by the merchants if they received the failed payment response. | N/A |
Suggested Actions (For Customers) | Some suggestion on what should be done by the customers if they received the failed payment response. | N/A |
Best PracticeIntegrators should use the
failedPaymentReasoncode to build any logic around the failed payment handling process in their application as it is generically mapped regardless of which payment processor Ezypay uses.
Australia
-
Bank Payments
http://www.ezypay.com/failed-payment-response-guide/au/bank -
Mastercard & Visa Card Payments
http://www.ezypay.com/failed-payment-response-guide/au/mastercard-visa/ -
American Express Payments
http://www.ezypay.com/failed-payment-response-guide/au/amex -
PayTo
http://www.ezypay.com/failed-payment-response-guide/au/payto
New Zealand
-
Bank Payments
http://www.ezypay.com/failed-payment-response-guide/nz/bank -
Mastercard & Visa Card Payments
http://www.ezypay.com/failed-payment-response-guide/nz/mastercard-visa
Singapore
- Mastercard & Visa Card Payments
http://www.ezypay.com/failed-payment-response-guide/sg/mastercard-visa
Philippines
- Mastercard & Visa Card Payments
http://www.ezypay.com/failed-payment-response-guide/ph/mastercard-visa
Malaysia
- Mastercard & Visa Card Payments
http://www.ezypay.com/failed-payment-response-guide/my/mastercard-visa
Taiwan
- Mastercard & Visa Card Payments
http://www.ezypay.com/failed-payment-response-guide/tw/mastercard-visa
Hong Kong
- Mastercard & Visa Card Payments
http://www.ezypay.com/failed-payment-response-guide/hk/mastercard-visa
South Korea
Updated 10 days ago