Core platform

  • Accepting payments to BSB/account numbers: clients can now create payment requests and receive payments from their customers made to a BSB and Account Number so that the customer has the flexibility to pay either via a PayID or a BSB/Account Number.
    This feature is not enabled for all clients by default, and can be switched on by our TechOps team through a request via service desk.
    A unique combination of BSB and Account Number will be generated for each payment request.
    A payment to a BSB/account number will credit the payment to the corresponding payment request similar to how a payment is credited for a payment request paid to a PayID.
    This feature is not available in the PayID Checkout app but is available only via API call.

Azupay dashboard

  • Customisation to Daily transaction report format: clients now have the option of choosing between comma delimited and pipe delimited CSV files for their daily transaction reports.
    Previously, the report was available in just the pipe delimited CSV file. This feature is available via the Client Config and by default for all new clients, the file will be comma delimited.
    If a client chooses a comma delimited CSV file for their daily transaction report, it will affect the changes to all channels i.e client dashboard, API calls and SFTP file transfer.
    For partners with sub-merchants, their newly created sub-merchants will inherit the same report format from the parent.

Azupay dashboard

  • Uplift to Payment request search: clients can now search for Payment request transactions using the ‘Client branch’ as an input field.
  • Select user role from dropdown at time of adding new users: when adding new users for your organisation to the Azupay dashboard, clients can now select the appropriate role at the time of set-up, eliminating the need for manual role changes after the user has been added - reducing operational risk of adding a user with the incorrect role

Core platform

  • New ‘Ultimate payee’ field: we have introduced a new ‘Ultimate payee’ field in the Payment Request API to get insights on which sub-merchant of a partner has created a payment request and received an incoming payment. Some clients that are mandated by our Risk and Compliance team will need to include their sub-merchant in this new field
  • Configurable webhooks: new added functionality to configure the retry rate of webhooks over a 24-hour period.

PayID Checkout app

  • Merchants can now set up custom messaging to be displayed on the main landing page of the PayID Checkout app by raising a help desk ticket specifying the message to be displayed on the screen to your end users

Azupay dashboard

  • Introducing a new 'Tech admin' user role: This newly created user role can perform all actions of a full Admin user except this user role cannot execute finance actions like payment refunds and balance management sweep of funds. The 'Tech admin' role can also add users to the dashboard but are limited to only adding 'Tech admin' and 'Finance operator' roles.
  • Improved transaction searching: clients can now search for payment transactions within a specific time range in conjunction with a specified PayID. We have also improved how the results are sorted and displayed in the dashboard to make it easier for clients who may want to view the most recent transactions first.

Core platform

  • Blacklisting of accounts: Azupay clients can now request us to blacklist bank accounts, and in doing so prevent incoming payments from these specified accounts. As a client, you can provide a list of BSB/account numbers from which we will block incoming payments.
    This feature ensures that our clients can easily manage and restrict payments from undesirable sources.