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

We’ve introduced a powerful new feature that gives Azupay customers greater control over their Daily transaction reports—right from the Azupay client dashboard.

What’s New?
You can now customise the fields included in your Daily transaction report via the Azupay client dashboard Settings page. This enhancement allows you to tailor your reports to suit your business needs, ensuring you only see the data that matters most.

Key Capabilities✅

• View and edit default fields
• When you visit the Settings page, you’ll see a new widget listing all available report fields.
• Your current default fields will be pre-selected for easy reference.
• You can add, remove fields using simple checkboxes.
• Include the New “Settled By” Field

For more detailed information: refer to this page in our Developer doc guides:
https://developer.azupay.com.au/docs/reports#/customising-the-daily-transaction-report

We’re enhancing the PayTo experience in Azupay's V3 Pay By Bank checkout by adding in the "Continue to mobile" prompt that was previously only available to customers choosing PayID as the payment option.

What’s New?
When users access the PayTo payment option within the Pay By Bank experience, they will now see a new option titled “Continue on mobile.” This feature allows users to effortlessly transfer their session to a mobile device using a QR code and will allow them to easily complete approval of the PayTo agreement on their mobile or tablet banking app.

How It Works

• A QR code will be displayed once the users click on "Continue on mobile" link
• Scanning the QR code with a mobile device will redirect the user to the checkoutURL, specifically toggled to the PayTo flow.

Azupay's client merchants can now customise the look-and-feel of the Pay By Bank UX they want to give to their customers. By going to the Apps page on the client dashboard and clicking on the 'Appearance' tab, dashboard users can set the merchant logo and accent colour to be used for button and link theme colours.

Once logo and appearance settings have been set, you are able to preview what the main payment landing page looks like with the new built-in preview function that you can access from within the client dashboard!

For further details, please refer to this page:
https://developer.azupay.com.au/docs/managing-apps#/customising

Previously, Azupay’s Refund API endpoint supported only two parameters:

• paymentRequestId (required)
• refundAmount (optional)

While functional, this design posed challenges such as:

• Risk of duplicate refund requests
• Inconsistent refund state management
• Difficulty handling retry scenarios

To address these issues, we’ve introduced a new parameter: clientRefundIDThe addition of clientRefundID ensures that each refund request is uniquely identifiable and improves the reliability and transparency of refund operations.

👉 For full technical details and implementation guidance, visit the Refund API documentation.