All Systems Operational

About This Site

StatusPage updates keep you informed about important developments related to our services due to planned or unplanned events. We let you know if there's any known issue, what's causing it, and when we expect things to return to normal or when scheduled bank outages are planned for maintenance, we inform you in advance.

If you are encountering issues not documented here, please raise a service desk request by following this link: https://azupay.atlassian.net/servicedesk/customer/portal/3

api Operational
90 days ago
100.0 % uptime
Today
dashboard Operational
90 days ago
100.0 % uptime
Today
Inbound to azupay payment processing Operational
90 days ago
100.0 % uptime
Today
Outbound from azupay payment processing Operational
90 days ago
100.0 % uptime
Today
External NPP Network Operational
90 days ago
99.98 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
May 7, 2026

No incidents reported today.

May 6, 2026
Completed - The scheduled maintenance has been completed.
May 6, 06:00 AEST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 6, 01:30 AEST
Update - Update on Business Impact Assessment:

As an update to this maintenance, Azupay will pause PayID registration events during the maintenance window. Once the maintenance is complete, we will process these registration events.

What can you expect from our APIs?

Payment Requests (Receive Inbound Payments via PayID)
During this maintenance window, you can submit PaymentRequests to our platform and they will be processed successfully, however PayID registration will be delayed. As this maintenance impacts the whole NPP network, it is expected that your end customer's banking app will not allow PayID lookup during this period either. We will process these delayed PayIDs immediately after the maintenance window.

Payments (Send outbound Payments)
Payments to PayID based recipients will error and return a failure code. If you make outbound payments during this window via a batch process, you may wish to delay until after the maintenance bulletin. Failed payments should be reviewed and re-attempted if appropriate.

Payment Agreements & Payment Initiations (Collect payments via PayTo)
Payment Agreement resolution to PayIDs will fail and payment initiations against PayID addressed based agreements are expected to fail. We recommend deferring creation of agreements and payment initiations until after the maintenance window.

May 4, 15:33 AEST
Scheduled - IMPORTANT: HIGH IMPACT MAINTENANCE

We have been informed this afternoon that Swift is performing maintenance on the NPPA network, and the addressing service used to create, update, search and delete PayIDs will be offline during this window. The outage window is expected to be 2:00-2:30 AM AEST on Wednesday, 6th May. This maintenance is upstream of Azupay, and will be affecting all NPP participants and banks.

This will impact your use of Azupay's products and services during this window. PayID lookup resolutions will fail, and PayID registrations will be unavailable.

Expected Impact per product:
- PaymentRequests (PayID) - Registrations of PaymentRequests will fail, and end customers will be unable to make payments to PayIDs as lookups will fail in their banking apps.
- PaymentAgreements (PayTo)- Agreement attempts to PayIDs will fail to resolve the PayIDs and will fail.
Payments)
- Payments (PayID) - Outbound Payments to PayIDs will fail, as the PayID will be unresolvable.

Azupay is conducting an impact analysis and will provide further guidance on recommendations for clients during this maintenance window by mid next week, and what behaviour you can expect from our APIs during the outage window.

If you have any questions, please raise a support request via our Service Desk at the following link: https://azupay.atlassian.net/servicedesk/customer/portal/3

Additional information on change window:

Swift have advised they need to undertake maintenance on the Addressing Service which will require suspension of the Addressing Service for up to 30 minutes in PROD. The change window details are below.

Change Start Date and Time: 6 May 2026 @ 01:30 AEST
Change End Date and Time: 6 May 2026 @ 06:00 AEST

As part of this change, the Production NPP Addressing Service will be suspended, for approximately 30 minutes.

The outage window is noted below.

Suspension Commencement: 6 May 2026 @ 02:00 AEST
Suspension Completion: 6 May 2026 @ 02:30 AEST

Apr 24, 17:13 AEST
May 5, 2026

No incidents reported.

May 4, 2026

No incidents reported.

May 3, 2026

No incidents reported.

May 2, 2026

No incidents reported.

May 1, 2026

No incidents reported.

Apr 30, 2026
Resolved - 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.

Apr 30, 09:34 AEST
Monitoring - 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.

Apr 29, 18:48 AEST
Identified - We are observing a recovery in impacted services as of 18:10 AEST and will continue to monitor to confirm resolution.
Apr 29, 18:22 AEST
Investigating - 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.

Apr 29, 18:05 AEST
Apr 29, 2026
Apr 28, 2026

No incidents reported.

Apr 27, 2026

No incidents reported.

Apr 26, 2026

No incidents reported.

Apr 25, 2026

No incidents reported.

Apr 24, 2026

No incidents reported.

Apr 23, 2026
Completed - The scheduled maintenance has been completed.
Apr 23, 06:00 AEST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Apr 23, 02:00 AEST
Scheduled - Our NPP banking partner will be performing scheduled maintenance on from 2:00 am to 6:00 am (Sydney Time).

Impact

• Brief, intermittent disruptions (under 60 seconds) may occur in NPP payment processing.
• Azupay will queue and automatically reattempt affected transactions.
• This may cause a short delay (a few minutes) in transaction processing and webhook confirmations.
• No action is required from clients.

For any questions, please contact our service desk:

Portal: Azupay Service Desk

Email: support@azupay.atlassian.net

Regards,
The Azupay Team

Apr 17, 14:53 AEST