Ezypay has made 3 improvements to increase the security of our checkout page. See below for a more detailed explanation on what these improvements are.

Ezypay has redesigned the existing Settlement Tax Invoice. These changes ensure that Ezypay's Settlement Tax Invoice is compliant across each of the countries in which we operate, along with offering an improved design for auditing purposes.

This change is an important part of Ezypay's overall Fraud & Compliance activities. Previously, we relied upon transaction monitoring to alert us to transactions above the allowed limits (after the fact). Given the evolving complexities and volume of the transactions on our platform, it is critical we prevent these transactions from occurring.

Ezypay has developed a Checkout Page and its ready for you to implement. This new feature allows merchants to take once-off credit card payments via a unique checkout URL.

We would like to inform you that we will be performing maintenance to improve the infrastructure and stability of the Ezypay platform.

At 12:30 pm AEST ( 2:30pm GMT) Monday January 13th, 2020, we will be updating the mapping of the payment provider responses to our failed payment response codes to provide more detailed and meaningful failed payment reason codes.

Changes to the 'Create Invoice API'
Ezypay is making changes to the 'Create Invoice API". When creating invoices, you are now required to indicate if the payment is a one-off payment or a recurring payment.

Previously merchants did not have have any form of reports that provided them information on the transactions that had occurred against their accounts to show whether the transactions were successful or if they had failed. Especially in the case of a merchant having insufficient funds for a settlement, as no Settlement Report would be available to them to understand why they had no settlement.

Reporting on customer paid fees

Updated Failed payment mappings