Previously, when we tried to do refunds for merchant or partner accounts that had insufficient balance, our system retried multiple times to check if sufficient balance was available for the operation and continued to retry till the account had sufficient balance.
But now, we have updated our core system to send an error when there is insufficient balance and will not retry the refund. Our clients will see the 400 status (Bad Request) with a failure code “ERR0.11 – Insufficient Balance”.
When creating sub-merchants via the Clients API, partners can now specify an optional 'Trading Name'.
This will help differentiate sub merchants with the same legal entity name, but may operate multiple stores or have different brands.
The 'tradingName' field will also be displayed on the dashboard, making it a breeze for partners to identify and manage different sub merchants.
For Azupay merchants that don’t have an NPP-enabled account for their sweep settlement, they can have scheduled sweeps settled in to their account via Direct Entry. This is not available by default, but the Azupay support team can set it up if our onboarded merchants or partners opt-in for this feature
The transaction ID of a refunded payment can now be viewed by you as a client or partner merchant on the Azupay dahsboard when a payment in status with ‘RETURN_COMPLETE’ is found. Previously if the transaction ID of a refunded payment was required, you needed to raise a service desk ticket to get this information.
This feature is likely to become very useful in confirming the refund transaction ID after making a refund payment to one of your customers for proof of refund during the payment dispute process with an end customer
A new App has been developed for you as a direct debit and card capture alternative. This app will allow you as a merchant to capture the PayID (and soon the BSB & account number)in order to guide users to creating a PayTo payment agreement.
This new app will provide the following benefits to our clients:
For merchant customers on the 1-click Checkout landing page wanting to pay with the PayID payment option, there is a QR code now available for users to scan and transfer PayID details onto their mobile phone from the desktop view. The transfer of PayID details onto their mobile phone allows for easier completion of payment through their mobile banking app.
Payments made via the 1-click Checkout app can now be categorised as settled via PayID or PayTo as the underlying payment method. This payment method information is displayed in search results on the Azupay dashboard.
When Azupay merchants log into the Azupay dashboard and view 1-click Checkout payments made by their customers, they can now see if the payment was settled by PayID or PayTo as the payment method.
There is a new column that can be added to search results called ‘Settled by’ which will show valid values of: ‘PayID or 'PayTo’ for 1-click Checkout app payments; OR BSB/Account number for all payments made to a virtual accounts BSB/account number combination
We have added an indication for our merchant's customers on the main payment landing that indicates after the customer has approved the Payment agreement from the merchant in their banking app, it will get cancelled before being redirected to the merchant's successful confirmation of purchase page. The reason for this change is to reduce confusion to customers when they receive ‘Payment agreement cancelled’ notification by email or SMS from their bank.
The transaction ID of a refund payment can now be viewed in the Azupay client dashboard for every payment that has a status of ‘RETURN_COMPLETE’. This information may come in useful for for any Azupay merchants/partners that are required to provide proof of refunds made to a customer during the official dispute process
Configurable search for outbound payments - clients can now configure the search results displayed when using transaction search on the client dashboard so that you can easily find the payment request that you are looking for.
Additionally client users can export configured search results displayed to CSV file with their preferences saved.
Client users can also now select the maximum number of records you want to see displayed in transaction search results and also set the number of records you want to see on each page. This is helpful you as a client if you have high transaction volumes as you can set the parameters that make it easier for you to find a transaction in a given time period.
With the introduction of pagination for search results page, the ‘Load more’ button has been removed which is a feature that you have asked us repeatedly to deprecate!
