Azupay have recently introduced a feature via the client dashboard that allows Distribution Partner clients to generate, disable and re-enable sub-merchant API authorisation keys via API - enhancing security, control, and operational flexibility in scenarios like fraud, suspensions, or maintenance.

Refer here to our API specs for further information:

• Create new API for sub-merchants: https://developer.azupay.com.au/reference/apikeysprovision#/
• Update new API for sub-merhants: https://developer.azupay.com.au/reference/updateapikeys#/

Azupay merchants can create payment requests straight from the Azupay dashboard. This means that our merchant clients can now create payment requests and receive inbound payments from their customers without having to integrate with Azupay payment request APIs, thus reducing integration time!

When creating payment requests to receive inbound payments from customers the following information can be set:

• Payment description
• Amount
• Customer first name
• Customer last name
• PayID domain (for PayID generation)
• Client reference

📘

Did you know that Azupay merchant partners can specify payout limits for the sub-merchants that they manage? Partners can set payout limits at the transaction level or even at a daily transaction level

• Payout limits can be set for sub-merchants at a transaction level i.e if $1000 is a transaction limit then the sub-merchant client cannot make an individual outbound payment greater than $1000.
• Daily transaction payout limits can be set for sub-merchants which looks at payments made over the current day from 12am of the day start to current time and ensuring the daily transaction limit is adhered to. If a client attempts to make a payment that would make them exceed the daily limit, then that payment will fail and client will receive an error code: 400 Bad Request: "Transaction payout limit exceeded"

Azupay merchants can now self service webhook configurations for all payment types on the Azupay dashboard. Previously merchant clients were only able to configure the webhook configurations for inbound payment requests catering for 'waiting', 'complete', and 'return complete' statuses.

Webhooks can now be configured to be sent for: payment requests, outbound payments, payment initiations and PayTo payment agreements; and webhook notifications sent when the payment changes to any of the possible transaction statuses.

To configure webhook preferences, you will need to navigate to the Settings page in the Azupay client dashboard, and find the section called: Configure Webhook Destinations.

Read more on configuring webhooks here

Azupay client dashboard users can now set 100, 200, 300 records that they want to see per page and easily paginate through results when a large volume of transactions are returned for the search results query for PayTo payment initiations

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.