azupay Outage History

Started Oct 07, 2026, 10:17 AM UTC· resolved Oct 07, 2026, 10:48 PM UTC

1. monitoring Oct 07, 2026, 10:17 AM UTC

   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.

2. resolved Oct 07, 2026, 10:48 PM UTC

   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

Read the full incident report →

Started Oct 07, 2026, 12:56 AM UTC· resolved Oct 07, 2026, 04:26 AM UTC

1. monitoring Oct 07, 2026, 12:56 AM UTC

   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.

2. resolved Oct 07, 2026, 04:26 AM UTC

   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.

Read the full incident report →

Started Sep 20, 2026, 02:49 AM UTC· resolved Sep 20, 2026, 10:27 AM UTC

1. identified Sep 20, 2026, 02:49 AM UTC

   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.

2. monitoring Sep 20, 2026, 04:37 AM UTC

   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.

3. monitoring Sep 20, 2026, 10:26 AM UTC

   We are continuing to monitor for any further issues.

4. resolved Sep 20, 2026, 10:27 AM UTC

   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.

Read the full incident report →

Started Sep 19, 2026, 04:45 PM UTC· resolved Sep 20, 2026, 12:45 AM UTC

1. identified Sep 19, 2026, 07:08 PM UTC

   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.

2. identified Sep 19, 2026, 11:34 PM UTC

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

3. resolved Sep 20, 2026, 12:45 AM UTC

   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.

Read the full incident report →

Started Aug 27, 2026, 05:22 AM UTC· resolved Aug 27, 2026, 06:26 AM UTC

1. identified Aug 27, 2026, 05:22 AM UTC

   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.

2. monitoring Aug 27, 2026, 05:37 AM UTC

   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.

3. resolved Aug 27, 2026, 06:26 AM UTC

   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.

Read the full incident report →

Started Aug 27, 2026, 04:27 AM UTC· resolved Aug 27, 2026, 06:26 AM UTC

1. investigating Aug 27, 2026, 04:27 AM UTC

   Azupay's service desk is currently being impacted by at Atlassian outage for JIRA and Confluence products, impacting Azupay's ability to view service desk requests. We have raised a support request with Atlassian to investigate the issue, and monitoring indicates it may be a wide spread issue for Atlassian customers as noted at https://status.atlassian.com/ If you require any urgent support, please instead email [email protected] while this incident is occurring as an alternate support channel.

2. monitoring Aug 27, 2026, 04:48 AM UTC

   Atlassian have identified a potential fix and are rolling it out to impacted regions. We have now regained access to service desk functionality. We will continue to monitor until formal incident resolution is provided by Atlassian.

3. resolved Aug 27, 2026, 06:26 AM UTC

   We are now resolving this incident, as Atlassian have confirmed full incident recovery.

Read the full incident report →

Started Aug 24, 2026, 03:36 AM UTC· resolved Aug 25, 2026, 04:41 AM UTC

1. investigating Aug 24, 2026, 03:36 AM UTC

   We are aware of issues in processing payments. We are currently investigating the impact and will provide a detailed update as soon as one becomes available. Please do subscribe to our status page for the latest and most accurate information. We apologise for the inconvenience caused.

2. investigating Aug 24, 2026, 04:17 AM UTC

   Our NPP Banking partner has acknowledged the issue and is working on resolution of the issue. Monitoring indicates the problem is primiarly impacting a percentage of requests for the following services: - PayID Registration and Deregistration events used by the PaymentRequest API. These are being redriven, however you may experience delays of a few minutes before PayIds become available to recieve payments. - Outbound Payments via the Payments API. These are being redriven, however your customers may experience a delay in settlement of a few minutes for outbound payments. - A small volume of PaymentAgreement and PaymentInitiation events are failing, impacting PayTo agreement status updates and payment initiation events. We continue to observe high latency on requests to our banking partner- the initial high error rate has reduced to near normal levels however we are still seeing a percentage of requests encountering errors and continue to monitor the issue.

3. identified Aug 24, 2026, 05:04 AM UTC

   We are continuing to experience intermitten latency to the NPP network via our banking partner. They have confirmed their teams are continuing to investigate and remediate the remaining intermittent service issues as a priority, and we expect an additional update within one hour. Azupay is redriving impacted transactions, and you may continue to experience a short delay in payId registration with some paymentRequest API calls.

4. identified Aug 24, 2026, 06:37 AM UTC

   We are continuing to experience intermitten latency to the NPP network via our banking partner. They have confirmed their teams are continuing to investigate and remediate the remaining intermittent service issues as a priority, and we expect an additional update within one hour. **The issue has not yet been resolved.** Azupay is redriving impacted transactions, and you may continue to experience a short delay in payId registration with some paymentRequest API calls.

5. monitoring Aug 24, 2026, 07:38 AM UTC

   System health of our banking partner has recovered as of 5:05pm AEST and 100% of requests are now being processed successfully. We will continue to monitor system performance for any regressions. We apologies for any inconvenience caused.

6. resolved Aug 25, 2026, 04:41 AM UTC

   This incident has been resolved. No further issues have been observed. Summary: PayTo agreements, PayID Alias Registration and Deregistrations and Outbound Payments experienced heightened errors between 24th August 01:00 PM AEST to 05:05 PM AEST. The initial investigation identified intermittent latency and elevated error rates within our banking partner’s connectivity to the NPP network. This primarily affected PayID registration/deregistration, outbound payments, and a small volume of PaymentAgreement and PaymentInitiation events. The banking partner acknowledged the issue and worked on remediation, with Azupay redriving impacted transactions while monitoring the service until request processing returned to normal. The system health of our banking partner has recovered as of 5:05pm AEST, and 100% of requests are now being processed successfully. Azupay has confirmed that impacted transactions are being processed successfully, including PayID registration and deregistration, outbound payments, PaymentAgreement, and PaymentInitiation events. A small number of outbound payments remained in a PENDING state following the NPP service disruption. These transactions were reviewed against their corresponding NPP status were manually patched to reflect the correct final status. We apologise for any inconvenience caused and thank you for your patience and understanding.

7. postmortem Sep 03, 2026, 07:48 AM UTC

   Our banking partner has provided us information regarding the root cause of this issue. **Incident Cause** On 24th August 2026, between 12:55 pm and 4:52 pm, a power outage and associated network disruption impacted an upstream service provider utilised by our banking partner for hosting. This activity was related to an underlying infrastructure change activity that caused an unexpected fault and cascading power failure, impacting part of a redundant architecture configuration and leading to performance issues with a portion of traffic. The faulty hardware impacted by the issue has been replaced, and follow up actions are planned to confirm the overall resiliency of the power configuration at the impacted data centre. It is not expected to re-occur. **Impact** This impacted communication between application and database components across several production platforms, and impacted a portion of Azupay traffic to and from the NPP network for approximately 1/3rd of traffic during the incident window for Payment activities and PayID maintenance. **Resolution** Our banking partner was able to successfully recover services via a graceful failover to their secondary site, and as Azupay has redundancy patterns implemented in our system, we were able to redrive impacted transactions during the incident window.

Read the full incident report →

Started Apr 29, 2026, 08:05 AM UTC· resolved Apr 29, 2026, 11:34 PM UTC

1. investigating Apr 29, 2026, 08:05 AM UTC

   We are aware of issues in processing payments and payment request registrations. We are currently investigating the impact and will provide a detailed update as soon as one becomes available. The issue appears to be upstream of us affecting our banking partner and has been escalated to them for incident management. Please do subscribe to our status page for the latest and most accurate information. We apologise for the inconvenience caused.

2. identified Apr 29, 2026, 08:22 AM UTC

   We are observing a recovery in impacted services as of 18:10 AEST and will continue to monitor to confirm resolution.

3. monitoring Apr 29, 2026, 08:48 AM UTC

   We are monitoring the issue and system performance has recovered. Our analysis shows the following impacts: Elevated number of errors: * Creation/Update of PayID's via api (Create PaymentRequest) PayID Registrations have recovered post a second spike in errors between 18:10 and 18:28. We have reprocessed paymentRequests that have been impacted. Analysis of other API services indicate that no impact to other APIs has occured. Our recommendations are as follows: * Please inform your customers to re-attempt payments to paymentRequests if issues were experienced when attempting a payment. Please do subscribe to our status page for the latest and most accurate information. We apologise for the inconvenience caused and will provide additional information on root cause once available.

4. resolved Apr 29, 2026, 11:34 PM UTC

   This incident has been resolved. No further issues have been observed. Summary: PayID Alias Registration and Deregistrations exeperienced hightened errors between 29 April - 17:30 AEST to 18:09 and 18:15 to 18:29. Due to the error rate only affecting a portion of traffic and Azupay redriving paymentRequest registrations, clients may not have experienced significant impact during the incident perioid. While we initially identified a small count of hightened identified errors on outbound payment processing due to increased latency on an upstream API, these transactions were retried and did not have introduced delay in payment processing. Root Cause of Issue We have requested a root cause analysis from our Payment Accesss Gateway provider banking partner for additional information on the cause of the issue. Initial investigation and resolution indicates a degradation in a portion of their compute resources in their load balanced API responsible for PayID registrations, and cycling the unhealthy nodes resolved the issue. We will work with our banking partner to identify opportunities to improve the resiliency of these services.

Read the full incident report →

Started Apr 15, 2026, 10:06 AM UTC· resolved Apr 15, 2026, 11:13 PM UTC

1. investigating Apr 15, 2026, 10:06 AM UTC

   We are aware of issues in payment request PayID registration and de-registration and payment agreement registrations and that these services are experiencing increased error rates. We are currently investigating the impact and will provide a detailed update as soon as one becomes available. Please do subscribe to our status page for the latest and most accurate information. We apologise for the inconvenience caused.

2. identified Apr 15, 2026, 10:10 AM UTC

   Our NPP banking partner has confirmed this issue and are investigating. Payments against registered paymentRequests are not impacted. We will be re-attempting registration of payIds for in flight payment requests. We will provide updates as they become available.

3. identified Apr 15, 2026, 10:42 AM UTC

   We are continuing to work on a fix for this issue.

4. monitoring Apr 15, 2026, 11:22 AM UTC

   We are observing that the error rate has recovered and services are now operating as expected. We will continue to monitor the performance. We will provide a root cause analysis when additional information is available.

5. resolved Apr 15, 2026, 11:13 PM UTC

   We have been monitoring the system and not seen any reoccurance of performance degradation, and the issue is resolved. The issue occured upstream of Azupay and we are awaiting a post incident review with root cause. We will provide further details once they are available.

6. postmortem Apr 16, 2026, 02:20 AM UTC

   **Client Post Incident Advice** The incident we experienced last night impacted the PayID registration process for our paymentRequest product between 7pm and 9pm AEST, and some PayID registrations during this incident were delayed. If you use our paymentRequest product and have a client who pays you via a payID, they may have been unable to complete a payment successfully against the PayID during this period. Azupay successfully registered all PayIDs by 10PM AEST after the incident window, with the majority of impacted paymentRequests being registered by 9:20PM AEST. You may need to contact customers who attempted payments during this period and request they re-attempt the payment if the paymentRequest is still in a WAITING status and you are expecting they should have paid by now. As the PayIDs were not registered, the customer would have not been able to successfully look up the PayID in their banking portal, and no payment would have been attempted. You should contact impacted clients, let them know the PayID is now available for payment, and they should re-attempt it. If end customers have any issues making payment to the registered PayID, please raise a request with our service desk at [https://azupay.atlassian.net/servicedesk/customer/portal/3](https://azupay.atlassian.net/servicedesk/customer/portal/3) for support. Additional information on the root cause is still pending. ----- We are awaiting a Post Incident Review from our upstream impacted connected institute, which should be supplied on the 1st of May. We will provide further details once this has been shared.

Read the full incident report →

Started Jan 23, 2026, 12:19 AM UTC· resolved Jan 23, 2026, 02:29 AM UTC

1. investigating Jan 23, 2026, 12:19 AM UTC

   Azupay has identified that ANZ (ANZBAU3LXXX) is currently experiencing an incident impacting Outbound NPP Payments, and are investigating if inbound transactions are also impacted. Clients making outbound payments that are impacted will have recieved PA04 and AB01 error codes, and the payment will be in a FAILED status. Clients should review if they should re-attempt these transactions. Incident Start Date/time: 23 Jan 2026 - 9:40 AM AEDT Incident End Date/time: TBD A further update will be provided when more information is available.

2. monitoring Jan 23, 2026, 12:33 AM UTC

   Our banking partner has confirmed that the ANZ bank outage has been resolved now. Azupay is currently monitoring the situation.

3. monitoring Jan 23, 2026, 12:34 AM UTC

   We are continuing to monitor for any further issues.

4. monitoring Jan 23, 2026, 01:18 AM UTC

   The incident has been confirmed as resolved by ANZ. We will monitor and resolve if no further updates are provided in the next few hours.

5. resolved Jan 23, 2026, 02:29 AM UTC

   Incident has been resolved. Incident Start Date/time: 23 Jan 2026 - 9:40 AM AEDT Incident End Date/time: 23 Jan 2026 - 11:05 AM AEDT

Read the full incident report →

Started Oct 15, 2025, 05:56 AM UTC· resolved Oct 15, 2025, 09:14 AM UTC

1. investigating Oct 15, 2025, 05:56 AM UTC

   We are aware of issues in Registering and Updating PayIDs. The Inbound and Outbound payments are not affected. We are currently investigating the impact and will provide a detailed update as soon as one becomes available. Please do subscribe to our status page for the latest and most accurate information. We apologies for the inconvenience caused.

2. investigating Oct 15, 2025, 06:32 AM UTC

   We are currently aware of intermittent issues affecting the creation and updating of PayIDs due to a downstream provider outage. Clients creating new PayIDs for inbound payments may experience delays in PayID registration. Customers attempting to make payments to these new PayIDs via their online banking may also encounter lookup failures. This is an industry-wide outage impacting all participants. Outbound payments using BSB and account numbers remain unaffected. However, outbound payments to PayIDs may experience intermittent failures during this period. We apologise for the inconvenience caused.

3. monitoring Oct 15, 2025, 07:06 AM UTC

   We believe the issue has now been resolved, and PayIDs are once again being registered within expected response times. The backlog of queued PayID creations has been cleared, and our systems are operating normally. We will continue to closely monitor system performance during the evening. Please do subscribe to our status page for the latest and most accurate information. We apologise for the inconvenience caused.

4. resolved Oct 15, 2025, 09:14 AM UTC

   This incident has been confirmed resolved. We have been monitoring our systems and no ongoing issues have been observed.

Read the full incident report →

Started Sep 23, 2025, 04:55 AM UTC· resolved Sep 23, 2025, 05:42 AM UTC

1. identified Sep 23, 2025, 04:55 AM UTC

   Notifying participant: NPPA Institution experiencing difficulty: NAB NAB is experiencing issues affecting Inbound and Outbound NPP Payments, and have self suspended from the NPP while they investigate the issue. The issue is currently affecting approximately 100% of Inbound and Outbound NPP Payments to and from NAB banking customers. NAB is currently working through resolution of the issue. Incident Start Date/time: 23 Sept 2025 @ 11:00 AEST Self-suspension Start Date/Time: 23 Sept 2025 @ 11:45 AEST Impact - End customers attempting to pay via NAB banking apps will be unable to make payments to PayIDs. - Payments from your Azupay account to NAB PayIDs will fail and return a PA04 Error.

2. resolved Sep 23, 2025, 05:42 AM UTC

   NAB have resolved the issue that has been affecting Inbound and Outbound NPP payments. NAB have advised that they have now issued an admi.016 (PA01) to reinstate their NPP services. Incident Start Date/time: 23 Sept 2025 @ 11:00 AEST Incident End Date/time: 23 Sept 2025 @ 15:02 AEST Self-suspension Start Date/Time: 23 Sept 2025 @ 11:45 AEST Self-suspension End Date/Time: 23 Sept 2025 @ 15:02 AEST We recommend reviewing impacted transactions and reprocessing as appropriate. Regards, the Azupay Team

Read the full incident report →

Started Sep 17, 2025, 12:29 AM UTC· resolved Sep 17, 2025, 04:04 AM UTC

1. investigating Sep 17, 2025, 12:29 AM UTC

   We have identified that Payments to Commonwealth Bank (CBA) are currently failing across several clients. We are investigating the issue to confirm if this is affecting other banks and escalating via appropriate channels to confirm the cause and resolve. We will provide updates as additional information becomes available. Regards, the Azupay Team.

2. monitoring Sep 17, 2025, 12:58 AM UTC

   We are monitoring an improvement in impacted banks as at 10.41 AM AEST. Impacted banks include: - CBA (82% of affected transactions) - NAB (12% of affected transactions) - several other banks have had a small number of transactions impacted. We are conducting an impact analysis of affected transactions and clients. A root cause has not yet been identified. We will provide updates as they are available.

3. monitoring Sep 17, 2025, 01:47 AM UTC

   We have not observed any further issues with CBA or NAB outbound transactions (Payments to clients) since 10:41AM AEST. A small number of transactions to Macquarie Bank are still being impacted as of 11:35AM AEST. We will continue to monitor the issue. If you have any questions or require support, please contact our service desk at https://azupay.atlassian.net/servicedesk/customer/portal/3 Regards, the Azupay team.

4. resolved Sep 17, 2025, 04:04 AM UTC

   We have been monitoring the issue and have not observed any additional instances of failed transactions due to this issue since 11:50AM. We will be marking this issue as resolved and continue to monitor services. A review indicates that the issue primarily impacted outbound payments to end customers via our Payments API, with a small amount of payment initiations (PayTo payment requests) also impacted. We are awaiting a root cause analysis from our upstream NPP partners, however initial investigation indicates that the the issue is an external issue that has impacted banks across the NPP network and was not isolated to Azupay. Azupay has confirmed that transactions affected by this issue has impacted the following four banks between the following times. - CBA: 9:29 am to 10:42 am - NAB: 9:30 am to 10:31 am - Macquarie Bank: 10:23 am to 11:50 am - Bank of Melbourne: 9:30 am to 10:11 am Azupay will reach out to impacted clients to provide additional information as required. Regards, the Azupay Team.

Read the full incident report →

Started Aug 23, 2025, 02:00 AM UTC· resolved Aug 23, 2025, 01:15 PM UTC

1. resolved Aug 26, 2025, 05:45 AM UTC

   Summary of Issue Our Banking Partner experienced an issue on on Saturday evening during routine maintenance of their systems that resulted in a rejection of 780 of transactions with an error code of L001. Azupay review indicates this affected outbound payments resolved between Saturday 11:20 PM and Saturday 11:35 PM, with the majority of affected transactions being affected between 23:30 to 23:31. The systems under maintenance with our Banking Partner are not associated with products and services Azupay, and were not included in our maintenance bulletin schedule. We are awaiting a post incident review to determine the root cause. Potential Action Required Azupay will contact affected clients with affected transaction Ids to assist with review and any client action required. Rejected transactions will need to be reprocessed for affected transactions. If your system implements recommended resiliency patterns to retry failed transactions, confirm that retry attempts were successful, otherwise resubmission may be required. Azupay provides guidance on handling error codes at Payment Error Codes Current guidance for L001 errors: Cuscal account error. Cuscal is unable to debit funds to make the payment. Client should retry for up to 8 hours before failing the payment and crediting the customers account. Further Support If you have any questions or require further support for this issue, please raise a request via our service desk at Service Desk

Read the full incident report →

Started Aug 22, 2025, 07:20 AM UTC· resolved Aug 22, 2025, 08:34 AM UTC

1. investigating Aug 22, 2025, 07:20 AM UTC

   We are aware of issues in delayed processing of outbound payments, inbound payments and payment request PayID registrations and de registrations. The issue has been confirmed by our Banking Partner who is investigating it. We are currently investigating the impact and will provide a detailed update as soon as one becomes available. Please subscribe to our status page for the latest and most accurate information. We apologise for the inconvenience caused.

2. investigating Aug 22, 2025, 07:42 AM UTC

   Inbound payments are now processing normally as are PayID registrations. Some outbound payments sent between 16.45 and 17.25 have been rejected and will need to be resubmitted. A number of payments remain in a PENDING state which will cause a delay in settlement. Our banking partner is still investigating the issue.

3. monitoring Aug 22, 2025, 08:01 AM UTC

   Service has been restored for all impacted processes. There are a number of outbound payments pending settlement that we are working with our banking provider to resolve. We'll continue to closely monitor the situation into this evening. We apologise for the inconvenience caused.

4. resolved Aug 22, 2025, 08:34 AM UTC

   All system are now operating normally and all pending outbound payments have been resolved. We'll continue to monitor throughout the evening. We apologise for any inconvenience caused.

Read the full incident report →

Started Nov 21, 2024, 02:32 AM UTC· resolved Nov 21, 2024, 04:11 PM UTC

1. investigating Nov 21, 2024, 02:32 AM UTC

   We are aware of issues in processing payID registrations, account inquiries and payTo payment initiations. We are currently investigating the impact and will provide a detailed update as soon as one becomes available. This is an upstream issue with our banking partner and we are working with their team for a resolution as soon as possible. Payment Requests and Payments are not believed to currently be affected. Please do subscribe to our status page for the latest and most accurate information. We apologise for the inconvenience caused.

2. investigating Nov 21, 2024, 02:33 AM UTC

   We are continuing to investigate this issue.

3. identified Nov 21, 2024, 03:19 AM UTC

   Our NPP banking partner has identified all affected services for this Incident and have confirmed clients will experience processing issues with the following: • PayID Resolution • Account Resolution • PayID Enquiry • Register PayID • Update PayID Name • Update PayID Status As Azupay registers PayIDs asynchronously for payment requests, for in flight payment requests raised after the incident begun at 1:25 AEST customers using our payment request app may see a payID checkout but will be unable to process these payment requests with their bank, as the PayIDs will not yet be registered on the NPP network. These requests are being queued by our system and will be registered once our NPP banking partner recovers relevant services. Payment Requests raised prior to the incident should operate as expected and should be able to receive payments. Our NPP banking partner believe they have identified the root cause and are in the process of deploying a break fix. We are seeing recovery of services occurring via relevant monitoring. We will provide updates as services recover and these in flight payment requests are successfully registered.

4. monitoring Nov 21, 2024, 03:45 AM UTC

   Monitoring indicates our NPP banking partner services have recovered. We are actively monitoring for any further issues. Queued Payment Requests are being re-processed, and affected services should now be available for use. Please raise any ongoing issues encountered via our service desk at https://azupay.atlassian.net/servicedesk/customer/portal/3 We apologise for any inconvenience caused during this outage.

5. identified Nov 21, 2024, 07:07 AM UTC

   We have had a recurrence of this issue with our NPP banking provider and we are working with them to resolve it. The following services as affected:: • PayID Resolution • Account Resolution • PayID Enquiry • Register PayID • Update PayID Name • Update PayID Status As Azupay registers PayIDs asynchronously for payment requests, for in flight payment requests raised after the incident begun at 17:40 AEST customers using our payment request app may see a payID checkout but will be unable to process these payment requests with their bank, as the PayIDs will not yet be registered on the NPP network. These requests are being queued by our system and will be registered once our NPP banking partner recovers relevant services. Payment Requests raised prior to the incident should operate as expected and should be able to receive payments.

6. monitoring Nov 21, 2024, 07:37 AM UTC

   Monitoring indicates our NPP banking partner services have recovered. We are actively monitoring for any further issues. Queued Payment Requests have been re-processed, and affected services should now be available for use. Please raise any ongoing issues encountered via our service desk at https://azupay.atlassian.net/servicedesk/customer/portal/3 We apologise for any inconvenience caused during this outage.

7. identified Nov 21, 2024, 08:40 AM UTC

   We have had a recurrence of this issue with our NPP banking provider again and we are working with them to resolve it. The following services as affected:: • PayID Resolution • Account Resolution • PayID Enquiry • Register PayID • Update PayID Name • Update PayID Status As Azupay registers PayIDs asynchronously for payment requests, for in flight payment requests raised after the incident begun at 19:25 AEST customers using our payment request app may see a payID checkout but will be unable to process these payment requests with their bank, as the PayIDs will not yet be registered on the NPP network. These requests are being queued by our system and will be registered once our NPP banking partner recovers relevant services. Payment Requests raised prior to the incident should operate as expected and should be able to receive payments.

8. identified Nov 21, 2024, 09:27 AM UTC

   We continue to encounter issues with our NPP banking provider and we are working with them to resolve it. The following services as affected: • PayID Resolution • Account Resolution • PayID Enquiry • Register PayID • Update PayID Name • Update PayID Status As Azupay registers PayIDs asynchronously for payment requests, for in flight payment requests raised after the incident begun at 19:25 AEST customers using our payment request app may see a payID checkout but will be unable to process these payment requests with their bank, as the PayIDs will not yet be registered on the NPP network. These requests are being queued by our system and will be registered once our NPP banking partner recovers relevant services. Payment Requests raised prior to the incident should operate as expected and should be able to receive payments.

9. identified Nov 21, 2024, 10:01 AM UTC

   Our analysis shows the following impacts: This isn't a cyber incident. Elevated number of errors: * BSB enquiry * PayID enquiry Delays in processing: * Creation of PayID's via api * PayTo payment agreement creation * PayTo payment initiations 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.

10. identified Nov 21, 2024, 10:28 AM UTC

    Our analysis shows the following impacts: This isn't a cyber incident. Elevated number of errors: * BSB enquiry * PayID enquiry Delays in processing: * Creation of PayID's via api * PayTo payment agreement creation * PayTo payment initiations 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.

11. identified Nov 21, 2024, 10:55 AM UTC

    Our analysis shows the following impacts: This isn't a cyber incident. Elevated number of errors: * BSB enquiry * PayID enquiry Delays in processing: * Creation/Update of PayID's via api * PayTo payment agreement creation * PayTo payment initiations 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.

12. identified Nov 21, 2024, 11:31 AM UTC

    Our analysis shows the following impacts: This isn't a cyber incident. Elevated number of errors: * BSB enquiry * PayID enquiry Delays in processing: * Creation/Update of PayID's via api * PayTo payment agreement creation * PayTo payment initiations 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.

13. identified Nov 21, 2024, 12:03 PM UTC

    Our analysis shows the following impacts: This isn't a cyber incident. Elevated number of errors: * BSB enquiry * PayID enquiry Delays in processing: * Creation/Update of PayID's via api * PayTo payment agreement creation * PayTo payment initiations 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.

14. identified Nov 21, 2024, 12:39 PM UTC

    Our analysis shows the following impacts: This isn't a cyber incident. Elevated number of errors: * BSB enquiry * PayID enquiry Delays in processing: * Creation/Update of PayID's via api * PayTo payment agreement creation * PayTo payment initiations 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.

15. identified Nov 21, 2024, 01:07 PM UTC

    Our analysis shows the following impacts: This isn't a cyber incident. Elevated number of errors: * BSB enquiry * PayID enquiry Delays in processing: * Creation/Update of PayID's via api * PayTo payment agreement creation * PayTo payment initiations 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.

16. identified Nov 21, 2024, 01:39 PM UTC

    Our analysis shows the following impacts: This isn't a cyber incident. Elevated number of errors: * BSB enquiry * PayID enquiry Delays in processing: * Creation/Update of PayID's via api * PayTo payment agreement creation * PayTo payment initiations 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.

17. identified Nov 21, 2024, 02:09 PM UTC

    Our analysis shows the following impacts: This isn't a cyber incident. Elevated number of errors: * BSB enquiry * PayID enquiry Delays in processing: * Creation/Update of PayID's via api * PayTo payment agreement creation * PayTo payment initiations 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.

18. identified Nov 21, 2024, 02:41 PM UTC

    Our analysis shows the following impacts: This isn't a cyber incident. Elevated number of errors: * BSB enquiry * PayID enquiry Delays in processing: * Creation/Update of PayID's via api * PayTo payment agreement creation * PayTo payment initiations 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.

19. monitoring Nov 21, 2024, 03:13 PM UTC

    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.

20. resolved Nov 21, 2024, 04:11 PM UTC

    We believe the issue is now resolved. The underlying root cause was extended response times for requests our systems sent to our upstream NPP banking provider. 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.

Read the full incident report →