Upstream Payment processing issues Impacting Outbound Bendigo Bank transactions - [incident first identified 7 October 2026 20:45 in AEST/AEDT timezone])
[2026-10-07 21:17] (monitoring): 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.
OperationalToday at 11:56 UTC
Resolved
Payment processing issues Impacting Westpac transactions - [incident first identified 7 October 2026 11:17 AEST in AEST/AEDT timezone])
[2026-10-07 11:56] (monitoring): 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.
[2026-10-07 15:26] (resolved): 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.
Degraded20 Sep at 12:49 UTC
Resolved
UPDATE: Payment processing issues to/from CBA accounts (incident number [AZ-19577] - [incident first 20th September 2026 @ 02:42 AEST])
[2026-09-20 12:49] (identified): 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.
[2026-09-20 14:37] (monitoring): 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.
[2026-09-20 20:26] (monitoring): We are continuing to monitor for any further issues.
[2026-09-20 20:27] (resolved): 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.
Degraded20 Sep at 02:45 UTC
Resolved
Upstream incident impacting CBA NPP transactions
[2026-09-20 05:08] (identified): 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.
[2026-09-20 09:34] (identified): CBA is continuing to investigate the issue affecting Inbound and Outbound NPP Payments.
[2026-09-20 10:45] (resolved): 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.
Community reports
No community reports yet
No users have reported issues with this provider yet.
Saw an error in description or reports for Azupay?
Frequently asked questions
Quick answers for payment teams and merchants investigating an incident. Firemap explains the evidence; it does not diagnose your merchant account.
Is Azupay down right now?
No. Azupay currently reports normal operation on its official status page. PayAtlas last checked it today at 18:20 UTC.
What do Operational, Degraded, Outage and Resolved mean?
They are the states Azupay publishes on its official status page. Operational means the service works normally. Degraded means part of it is slower or failing for some customers, regions or payment methods, while the rest still works. Outage means a major disruption: a service, or a key part of it, is unavailable. Resolved marks an incident Azupay has closed; the time it was resolved shows when you hover it.
Does this confirm that my merchant account or customers are affected?
Not on its own. Firemap shows what Azupay publishes about its platform, not the state of your account. An incident may affect only some regions, payment methods or integrations. Check your own transaction logs and decline codes, and contact Azupay support with specific transaction IDs if you see failures.
Where does Firemap get this status information?
From official status pages only. Firemap reads each page it tracks automatically every few minutes and records every status change and incident the provider publishes there. Nothing about Azupay is added or edited by hand.
Why can official and community signals disagree?
They come from different sources. The official status is what Azupay has confirmed, and providers often post an incident only after the first failures. Community reports come from users and can show a problem earlier, but it may be local: one bank, one country or one integration. Treat reports without an official incident as an early signal, not a confirmed outage.
What should I check before changing payment routing?
Start with your own data: error rates, decline codes and response times by payment method, card scheme and country. Compare them with the scope of the incident on the status page. Make sure the backup provider supports the same methods and currencies, move a small share of traffic first, and switch back once the incident is resolved and your metrics recover.
What is Firemap’s coverage and method?
Firemap tracks the official status pages of payment providers listed on PayAtlas. Each page is checked automatically, and every incident is stored with its start time and, once resolved, its end time. When Firemap has data for Azupay, this page shows up to 90 days of status history and incidents from the last 30 days.
What can Firemap confirm, and what can’t it?
Firemap can confirm only what Azupay has published on its status page: the current status, incidents with their start time and, once resolved, end time, and how long the page has been tracked. It cannot confirm the impact on a specific merchant, transaction or region unless Azupay says so, and it cannot see problems the provider has not reported.
Save the providers you work with and get instant access to their status, coverage, insights,
comparisons, and recommended alternatives whenever you need them.
Cookies enable us to store your preferences and give you a personalized website experience.
We also use cookies for analytics and targeted marketing.
We respect your right to privacy, so you can choose not to allow some types of cookies.
Read our Cookies Policy to learn more.
Necessary Required
These cookies are crucial for the website to perform its main functions and associated services. Simply put: the site can't fully function without them, so disabling them isn't an option.
Marketing
To bring you the most relevant content, we and our advertising partners use marketing cookies. If you choose to disable them, you might see less relevant ads.
Analytics
Analytics cookies provide anonymous insights into how visitors engage with the PayAtlas website, helping us improve user experience and functionality.
Deny
Save My Preferences
PayAtlas
Share your feedback
It goes to our team and shows up on the public board.
