Given that you know a customer's payer name BSB/ account number information, when you provide this to us in the Payment Agreement Request API then Azupay will pre-fill this information in the Subscriptions App main landing page for the customer. This leads to a more seamless payment experience for your customers setting up an agreement with you using Subscriptions app!

For more information on how to ensure you prefill payer's BSB account number information or PayID, please refer to this API spec for PaymentAgreementRequest: https://developer.azupay.com.au/reference/createpaymentagreementrequest#/

Azupay have enhanced features offered in the recently launched Subscriptions app to offer merchants the ability to craft bespoke PayTo agreements.

Here's is what merchants can now tailor PayTo agreements for their customer:

• Frequency
• Start date
• End date
• Description

Additionally, we've ensured that validation has been enhanced when PayTo agreements are created. No more formatting mishaps! We’ve added:

• Amount Check: Ensures amounts have the correct format (like two decimal places).
• End dates can't precede start dates.
• Start dates must be today or later.
• Error Feedback: If inputs go awry, clear error messages will guide you back on track.

With these new features, setting up recurring payments is smoother than ever, offering a customised and streamlined experience for everyone involved.

Previously, when we tried to do refunds for merchant or partner accounts that had insufficient balance, our system retried multiple times to check if sufficient balance was available for the operation and continued to retry till the account had sufficient balance.

But now, we have updated our core system to send an error when there is insufficient balance and will not retry the refund. Our clients will see the 400 status (Bad Request) with a failure code “ERR0.11 – Insufficient Balance”.

When creating sub-merchants via the Clients API, partners can now specify an optional 'Trading Name'.
This will help differentiate sub merchants with the same legal entity name, but may operate multiple stores or have different brands.
The 'tradingName' field will also be displayed on the dashboard, making it a breeze for partners to identify and manage different sub merchants.

For Azupay merchants that don’t have an NPP-enabled account for their sweep settlement, they can have scheduled sweeps settled in to their account via Direct Entry. This is not available by default, but the Azupay support team can set it up if our onboarded merchants or partners opt-in for this feature

The transaction ID of a refunded payment can now be viewed by you as a client or partner merchant on the Azupay dahsboard when a payment in status with ‘RETURN_COMPLETE’ is found. Previously if the transaction ID of a refunded payment was required, you needed to raise a service desk ticket to get this information.

This feature is likely to become very useful in confirming the refund transaction ID after making a refund payment to one of your customers for proof of refund during the payment dispute process with an end customer

A new App has been developed for you as a direct debit and card capture alternative. This app will allow you as a merchant to capture the PayID (and soon the BSB & account number)in order to guide users to creating a PayTo payment agreement.

This new app will provide the following benefits to our clients:

• Drastically reduces effort compared to direct integration using Azupay PayTo APIs
• Mimics the card on file approach for the merchant as much as possible (as we know that our merchants are familiar with this form of payment)

For merchant customers on the 1-click Checkout landing page wanting to pay with the PayID payment option, there is a QR code now available for users to scan and transfer PayID details onto their mobile phone from the desktop view. The transfer of PayID details onto their mobile phone allows for easier completion of payment through their mobile banking app.

Payments made via the 1-click Checkout app can now be categorised as settled via PayID or PayTo as the underlying payment method. This payment method information is displayed in search results on the Azupay dashboard.

When Azupay merchants log into the Azupay dashboard and view 1-click Checkout payments made by their customers, they can now see if the payment was settled by PayID or PayTo as the payment method.

There is a new column that can be added to search results called ‘Settled by’ which will show valid values of: ‘PayID or 'PayTo’ for 1-click Checkout app payments; OR BSB/Account number for all payments made to a virtual accounts BSB/account number combination

We have added an indication for our merchant's customers on the main payment landing that indicates after the customer has approved the Payment agreement from the merchant in their banking app, it will get cancelled before being redirected to the merchant's successful confirmation of purchase page. The reason for this change is to reduce confusion to customers when they receive ‘Payment agreement cancelled’ notification by email or SMS from their bank.