Azupay have recently added a new field to the PaymentRequestAPI called 'SuggestedPayerPayID'. Adding a value to this field allows a merchant who might know the user's PayID to pass that to Azupay, and it will prefilled in the Pay By Bank payment page displayed to customers.
When creating the PayTo agreements, merchants will now be able to specify how many payments they need to take based on the frequency that is set in the Payment Agreement API by specifying a value in the 'countPerPeriod' field. This allows merchants to flexibly manage their payment collection.
Example: Two payments need to be made in a week; set the frequency to weekly and set the count per period to two.
Read more here: https://developer.azupay.com.au/reference/createpaymentagreement
Azupay client dashboard users can now search for payment request transactions on the transactions search page by completion date instead of just creation date. Users are able to toggle between searching for transactions by creation date or completion date.
Recently, some of our clients and prospects have expressed interest in ad-hoc payment capture using Azupay's Pay by Bank with PayTo and PayID UX payment solution. However, their customers are much more familiar with BSB/Account number than PayID so we have introduced the ability for customers to enter in BSB/account number details to allow them to set up the PayTo agreement. This option to enter in BSB/account number details to set up an agreement can be set to the default state as well.
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.
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:
