Zepto Payments AU incident

Incident Awareness Update from Zepto Inbound NPP Payments

Major Resolved View vendor source →

Zepto Payments AU experienced a major incident on March 6, 2023 affecting NPP Transactions [Outbound], lasting 1h 39m. The incident has been resolved; the full update timeline is below.

Started
Mar 06, 2023, 05:08 AM UTC
Resolved
Mar 06, 2023, 06:48 AM UTC
Duration
1h 39m
Detected by Pingoru
Mar 06, 2023, 05:08 AM UTC

Affected components

NPP Transactions [Outbound]

Update timeline

  1. investigating Mar 06, 2023, 05:08 AM UTC

    Dear Valued Zepto Customer, We have noticed degraded performance affecting inbound NPP Payments. Incident Start: 06/03/2023, 3:28 PM (Sydney Time) Affected: Inbound NPP This is causing delays in receiving PayID payments and inbound NPP payments. Please subscribe to our status page updates by visiting https://status.zepto.money/ as we will be posting updates until resolution. We will provide further updates shortly. We’re here for you, Zepto

  2. investigating Mar 06, 2023, 06:06 AM UTC

    Dear Valued Zepto Customer, There is intermittent degraded performance affecting inbound NPP transactions. We are seeing inbound NPP transactions start to process as normal. Transactions affected: Inbound NPP Transactions Once this incident has been resolved, a PIR will be issued. We’re here for you, Zepto

  3. investigating Mar 06, 2023, 06:34 AM UTC

    Dear Valued Zepto Customer, At 5:30 PM, inbound NPP service was restored. This issue resulted in some inbound NPP payments being delayed. All new inbound NPP payments are being processed as normal while we continue to work through the backlog. We sincerely apologise to our customers and partners for any inconvenience caused due to this incident. A Post Incident Report (PIR) will be issued in the coming days. As always, for any queries that need immediate attention, don’t hesitate to contact our Support Team through your portal, email us at [email protected] or contact your Zepto Account Manager directly. Team Zepto

  4. resolved Mar 06, 2023, 06:48 AM UTC

    This incident has been resolved.