Azupay have introduced a feature to enhance the Single Sign-On (SSO) experience for Azupay clients by allowing them to use their existing Identity Provider (IdP) to authenticate users and map internal roles to Azupay client dashboard roles. This will ensure that users are granted appropriate permissions within Azupay based on their roles and group memberships in their enterprise systems. The goal is to automate and streamline the role assignment process during user login, providing a seamless and secure access management solution for clients and partners.

Azupay have made a change to the existing Azupay client dashboard Finance operator role to restrict this user role being able to view top-account information on the homepage and thus preventing users with this role type performing top up transactions to their Azupay account from the client settlement account.

Previously Azupay client dashboard users were only able to search for payment requests based on the date that the payment request was created. We have now added a new criteria for which dashboard users can search for their inbound payment transactions by. This will allow you to better track finalised transactions and gain more flexible insights into transaction statuses

Some of our clients have observed that while the funds from a PayTo payment initiation lands in their client account in under 2 seconds, the notification of the same happens anytime between 10-25 seconds. Azupay have introduced a new feature so that Azupay can notifies them (and all clients) of the received payment when the funds land in the client’s settlement account.

Azupay’s clients currently use the Balance API to retrieve real-time balance information. However, some clients have recently requested the ability to access historical balance data by specifying a date and time.

An optional timestamp parameter can be supplied to retrieve the account balance at a specified point in time which is an ISO date/time string in UTC format.

Currently, when creating PayTo agreements, only the description field (140 characters) is being populated while the short description field (35 characters) is left empty. Although the short description is marked as optional in the NPP guidelines, its absence is causing issues with some banks. To improve compatibility and user experience, Azupay now automatically populate the short description field in PayTo agreements by using the first 35 characters of the main description field.

Azupay have recently added capability for batch processing of ABA files for outbound payments in addition to having batch file support for CSV files. Any ABA files generated by our clients' accounting or invoicing systems can be directly processed by Azupay instead of using their bank.

Here are the benefits of supporting ABA batch file processing for our clients:

• Improved cashflow: With DE payments taking many hours, often processing the next business day (not on weekends or public holidays), businesses are forced to fund their payment accounts earlier and for longer. With Azupay, clients can fund and send payments in real-time 24/7, every day of the year.
• Enhanced CVP: We all know how important Customer Experience (CX) is. Real-time payments directly boost CX by providing customers with instant gratification and convenience.
• Seamless transition: No development required to switch clients' batch processing over to Azupay. No paperwork required either for clients as clients are covered by existing agreement with us for outbound payments.

Asking a customer to provide a one-time-passcode (OTP) in the 1-click Checkout app payments journey adds friction to the experience. In the 1-click Checkout "single payment" journey, it is redundant given that the customer will always be asked to approve the PayTo agreement in their banking app or online banking. We have made the safe assumption that authentication to gain access to a customer’s banking app or online banking is sufficient and that they indeed do own the account that payment is being taken from.

For this feature, we have removed the need to provide an OTP, instead once the customer provides their PayID or BSB/account details to create a PayTo agreement, they are then asked to approve the agreement in their banking app or online banking.

Inbound payments to payment requests with BSB/account number specified (“Virtual accounts” payment request feature) have historically not contained any payer account information. Azupay have made the change to include payer name and BSB/account number information with the transaction information sent through so that clients can retrieve this information as required (in the case of fraud etc.)

To make the customer experience for 1-click Checkout more streamlined, when a customer has authorised a PayTo agreement created through 1-click Checkout but the payment initiation fails, an error message will be displayed letting the customer know that the payment failed due to insufficient funds. A link to 'Change PayID” will be shown within the error message and clicking this link will allow the customer to enter in another PayID for which they can create another PayTo agreement against.