Is azupay down?

We have identified a spike in failures of outbound payments impacting Bendigo Bank for their BSB range 633 stating at 20:45 and ongoing. The issue is isolated to this Bendigo Bank BSB range. These transactions are being rejected with PA04. We recommend re-attempting impacted transactions if they are in a FAILED status and need to be re-attempted after this issue notice is resolved. We will provide updates as they become available to Azupay.

The outage impacting Bendigo Bank resolved around approximatley 2026-10-07 21:50:00 Australia/Sydney last night, and on monitoring, no further issues have been experienced. We are resolving this issue. We recommend re-attempting impacted transactions if they are in a FAILED status and need to be re-attempted. Information on error codes are available from our developer docs at https://developer.azupay.com.au/docs/making-payments#failure-reason-codes

We have identified a spike in failures of outbound payments impacting a subset of transactions for several NPP participants stating at 11:17 and resolving at 11:47 AEST. The issue appears to be concentrated to Westpac based accounts. These transactions are being rejected with PA04 or AB01 errors. While the issue appears to have resolved, we recommend re-attempting impacted transactions if they are in a FAILED status and need to be re-attempted.

Westpac have confirmed this issue is resolved and have published the following guidance on impact windows: Incident Start Date/time: 07 October 2026 @ 11:16 AEDT Incident End Date/time: 07 October 2026 @ 11:33 AEDT NPP Payment Self suspension Start Date/Time: 07 October 2026 @ 11:25 AEDT NPP Payment Self-suspension end Date/Time: 07 October 2026 @ 11:33 AEDT We are now resolving this issue. Information regarding the PA04 and AB01 error codes is avaialble from our developer documentation at https://developer.azupay.com.au/docs/making-payments#failure-reason-codes *Reason* Code Description *AB01* Clearing process aborted due to timeout. NPP Error. Client should retry for up to 8 hours before failing the payment and crediting the customers account. *PA04* Participant Not Available. Receiving bank is experiences problems. Client should retry for up to 8 hours before failing the payment and crediting the customers account.

Our analysis shows the following impacts: This isn't a cyber incident. Delays in processing: * Outbound payments via api to CBA accounts * Processing of inbound payments to PayID's from payer's CBA bank account Our recommendations are as follows: * Please inform your customers of delays where applicable. Please do subscribe to our status page for the latest and most accurate information. We apologise for the inconvenience caused.

We believe the issue is now resolved and will continue closely monitoring the performance of the system. If you are still encountering issues, please do reach out using our service desk: https://azupay.atlassian.net/servicedesk/customer/portal/3 including any pertinent information such as PayID's, bsb/account numbers, date/time stamps and amounts. Please do subscribe to our status page for the latest and most accurate information. We apologise for the inconvenience caused.

We are continuing to monitor for any further issues.

We believe the issue is now resolved. The root cause of the issue was due to intermittent transaction processing errors encountered at CBA. If you are still encountering issues, please do reach out using our service desk: https://azupay.atlassian.net/servicedesk/customer/portal/3 including any pertinent information such as PayID's, bsb/account numbers, date/time stamps and amounts. Please do subscribe to our status page for the latest and most accurate information. We apologise for the inconvenience caused.

Azupay has identified that CBA is currently experiencing an incident impacting Outbound and Inbound NPP Payments. These issues are affecting around 10% of payments. Some Outbound payments will enter a FAILED status with failure reason of AB01 or PA01. Inbound payments may be delayed.

CBA is continuing to investigate the issue affecting Inbound and Outbound NPP Payments.

CBA have resolved the issue at 20th September 2026 @ 08:30 AEST. Any outbound payments affected by this degradation will have encountered a FAILED status with an AB01 or PA01 reason code. You will have to retry these payments. Any delayed inbound payments have now been processed. If you require any further assistance, please raise a support ticket through the usual channels.

We are currently experiencing high error rates and latency impacting NPP traffic via our Banking Partner. Our analysis shows the following impacts Elevated number of errors: * PayID Registrations via PaymentRequest API Delays in processing: * Outbound payments via api * Creation/Update of PayID's via api * Processing of inbound payments to PayID's from payer's bank * PayTo payment agreement creation * PayTo payment initiations We have escalated the incident to our banking partner and are conducting a more detailed impact analysis. Our recommendations are as follows: * Please inform your customers of delays where applicable. Please do subscribe to our status page for the latest and most accurate information. We apologise for the inconvenience caused.

A fix has been implemented as of 3:23 PM AEST by our banking partner and we are observing that errors are no longer occuring and latency has returned to expected levels. We will continue to monitor traffic.

Monitoring indicates services are stable and have not had any reoccurance of issues. We are now resolving this incident. Post the issue, we have redriven a small percentage of transactions that were been impacted by this outage and that failed to successfully process. - A small amount of outbound payments may have been delayed in settlement and have been redriven and should now be settled. These will have shown a PENDING Status, and should now progress to a terminal status of SETTLED. - A small amount of PayID registrations for Payment Requests may have been delayed, which may have impacted the ability of customers to make payments to associated PayIDs tied to the Payment Request. These will have shown a WAITING status but may have been unresolvable in customer's banking interfaces. These should now be available to receive payments. Post incident monitoring indicates the degradation in services was from 3:04 PM AEST to 3:27 PM AEST. We are requesting additional information regarding the cause of the outage.