SecurePay Australia incident
SecurePay - Service Degradation - Fiserv Transaction Processing
SecurePay Australia experienced a major incident on June 30, 2025 affecting Payment Processing - API (XML API, Java API) and Payment Processing - Web (SecureFrame, DirectPost, SecureBill) and 1 more component, lasting 3h 4m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jun 30, 2025, 11:06 PM UTC
Merchants using Fiserv as their acquirer are experiencing declined transactions with a 124 declined code. Our technical team is actively engaged and investigating the matter further. If you have any questions, please get in touch with our Customer Experience team on 1300 786 756 option 2.
- investigating Jun 30, 2025, 11:11 PM UTC
Merchants using Fiserv or First Data, Westpac, and St George as their acquirer are experiencing declined transactions with a 124 declined code. Our technical team is actively engaged and investigating the matter further.
- identified Jun 30, 2025, 11:55 PM UTC
Impact is ongoing, with 124 failure codes still being received. Our technical teams are working on a solution. We will continue to provide updates as we work towards a solution.
- identified Jul 01, 2025, 12:13 AM UTC
A possible fix has been identified, and is being tested. We will continue to provide updates as we work towards a solution.
- identified Jul 01, 2025, 12:49 AM UTC
A fix is being implemented, a further update will be posted when the fix is live.
- monitoring Jul 01, 2025, 01:27 AM UTC
A fix has been implemented, and merchants should now see their transactions approving as normal. We are monitoring service health following the fix. Transactions declined during the impact can now be reattempted. If you have any questions, please get in touch with our Customer Experience team on 1300 786 756 option 2.
- resolved Jul 01, 2025, 02:11 AM UTC
All services are stable.