Azupay's Pay by Bank checkout UX now remembers a payer’s previously used payment method and defaults to it on future transactions. If a payer has successfully completed a payment using PayTo or PayID with any Azupay merchant in the past, and the current merchant supports PayTo payments for its customers, Azupay's Pay by Bank UX will automatically land on that same payment method when a new transaction is created.

The payment method toggle remains visible, allowing payers to easily switch methods if needed, while reducing friction and improving checkout conversion.

On the Pay by Bank payment landing page, PayIDs can vary in length depending on their format (for example, email-based PayIDs). When a PayID is long enough to require wrapping, the previous layout used caused the copy button to become misaligned, affecting visual consistency and usability.

To ensure a clean and reliable experience on the Pay by Bank payment landing page, the PayID display was updated to handle longer values more gracefully. Wrapping the PayID from the “@” symbol allows the identifier to remain readable while keeping the copy button correctly aligned, improving both presentation and ease of use for customers.

Some PayID payment requests are set up as open static PayIDs, allowing client's customers to make multiple payments without a predefined amount. Previously, this resulted in a blank amount field in the Pay by Bank checkout UX, which could be unclear for some customers.

The Pay by Bank checkout UX now displays “Pay any amount” when no fixed amount is included in the PayID payment request. This provides clearer guidance, reduces confusion, and helps customers understand that they can enter the amount they wish to pay.

Some merchants - such as subscription or membership based businesses - need the flexibility to collect a customer’s next recurring payment slightly before the current billing period officially ends. Previously, the Azupay PayTo payment initiation logic required the full period (e.g., 12 months) to pass before another payment could be processed. This caused issues for some merchants, who collect renewal fees a few days before the annual term expires.

To address this, we have enhanced our Pay & Subscribe UX solution to allow merchants to process one additional payment within the same billing period for eligible agreement types. This ensures smoother renewal experiences and removes unnecessary payment initiation failures.

To improve clarity and reduce confusion for your customers during checkout, we’ve updated the payment method selection to make PayTo and PayID payment method options easier to understand and more visually appealing for payers. Clients told us that previous labels such as “Pay by Bank (PayTo)” and “Bank Transfer (PayID)” sometimes leads to uncertainty about which option to choose.

This enhancement introduces official trademarked PayTo and PayID logos, along with simple explanatory text to help payers confidently select their preferred payment method.

Compliance changes from our banking provider made recently require sub-merchants of Distribution partners created via the Clients API to supply a minimum KYC dataset.

This update ensures Distribution partner merchants submit all required KYC fields when onboarding sub-merchants, preventing downstream creation failures.

For more information on required mandatory fields for KYC, please refer to this file specification: Clients API

Note: the requirement to ensure the correct information is supplied in the KYC object when calling the Clients API to create new sub-merchants only impacts a select number of Distribution Partners. We will advise you if you need to make any changes to your API integration in order to fulfil your compliance requirements.

Returning payers using passkeys previously needed to authenticate twice when making a payment above their existing PayTo agreement limit.

With this improvement, payers now only authenticate with their banking app to approve the amended agreement amount. No secondary passkey authentication required.

This reduces friction, improves conversion, and aligns with user expectations.

We’ve enhanced the Pay by Bank experience to make the payment journey smoother for your customers. Instead of prompting payers to set up a passkey before they have set up an agreement to make a PayTo payment, they are now shown the option to create a passkey for future payments on the main payment landing page that asks them to enter their PayID.

This new opt-in approach keeps the payment flow seamless while still giving customers easy access to the added security and convenience of passkeys. It also makes it simpler for merchants to include the passkey option in their Azupay UX configuration with confidence.

For payment requests that accept multiple payments, users are allowed to make multiple partial payments toward a single transaction. The intended flow is that after completing a partial payment, the user should be redirected directly to the partial payment received screen, and when they choose to pay remaining amount, they should remain on the secure checkout page—even after a page refresh.

However, during testing of this flow, an unexpected redirection sequence was observed:

• After completing a partial payment , the user briefly sees an intermediate screen before being redirected to the correct ‘Partial payment received’ screen.
• When clicking ‘Pay remaining amount’, the user is redirected to the ‘Secure checkout’ page as expected, but refreshing this page causes an incorrect redirect back to the ‘Partial payment received’ screen.

This behaviour in the payment flow has now been fixed!

This feature introduces greater flexibility for merchants using Azupay’s Pay and Subscribe UX solution. Merchants can now define both the type of agreement (fixed or variable amount) and an end date for recurring PayTo agreements. This enhancement supports use cases where merchants want to establish variable payment agreements that can be managed offline while still leveraging Azupay’s checkout UX.

Previously, only open-ended, fixed-amount agreements with an initial payment were supported.

For more information about coonfiguring Pay and Subscribe for your payment request use case, please refer to this API file spec: https://developer.azupay.com.au/reference/createpayidpaymentrequest#/

And this guides documentation: https://developer.azupay.com.au/docs/3-comprehensive-integration-guide#/