Is azupay down?

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.

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

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.

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.

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.

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.

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

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.

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.

**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.