We’ve enhanced the payment success screen to improve how longer PayIDs are displayed within iFrames. Previously, extended PayIDs could wrap awkwardly across lines, affecting readability. With this update, long PayIDs are now neatly truncated with an ellipsis (…) to maintain a clean layout.

Users can simply hover over the PayID to view the full identifier, ensuring clarity without compromising design or user experience.

Azupay has made the Pay By Bank UX even simpler for customers that return to you for repeat purchases.

Currently, when a returning payer attempts to make a payment that exceeds their PayTo agreement's maximum amount limit, they encounter a two-step process that creates friction in the user experience. (The customer must approve an agreement amendment to increase the maximum amount limit and then after amendment approval, the customer must click again to initiate the actual payment.)

We have updated the Pay by Bank UX to remove the two-step process and ensure our customers can make a payment with you in the easiest way possible.

To support merchants with strict account verification requirements, this enhancement ensures that payer details—such as PayID or BSB/Account—are securely prefilled and locked when creating a PayTo payment agreement via the Pay by Bank UX.

In order to prefill BSB/account number or PayID field shown to your customer, simply send in a value in suggestedPayerDetails field. Please refer to the PaymentRequest API file specification for further details on this field.

Note: you will also need to raise a ticket with Azupay service desk to enforce the guardrails of changes to payer PayID or BSB/account number details. We will make changes to your client configuration Pay by Bank setup

You can now use the Azupay Payment Request API via the Pay by Bank UX solution to collect an initial once-off payment from your customers and then setup a PayTo agreement to collect future payments in one transaction!

Collect an initial amount from your customers, while setting up a recurring PayTo agreement . Recurring PayTo agreements can be for a recurring regular amount, or a flexible PayTo agreement for future ad-hoc payments.

Key features

• Initial payment – one-time setup payment or first billing cycle amount.
• Recurring payments – collect ongoing payments via a simple API call.
• Automatic agreement creation – payment agreements are created during checkout, linking initial and recurring amounts.

For more information - refer here: and talk to your Azupay account manager or Sales representative to understand how to integrate this feature into your current payment flows

Currently, when Virtual Accounts are enabled in a client’s configuration, Payment Requests automatically have Virtual Accounts created by default.

However, as some clients have indicated they require more control over when Virtual Account BSB/account numbers are created, Azupay have introduced a new field enableVirtualAccount to specify that a payment request should have a Virtual Account number created for it, rather than applying this behaviour universally to all new payment requests.

For more information on this new feature, pelase refer to the Payment Request API file spec here: https://developer.azupay.com.au/reference/createpayidpaymentrequest#/

We’re streamlining the return-payer experience in our Pay by Bank hosted checkout experience to minimise clicks and cognitive load for your customers. Returning payers will land on a confirmation screen showing masked PayID details so that are confident to authenticate with their passkey and make a payment against their PayTo agreement with the merchant.

Who it’s for Returning customers who previously paid the merchant via the V3 checkout and have an active PayTo agreement.

For more information on our Pay by BAnk UX checkout, please refer here: PayTo repeat payments with passkeys

Azupay can now generate CAMT.053 bank statements for you. A CAMT.053 bank statement is standard digital file format that provides a clear, structured view of your transaction activity.

Unlike a PDF statement, a CAMT.053 file is machine-readable, making it easy for your ERP, accounting, or treasury system to process automatically, no manual entry required.

To enable the CAMT.053 bank statement detailing your transaction activity, please raise a request with Azupay service desk.

For more information on the CAMT.053 file format, please refer here: CAMT.053 Bank Statements

Azupay clients can now initiate outbound payments directly from the Azupay Dashboard - no API integration required! The new Disbursement solution enables Finance Admin and Admin users to send funds to PayIDs with built-in verification, role-based controls, and real-time status tracking.

Whether you're issuing refunds, paying suppliers, or managing payroll, this feature offers a fast, secure, and auditable way to disburse funds—all from one central place.

👉 To enable this feature, raise a ticket with the Azupay Service Desk. 📘 Learn more here: Disbursements

To help clients proactively manage their Azupay account balances, we’ve introduced a configurable Low Balance Alert Notification feature. This enhancement enables Admin and Finance Admin users to receive timely email alerts when their account balance drops below a specified threshold—ensuring uninterrupted operations and allowing for prompt top-ups.

How It Works:

Admin or Finance Admin users can access the Balance Management screen to:

• Set a custom alert threshold amount (e.g. $50,000.00).
• Define an email distribution list of up to 5 recipients to receive the low balance alerts

When the Azupay account balance falls below the configured threshold, an email alert is automatically sent to the designated recipients. The alert includes:

• Client Name: [Merchant name]
• Alert Threshold: $[Threshold_Amount]
• Date & Time Triggered: [Alert_Timestamp in Australia/Sydney time]

Refer to this page in our Developer portal for further details: https://developer.azupay.com.au/docs/managing-your-account-balance#/low-balance-alert-notifications

To support merchants with strict account verification requirements, this enhancement ensures that payer details—such as PayID or BSB/Account—are securely prefilled and locked when creating a PaymentAgreementRequest via Subscriptions app.

In order to prefill BSB/account number or PayID field shown to your customer, simply send in a value in suggestedPayerDetails field. Please refer to this Payment AgreementRequest API file specification for further details.

Note: If you send in a value to suggestedPayerDetails, your customer will not be able to edit the PayID or BSB/Account number in this field when it is shown to them on the UI