Is Azupay Down Right Now? Check if there is a current outage ongoing.

Our NPP banking partner will be conducting scheduled maintenance on Thursday, 05 June 2025 from2:00 am to 6:00 am (Sydney Time).Impact:During this maintenance window, under 60 secs intermittent disruptions are expected to NPP payment processing.Azupay will gracefully queue and re-attempt affected transactions on behalf of clients during this period , which could result in a slight delay of a few minutes for affected transactions and a delay on webhook confirmations of transactions. No action is required. If you have any questions, please reach our via our service desk at https://azupay.atlassian.net/servicedesk/customer/portal/3 or support@azupay.atlassian.netRegards, the Azupay team

Scheduled maintenance is currently in progress. We will provide updates as necessary.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

We are continuing to investigate this issue.

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.

The issue has now been resolved and all services are operating as expected. The root cause of the problem is still being investigated by the downstream service 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.

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 aware of industry wide issues with looking up PayIDs in customer's online banking systems. 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.

We have monitored services for 30 minutes post incident resolution and have confirmed systems are back at normal operational capability and are closing this incident. Our banking partner has confirmed they experienced a degradation in a compute node associated with PayId registration and de-registration when bringing NPP services back up post planned maintenance which affected service resumption between 12:28AM and 12:54AM, and caused a degradation in our ability to process queued de-registration events due to a prolonged backlog of requests. We were able to fully process this backlog and resume services by 1:13AM. This issue occurring within the planned maintenance window of 12:00 am to 5:00 am but outside of our planned outage window between 12:15AM and 12:30 communicated in https://status.azupay.com.au/incidents/6jkvwk9p4q53. Thank you for your patience as we worked on resolving this issue. Regards, the Azupay Team.

The PayId de-registration queue has been cleared and payId registration has been re-enabled. We are now monitoring to confirm normal system operations.

The issue causing errors has been resolved and a backlog of payment de-registrations are being processed. During this process we have paused registration of new PayIds and expect to be able to re-enable PayId registrations by 1:20.

Post planned outage we are experiencing issues with De-registration of PayId aliases and have delayed re-enabling alias registrations for new PayIds. We have now enabled PayId registration and are investigating with our banking partner regarding the degradation of De-registrations of PayIds.

This issue has been resolved via a fix. Search results for payment requests can now be paginated through as expected via the pagination controls at the bottom of the search screen, up to the volume of transactions set in the search "Configure Results" screen.

We have identified an issue currently affecting our dashboard search functionality that will limit records being returned via Payment Request searches to approximately 700 records. The cause of the issue has been identified and a fix is in development. As a work around, search can be used across shorter time periods, and the Reports download functionality can be used to retrieve all transactions for the period via https://dashboard.azupay.com.au/reports

We are aware of a now resolved issue in processing outbound payments due to a short outage encountered last night (at approximately 3am) by our NPP provider. This issue has only affected a small number of our customers processing payments during this window. Affected customers will be communicated with directly and if you have not been affected, no action is required. This has resulted is a small number of payments failing and these will need to be resubmitted. Our recommendations are as follows: * Please inform your customers of delays where applicable. * Reprocess required outbound payments that have failed.

Our analysis shows the following impacts: This isn't a cyber incident. Elevated number of errors: * Outbound payments via api Our recommendations are as follows: * Please inform your customers of delays where applicable. * The errors were encountered from 11:23am to 11:56am GMT+11. During this time, any requests to make outbound payments via /payment API would have been met with a 5xx error. The payments were not accepted by Azupay and you will need to re-submit them. 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. The root cause of this incident was in system errors encountered by our NPP provider. This was not a cyber security incident. 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 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.

Our analysis shows the following impacts: This isn't a cyber incident. Delays in processing: * Outbound payments via api * Processing of inbound payments to PayID's from payer's bank * Creation of PayID's via api 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 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.

All NPP services are now operating normally. We do not believe there are any residual issues due to the outage. We apologise for the inconvenience caused.

CBA have restored their NPP connection and we are now seeing payments flow in both directions as expected. We will continue closely monitoring the system for the rest of the evening.

The issue impacting inbound and outbound payments for CBA accounts is ongoing. We will continue to monitor and provide updates here as they come to hand.

The issue impacting inbound and outbound payments for CBA accounts is ongoing. We will continue to monitor and provide updates here as they come to hand.

CBA has advised they are currently experiencing a wide spread system outage and have suspended themselves from the NPP network. Inbound payments from CBA accounts will not be received until CBA restores it's systems and outbound payments will need to be resubmitted once CBA is online 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. The root cause of the incident were system issues encountered by our npp connectivity provider affecting the processing of outbound payments. Whilst the majority of outbound payments were retried and settled. Approximately 279 will require manual intervention from azupay. These will be re-processed in the coming days. This was not a cyber incident. 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 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.

Our analysis shows the following impacts: This isn't a cyber incident. Delays in processing: * Outbound payments via api 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.

Our NPP provider has advised that issue is now resolved and will continue closely monitoring the performance of the system. We expect the current backlog of outbound payments to be cleared in the next 30 minutes. 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.

Our analysis shows the following impacts: This isn't a cyber incident. Delays in processing: * Outbound payments via api * Returns of invalid payments 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 have been advised by our NPP provider that there is an issue impacting outbound NPP transactions. Inbound payments, including PayID registrations are now performing normally. Our analysis shows the following impacts: Delays in processing: * Outbound payments via api - delayed settlement 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 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.

We believe the issue is now resolved. If you are still encountering issues, please do reach out using our service desk: https://azupay.atlassian.net/servicedesk/customer/portal/3 including any relevant 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 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 await further advice from our payments processing provider. Our analysis shows the following impacts: Elevated number of errors: * None Delays in processing: * Incoming payment refunds Our recommendation(s): * 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 await further advice from our payments processing provider. Our analysis shows the following impacts: Elevated number of errors: * None Delays in processing: * PayTo payment agreement creation * Creation of PayID's * Incoming payment refunds Our recommendation(s): * 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 await further advice from our payments processing provider. Our analysis shows the following impacts: Elevated number of errors: * None Delays in processing: * PayTo payment agreement creation * Creation of PayID's * Incoming payment refunds Our recommendation(s): * 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 await further advice from our payments processing provider. Our analysis shows the following impacts: Elevated number of errors: * None Delays in processing: * PayTo payment agreement creation * Creation of PayID's Our recommendation(s): * 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.

Good morning! We can confirm that outbound payments are entering SETTLED status at the usual rate. There remain a small batch of outbound payments stuck in PENDING status for which we await further instructions from our payments processing provider. Please refer to the following section for updates on other functions of the platform. Our analysis shows the following impacts: Elevated number of errors: * None Delays in processing: * PayTo payment agreement creation * PayTo payment initiations * Creation of PayID's Our recommendation(s): * 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 continue to await further updates from our payments processing provider. We will suspend further updates on the status page until approximately 5AM AEDT Wednesday 8th Feb 2023. We apologise for the inconvenience caused.

We have received updates from our payment processing provider indicating that some outbound payments which have already gone into PENDING status will take a bit more time to become SETTLED. The rest may have already gone into SETTLED status. We continue to observe intermittent errors and delays. Our analysis shows the following impacts: Elevated number of errors: * BSB enquiry api * PayID enquiry api * Client management api Delays in processing: * PayTo payment agreement creation * PayTo payment initiations * Outbound payments * Creation of PayID's * Processing of inbound payments to PayID's from payer's bank Our recommendation(s): * 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 continue to await further updates from our payments processing provider. Our analysis shows the following impacts: Elevated number of errors: * BSB enquiry api * PayID enquiry api * Client management api Delays in processing: * PayTo payment agreement creation * PayTo payment initiations * Outbound payments * Creation of PayID's * Processing of inbound payments to PayID's from payer's bank Our recommendation(s): * 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.

Most transactions are flowing albeit at a rate slower than usual. We continue to await further updates from our payments processing provider. Our analysis shows the following impacts: Elevated number of errors: * BSB enquiry api * PayID enquiry api * Client management api Delays in processing: * PayTo payment agreement creation * PayTo payment initiations * Outbound payments * Creation of PayID's * Processing of inbound payments to PayID's from payer's bank Our recommendation(s): * 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 await further updates from our payments processing provider on their progress restoring services. Our analysis shows the following impacts: Elevated number of errors: * BSB enquiry api * PayID enquiry api * Client management api Delays in processing: * PayTo payment agreement creation * PayTo payment initiations * Outbound payments * Creation of PayID's * Processing of inbound payments to PayID's from payer's bank Our recommendation(s): * 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.

It appears as though there are some still residual issues within our payments processing provider. We await further updates from them on their progress restoring services/ Our analysis shows the following impacts: Elevated number of errors: * BSB enquiry api * PayID enquiry api * Client management api Delays in processing: * PayTo payment agreement creation * PayTo payment initiations * Outbound payments * Creation of PayID's * Processing of inbound payments to PayID's from payer's bank Our recommendation(s): * 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 await further updates from our payment processing provider on their progress restoring services. Our analysis shows the following impacts: Elevated number of errors: * BSB enquiry api * PayID enquiry api * Client management api Delays in processing: * PayTo payment agreement creation * PayTo payment initiations * Outbound payments * Creation of PayID's * Processing of inbound payments to PayID's from payer's bank Our recommendation(s): * 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.

Our payments processing provider has advised that they have identified the issue are working to restore services. Our analysis shows the following impacts: Elevated number of errors: * BSB enquiry api * PayID enquiry api * Client management api Delays in processing: * PayTo payment agreement creation * PayTo payment initiations * Outbound payments * Creation of PayID's * Processing of inbound payments to PayID's from payer's bank Our recommendation(s): * 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 await further updates from our payments processing provider on the issue. Our analysis shows the following impacts: Elevated number of errors: * BSB enquiry * PayID enquiry Delays in processing: * PayTo payment agreement creation * PayTo payment initiations * Outbound payments via api * Creation of PayID's via api * Processing of inbound payments to PayID's from payer's bank Our recommendation(s): * 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 await further updates from our payments processing provider on the issue. Our analysis shows the following impacts: Elevated number of errors: * BSB enquiry * PayID enquiry Delays in processing: * PayTo payment agreement creation * PayTo payment initiations * Outbound payments via api * Creation of PayID's via api * Processing of inbound payments to PayID's from payer's bank Our recommendation(s): * 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.

Our analysis shows the following impacts: Elevated number of errors: * BSB enquiry * PayID enquiry Delays in processing: * PayTo payment agreement creation * PayTo payment initiations * Outbound payments via api * Creation of PayID's via api * Processing of inbound payments to PayID's from payer's bank 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.

Our analysis shows the following impacts: Elevated number of errors: * BSB enquiry * PayID enquiry Delays in processing: * Outbound payments via api * Creation of PayID's via api * Processing of inbound payments to PayID's from payer's bank 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 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.

We believe the issue is now resolved. 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 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.

Our analysis shows the following impacts: Elevated number of errors: * Outbound payments via api * BSB enquiries via api Delays in processing: * Outbound payments via api of around 4 minutes * Creation of PayID's via api of around 5 minutes * Processing of inbound payments to PayID's from payer's bank may be delayed. However, we can see payments trickling through. Please do subscribe to our status page for the latest and most accurate information. We apologise for the inconvenience caused.

Our analysis shows the following impacts: Elevated number of errors: * Outbound payments via api * BSB enquiries via api Delays in processing: * Outbound payments via api of around 10 minutes * Creation of PayID's via api of around 5 minutes * Processing of inbound payments to PayID's from payer's bank may be delayed. However, we can see payments trickling through at a reduced rate Please do subscribe to our status page for the latest and most accurate information. We apologise for the inconvenience caused.

We are continuing our investigation and will provide a detailed update as soon as one becomes available. Monitoring of our systems show that some inbound payments to PayID's from payer bank's are making their way through. Although it's a small number compared to the usual volume of traffic. Please do subscribe to our status page for the latest and most accurate information. We apologise for the inconvenience caused.

Our analysis shows the following impacts: Elevated number of errors: * Outbound payments via api * BSB enquiries via api Delays in processing: * Outbound payments via api * Creation of PayID's via api * Processing of inbound payments to PayID's from payer's bank. The last payment messages received from the wider npp network were at 8:30pm AEDT Please do subscribe to our status page for the latest and most accurate information. We apologise for the inconvenience caused.

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.

We believe the issue is now resolved. 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 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 currently experiencing a delay registering new PayIDs. 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.

All daily reports for 24th October have been generated for all clients and are available for download via the Merchant Dashboard. We apologise for the delay and any inconvenience caused.

The team is continuing to work on the issue and we expect to have the outstanding reports generated by 4pm today. We will post an update here once the reports have been regenerated successfully. We apologise for the delay and any inconvenience caused.

Daily report generation for some clients has been delayed and are not currently available for download through the Merchant Dashboard. We have identified the issue and we are currently working on a fix. We will post an update here once the reports have been regenerated successfully. We apologise for the delay and any inconvenience caused.

Our NPP service provider has rectified the issue and NPP services have returned to normal operation. In addition: - All inbound and outbound payment queues have been cleared - Pending PayID registrations and deregistrations have been completed We will continue closely monitoring the system for the next few hours. Apologies for any inconvenience caused.

Restoration efforts at our NPP connectivity providers end are yielding system performance approaching previous levels. We apologise for the inconvenience caused, we will provide updates as and when they come through.

Restoration efforts at our NPP connectivity providers end are yielding more positive results but unfortunately are yet to return to their previous levels. We can see that inbound payments are arriving fairly consistently, nearly matching their previous levels. We can also confirm that attempts to make outbound payments, register PayID's are succeeding more often than not. We will continue to monitor the service and provide updates as and when they come. We apologise for the inconvenience caused.

Following restoration efforts at our NPP connectivity providers end, we can confirm the following: Some attempts to register PayID's are successful, some of your customer's may be able to use PayID's in their online banking platform. We have also noted some short bursts of pending payments arriving in our platform which should update PaymentRequest's in WAITING status to COMPLETE.

Efforts to restore services on our NPP connectivity suppliers end are continuing. Please refer to the update provided at 14:40 AEDT for details of impact. We apologise for the inconvenience caused, we will provide updates as and when they come through.

Efforts to restore services on our NPP connectivity suppliers end are continuing. Please refer to the update provided at 14:40 AEDT for details of impact. We apologise for the inconvenience caused, we will provide updates as and when they come through.

We have identified an issue with our supplier of NPP connectivity. The issue impacts a wide range of services including inbound and outbound payments, PayID registrations, etc. You may see the following behaviour: Outbound payments via POST /v1/payment may result in a 500 error or may not reach SETTLED status Inbound payments to PayID's created via our PaymentRequest api's may not be acknowledged in real time by azupay. PayID's created via our PaymentRequest api may not work in online banking apps We apologise for the inconvenience caused, we will provide updates as and when they come through.

We are investigating an issue with NPP payments and will provide further updates as soon as possible

This issue is now resolved. All pending outbound payments have been processed. Inbound payments will arrive if the payer's bank resubmits them or the payer resubmits them. Please reach us via the usual channels if you have any questions.

Thanks for contacting Azupay Support. Firstly, please ensure you subscribe to our status page. The Fast Payment system in Australia had an outage from approximately 7pm AEDT on 12/10/22 to 2.30am AEDT on 13/10/22. The Reserve Bank of Australia has advised that their settlement service has been restored as of 2.30am. There remains a significant number of transactions that were submitted during the period described above that are in a pending status and will be processed throughout the next 48hrs. Azupay will retry all outbound payments that are in a pending status. Azupay is aiming to complete these retries today. We will provide regular updates and advise if this changes via the status page. For payments made or expected to be received during this period – please consider the following: * It is recommended that you should not resubmit outbound payments that were submitted during the period that are in a pending status and/or not settled. * For inbound payments, there are the following dependency: * The initiating bank retrying the affected payments. Should you receive contact from your customers, it is advised they do not resubmit payments unless payments previously attempted have been returned to their account.

The industry-wide NPP outage has now been resolved. Some inbound payments are now being received but at a much reduced rate than normal. Outbound payments have been restored by our NPP service provider but will take longer than usual to transition to SETTLED status. Updates will be posted here as we receive further information. We appreciate your patience.

The industry-wide NPP outage remains unresolved and work is continuing to restore the service. Some inbound payments are now being received but at a much reduced rate than normal. Outbound payments have been suspended by our NPP service provider until the issue is resolve and clients will receive 500 - Service Unavailable errors on the Payment API until further notice. Updates will be posted here as we receive further information. We appreciate your patience.

We have been advised that the issue is across the NPP network. It's therefore affecting multiple banks. More updates will be provided as and when they become available.

We are continuing to await further updates from our supplier. We thank you for your patience.

This issue is also affecting settlement of outbound payments. Your attempts to make outbound payments may be met with a PENDING status for an extended period of time.

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

There are currently delays of at least 90 minutes receiving payments to PayID's created via Azupay. The issue appears to be upstream from us and we are investigating with our suppliers to identify the root cause.

This incident has been resolved.

Customers may experience a delay of up to 27 minutes between registering a PayID and having it available for use in online banking.

Customers may experience a delay of up to 33 minutes between registering a PayID and having it available for use in online banking. We are pleased to report that we expect this figure to continue to trend downwards through the implementation of some remediation actions on the azupay side.

We are currently experiencing a high volume of PayID registration requests. These are being processed and there is a delay of approximately 40 minutes between submitting a POST /v1/paymentRequest api call and the PayID becoming available for use in online banking.

This incident has been resolved.

Some outbound payments are getting stuck in PENDING status. Our npp supplier is currently investigating. We will provide further updates shortly.

Our NPP provider has confirmed the issue has been resolved. We'll continue to closely monitor the system for the next few hours.

We are now seeing consistent response times within SLAs from our NPP provider and will continue to monitor until they have confirmed the issue is closed.

System response time has improved but remains on the high side. We are continuing to monitor the situation and will post updates here again shortly.

Our supplier has acknowledged the issue and is working to resolve it. The impact remains the same as communicated previously.

Our supplier has acknowledged the issue and is working to resolve it. The impact remains the same as communicated previously.

You may encounter timeouts or significantly longer than usual response time trying to: - Register PayID via the POST /v1/paymentRequest - Enquiring about BSB via the POST /v1/accountEnquiry - Enquiring about PayID's via the POST /v1/payIDEnquiry - Making payments out via the POST /v1/payment We are continuing to receive payments where the PayID is already registered.

We are continuing to investigate this issue.

We are continuing to investigate this issue.

We have identified that some api's are intermittently failing altogether or timing out. We are currently investigating.

This incident has been resolved.

The system has recovered and we have cleared the backlog of outbound payments. We will continue to monitor the system. The next update will be tomorrow morning.

Our NPP service provider is still investigating this issue and aims to resolve it soon. A further update will be provided within 2 hours.

Our NPP provider is working to resolve the issue as soon as possible. We will provide another update by 6:30pm AEST.

We have identified the root cause and are waiting on our supplier to resolve an issue with outbound payment processing. In the meantime, you can continue to submit outbound payment requests but they will be delayed in their transition from CREATED to SETTLED.

We have detected an issue with settling outbound payments submitted via our API. The issue began at 2:20pm and at this stage is ongoing. Your should still see successful responses from our api, the impact is just increased latency between the transition from CREATED to SETTLED status.

Our NPP provider has rectified the issue and all systems are operating normally.

A fix has been implemented by our service provider and we will monitor for the next hour. Please report any further issues via the Azupay Help Centre.

Outbound payments are failing with error code L001. We are working with our NPP provider to identify and fix the issue.

In the past few hours there have been no failures to register PayID's. We are continuing to monitor the system for repeat errors.

We are continuing to monitor for any further issues.

We have not seen a repeat of the error since 10:30pm last night. We will continue to work with our supplier to identify the root cause of the issue.

We are continuing to await the results of investigations on our supplier side. Monitoring shows no further degradation of the system.

We are continuing to await the results of investigations on our supplier side. In the meantime, we can confirm that this error has not been encountered in the past hour.

Some customers are encountering intermittent errors registering PayID's using the POST /v1/paymentRequest api. Out of all the requests submitted across our customers over the past 2 days, 8% of these have encountered this error. There was a concentration of these errors around on the 20/04/2022 from 22:30pm to approximately 23:00 and again on the 21/04/2022 from 12:30pm to 2:30pm. This issue only affects the registration of PayID's occasionally. It does not affect the receipt of payments where the PayID is already registered. There is also no impact on any other functions of the Azupay platform. We have raised this with our supplier and will continue to provide updates.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

Cuscal are currently implementing a fix and the payment queues are clearing. Normal service should be restored shortly.

We are aware of an issue affecting inbound and outbound NPP payments. We have been notified by Cuscal that they are experiencing issues with their NPP connectivity and are currently investigating the cause of the problem. We are closely monitoring the situation with Cuscal and will provide updates here as information becomes available.

Calls to POST /v1/paymentRequest api are likely to have failed with error "Contact Support" between 10pm and midnight AEDT. As there is no longer an issue with the API, we will proceed to close this incident. Please do not hesitate to contact us if you encounter any other issues.

We are continuing to monitor for any further issues.

Our logs indicate that the majority of errors were encountered between 10pm and midnight on the 30th November 2021 GMT+11. With the last instance of the error being just before midnight. We will continue to monitor system status in the meantime.

We are seeing intermittent errors when customers are invoking POST /v1/paymentRequest calls. Customers may see a response body containing a message "Contact Support" with a 500 http status code.

This incident has been resolved.

NPPA Incident Notification: Cuscal / Bendigo and ING affecting Inbound and Outbound Processing Notifying participant: NPPA Institution experiencing difficulty: Cuscal Description Cuscal has reported an issue for NPP Payments affecting Inbound and Outbound Processing including all Identified Institutions. The issue is also affecting Bendigo and ING • Cuscal Limited (CUSCAU2SXXX) • BBL Bendigo and Adelaide Bank Limited (BENDAU3BXXX) • ING Bank (Australia) Limited (INGBAU2SXXX) Incident Start Date/time: 04/08/2021 16:40 AEST Incident End Date/time: Ongoing Impact: The issue affects Inbound and Outbound payments for Cuscal, ING and Bendigo including Identified institutions

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are continuing to investigate this issue.

Westpac (WPACAU2SXXX) has reported an issue for NPP Payments affecting some of their Outbound processing. The issue is impacting 50% of outbound payments from one of their channels. Incident Start Date/time: 05/07/2021 10:00am AEST Incident End Date/time: Ongoing Impact: Outbound Payments Westpac is continuing to investigate the issue and an update will be provided when the issue is resolved.

Incident Start Date/time: 03/07/2021 00:45am AEST Incident End Date/time: 03/07/2021 02:40am AEST

We use AWS Cognito to provide our security layer for the dashboard. Unfortunately, we failed to configure the redirect url correctly for the uat environment resulting in this error. The issue was identified and resolved at around 1pm on the same day. We apologise for any inconvenience caused.

Users would have been unable to access the dashboard in the uat environment. The error was encountered after attempting to sign-in was: 'An error was encountered with the requested page.'.

This incident has been resolved.

Monitoring shows that the status of refunds is now updating to RETURN_COMPLETE immediately as intended. We will continue to monitor the situation and leave this incident open.

Just a quick update. Our supplier is continuing to work on a resolution for this issue.

Our supplier is continuing to work on a resolution for this issue.

The issue has been identified and a fix is being implemented.

We are currently experiencing an issue where the status of refunds is not updating from RETURN_IN_PROGRESS to RETURN_COMPLETE. Despite that, we can confirm that the funds are being returned to the source account. We are working with our supplier to resolve the issue. There is no impact if a refund is not requested.

An incorrect deployment to the environment caused the dashboard tool in uat to become unavailable. We apologise for the inconvenience caused. Please do reach out if you encounter any further issues.

This incident has been resolved.

An incorrect deployment to the environment caused the dashboard tool in uat to become unavailable. We apologise for the inconvenience caused. Please do reach out if you encounter any further issues.

We are continuing to investigate this issue.

We are currently investigating this issue.

This incident has been resolved.

A fix has been implemented and we are now monitoring the results

Fyi, the connectivity issues were first detected on the 2020-10-17 at 08:09:27 GMT+11:00

Our supplier is continuing restoration of their environment. Another update to be provided in an hour.

There is an outage on our suppliers side and they have informed us that their systems will be restored at 11:30am GMT+11

There may be an elevated number of api errors in the following api endpoints POST /v1/paymentRequest POST /v1/accountEnquiry POST /v1/payIDEnquiry POST /v1/payment

We're experiencing an elevated level of errors in the following api's in our UAT environment POST /v1/paymentRequest POST /v1/accountEnquiry POST /v1/payIDEnquiry POST /v1/payment An issue with one of our supplier systems is causing these api's to return 504 GATEWAY_TIMEOUT responses.