Upcoming changes to failed payment mapping for AU and SG
Updated Failed payment mappings
Release date Wednesday 2nd October
We are constantly striving to improve on our collection rates and have undertaken a comprehensive review of the failed payment mapping codes we receive from our Australian and Singapore Mastercard and Visa processing provider to identify improvements to our failed payment response handling.
These changes will collectively result in both reduced payment failures and optimised handling of those payments that have declined.
From Wednesday October 2nd, new failed payment codes and mapping will be used for all new transactions. The new responses and mapping information will be displayed when utilising these APIs:
- List Invoice API - https://developer.ezypay.com/reference#list-invoices
- List transaction API - https://developer.ezypay.com/reference#list-transactions
- Invoice_past_due webhook payload - https://developer.ezypay.com/docs/webhook-event-response#section-invoice-status-payload-event
The invoice and transaction status and FailedPaymentReason codes are summarised in the table below.
Payment provider response codes and descriptions are also updated and the full list can be found
https://developer.ezypay.com/docs/failed-payment-response
| Invoice / webhook status | Transactions Status | Failed payment reason code | Payment Method status |
|---|---|---|---|
| PAID | Success | Success | Valid |
| PAST_DUE | Failed | Insufficient_funds | Valid |
| PAST_DUE | Failed | customerto contact_bank | Valid |
| PAST_DUE | Failed | Invalidpayment method | Invalidated |
| PAST_DUE | Failed | lost_or_stolen_card | Invalidated |
| PAST_DUE | Failed | expired_card | Invalidated |
| PAST_DUE | Failed | limit_exceeded | Valid |
| PAST_DUE | Failed | suspected_fraud | Invalidated |
| PAST_DUE | Failed | bank_system_error | Valid |
| PAST_DUE | Failed | ezypay_error | Valid |
Invalidating Payment methods
Please note that Ezypay will take action to automatically invalidate the payment card details held on file, according to the provider response code, to ensure no retries or new transactions are processed or attempted. This will avoid unnecessary failed payment fee stacking.
Failure reason codes that will invalidate payment methods are shown in the table above.
When any new invoice or retry is sent with an invalidated payment method, these invoices will not be sent to our provider for processing and the invoice status will be set to Past_Due.
Invalid payment methods need to be updated before invoices can be retried.
Specific changes in respect of this and other payment response code handling in your country are documented here.
If you have any questions about these changes and the system behaviours that result, please do not hesitate to contact our support team on 1300 300 553 or at [email protected].