azupay incident

Incident NPP Platform experiencing PayID registration issue. 15th October 2025 - 4:47 PM AEDT

Minor Resolved View vendor source →

azupay experienced a minor incident on October 15, 2025 affecting External NPP Network, lasting 3h 18m. The incident has been resolved; the full update timeline is below.

Started
Oct 15, 2025, 05:56 AM UTC
Resolved
Oct 15, 2025, 09:14 AM UTC
Duration
3h 18m
Detected by Pingoru
Oct 15, 2025, 05:56 AM UTC

Affected components

External NPP Network

Update timeline

  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.