Azupay clients have observed that when a payment fails, the response usually includes a specific status code and reason, such as AC02: The Debtor Account Number is invalid or missing.

However, in cases where the payment fails due to insufficient balance in the Azupay client account, the API returns a 400 Bad Request response without a specific failure status code or detailed reason. This lack of clarity makes it challenging for Azupay clients to accurately identify and track the cause of failure. This recent fix includes updates to failure codes and corresponding reasons so that clients may more easily understand the cause of an outbound payment failure.

Refer to this page for Payment error codes & reasons - NPP used codes & reasons:
https://developer.azupay.com.au/docs/making-payments#/failure-reason-codes---npp

Refer to this pay for Azupay specific Payment error codes & reasons:
https://developer.azupay.com.au/docs/making-payments#/failure-reason-codes---azupay-specific

Azupay recently provided our clients the ability to create payment requests from the dashboard - without any API integration required! (Ask us how.)
After research and consultation with our clients understanding specific payment use cases, we have uplifted the create payment request function accessible from the Azupay client dashboard to provide the ability to specify the custom PayID prefix they would like to generate for their customers.

For further information on this new feature, please refer to: https://developer.azupay.com.au/update/docs/create-payment-request-from-dashboard#/

Currently, there only exist two user roles for managing technology related administration functions within the Azupay client dashboard - 'Tech Admin' and 'Admin' and our consultation with clients has informed us that this may not meet all clients’ needs. Thus, the newly added 'Tech Operator' role will enable the user to perform actions similar to those of a 'Tech Admin', but without the ability to add new users to the dashboard.

For further information on this new role, please refer to: https://developer.azupay.com.au/docs/user-roles-reference#/

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