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

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 help@ezypay.com.

Removal of Customer Paid Fees in the merchant's settlement report

Ezypay will be removing the reporting of customer paid Ezypay fees from the merchant’s settlement reports (PDF and CSV) and settlement tax invoice (PDF).

Customer paid Ezypay fees may consist of transaction fee, load fee and/or failed payment fee if the merchant has opted for their customers to bear the respective fee payment instead of themselves. This would have been set up during the initial merchant configuration.

Ezypay fees that are paid by customers are neither a revenue to the merchant’s business nor a payment made by the merchant to Ezypay. Therefore, customer paid fees should not be reported as such on any Ezypay reports. With the fix, merchant will no longer see these entries in the settlement reports. Customer paid fees will also not be included in the calculation in the settlement tax invoice issued by Ezypay to merchant.

If Ezypay fees are mostly borne by customers in the merchant’s setup, then the merchant may see a big drop in the number of fees reported. This may also result in a reduced number of rows in the settlement report CSV and fewer pages in the settlement report PDF.

Cancel Subscription API to Include Effective Cancellation Date
Previously integrators did not have the ability to request for a future cancellation date, unless the cancel subscription request was sent on the actual date the cancellation of subscription was required.

With this release, integrators can now send through a cancellation request in advance of the cancellation date. Ezypay will only cancel the subscription on the effective date that had been specified through the API call.

New Feature Release: Outstanding Payments Report
Previously Ezypay did not have any reports or data that was easily accessible for merchants to view which of their customers had outstanding payments, missed payments or overdue payments, etc.

With the feature release of the Outstanding Payments Reports, merchants are now able to access data from Ezypay on which customers have outstanding payments, and how much they owe up to date.

In addition, the report will also display the accounting code of the subscription payment or on-demand invoice item type. However it will not display account code from other invoice item types, such as transaction fee, add-on payment or set up payment.