We have introduced a product enhancement for users that have Ezypay’s PayNow failed payment notifications enabled. Currently, in the event of a failed payment, Ezypay will send an email to the merchant’s customers regardless of whether it was the first failed payment attempt, or subsequent failed attempts of the same invoice.

With this new enhancement, the merchant will have the choice to send their customers a failed payment notification only on the first failed attempt of an invoice, or to maintain the current settings.

By enabling this new feature, the merchant’s customers will not receive further email notifications from Ezypay for the same invoice attempted, even if the invoice fails again after a rebill or manual retry. Merchants can then decide how they want to collect any money owed by the customer when the payment fails for the second time and from further failed attempts. For example, the merchant could collect the money directly from the customer, or they can write-off the failed payment and schedule in for another payment to be debited.

This enhancement applies to both subscription and on-demand invoices.

If your users would like to alter their current PayNow failed payment notification settings to enable this new feature, they will need to contact Ezypay directly.

Ezypay has recently made some product enhancements to your on-demand invoices that fall under the unpaid status.

With these new editable fields, you now have more flexibility on what you can edit against an invoice before a payment is processed.

For example, if you find that the invoice amount in a pending invoice is incorrect, you can now edit the amount without either waiting for the incorrect amount to be processed first, and then having to issue a refund afterwards or charge the customer again for the balance required.

On-Demand invoices with a future scheduled payment date can now have additional values changed before payment is sent for processing. You can now edit the values in four more fields in addition to the three existing ones. The newly added editable fields are:

• Amount
• Accounting code
• External invoice ID
• Processing model

In addition to the existing editable fields, including:

• Payment method token
• Scheduled payment date
• Description

The technical API reference details can be found here

We would like to inform you that we will be performing maintenance to improve the infrastructure and stability of the Ezypay V2 platform on the 18th August 2022 - 00:00 - 02:00 AEST.

All V2 online services will be affected during this period. This includes our APIs, hosted payment pages, checkout pages and our failed payment collection pages (paynow.ezypay.com).

Any attempts to add, edit or make payments during this time will return an error. You should re-try these actions after our system is back online. Payments that were already scheduled before the outage time will not be affected and will be processed as normal.

All API calls to api-global.ezypay.com during this time will receive a HTTP 503 response. You will need to retry these calls after our system is back online.

For up-to-date status for our system please visit https://status.ezypay.com. If you experience any issues after the outage period, please contact us at [email protected].

We apologise for any inconvenience this may cause.

📘

This scheduled maintenance affects: (V2) vault.ezypay.com / hosted.ezypay.com (Customer payment method management), (V2) identity.ezypay.com (Customer login, Merchant login), (V2) paynow.ezypay.com (Customer once-off payment), (V2) checkout.ezypay.com (Customer once-off payment), and (V2) api-global.ezypay.com (Customer creation, Customer variations, Billing variation, Merchant on-demand billing).

Ezypay has added a new functionality that allows merchants to perform partial refunds against an invoice.
Earlier, a merchant could refund only the full invoice amount or the full amount in individual invoice items. With the addition of this new functionality, a merchant will now have the following options while processing a refund:

• Refund a partial amount in an invoice
• Refund a partial amount in individual invoice items

For a detailed explanation on how partial refunds can be implemented, please look here.

The technical API reference details and example code can be found here.

Ezypay has recently added some new webhooks that will help you with subscription and invoice management. Webhooks are key to all our integrations as they provide real-time notifications.

The payload in the webhooks provide additional data that integrators can act upon, if required.
We have added 4 new webhooks and updated 2 of our existing webhooks which will enable you to manage your subscriptions more effectively.

Further details on the webhook event responses can be found here

Further information on the above webhooks is available here.

Ezypay has made some improvements to our APIS and webhook event that will help integrators manage payment methods more effectively.

Previously integrators:
• Could not easily identify which payment method was replaced, especially when the customer had updated their payment method through the Pay Now page.
• Invoice details had only provided the payment method token ID. If a payment method token had been deleted, an integrator could no longer retrieve the details of the payment method.

Due to these reasons, Ezypay had made the following changes:

1. Identification of the Replaced Payment Method

2. Storing Payment Method Information Against Invoice Details

This update relates to how our chargebacks webhook event is now handled. A chargeback is when a customer disputes a transaction with their bank.

Ezypay had made some changes to the way we handle chargeback. When Ezypay receives a customer dispute notification from the bank, the disputed invoice will now be updated to invoice_past_due and credit_note_created immediately, and funds will be deducted from the next available settlement.

If the bank later notifies Ezypay that the customer’s chargeback was unsuccessful, the deducted amount will be credited back to the merchant’s next settlement and the customer’s invoice will be updated to invoice_paid and credit_note_paid

If the customer’s chargeback was successful, then the customer’s invoice will remain as invoice_past_due and with the updated status of credit_note_failed.

As these chargeback invoices are updated by Ezypay, it is important that partners use the following webhook events to update the customer's invoice status so that notifications of the chargeback invoices can be received, the invoice statuses are correctly updated so that merchants are aware of the chargeback outcome for their customers:
• invoice_past_due
• invoice_paid
• credit_note_created
• credit_note_paid
• credit_note_failed

More information on how Ezypay handles chargeback can be found here

We would like to inform you that we will be performing a required upgrade to our Sandbox environment, which will result in a 1-hour disruption of services within the Sandbox environment only:

Australian Eastern Daylight Time (AEDT):
Wednesday October 27th from 11:00am to 12:00pm

New Zealand Daylight Time (NZDT):
Wednesday October 27th from 1:00pm to 2:00pm

Coordinated Universal Time (UTC):
Wednesday October 27th from 12:00am to 1:00am

Please plan around the mentioned downtime as all access to the Ezypay APIs within the Sandbox environment will not be available.

We apologise for any inconvenience this may cause. For any questions, please contact us at [email protected].