SecurePay - Service Degradation - Fiserv Transaction Processing

Incident Report for SecurePay

Resolved

All services are stable.
Posted Jul 01, 2025 - 12:11 AEST

Monitoring

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.
Posted Jul 01, 2025 - 11:27 AEST

Update

A fix is being implemented, a further update will be posted when the fix is live.
Posted Jul 01, 2025 - 10:49 AEST

Update

A possible fix has been identified, and is being tested.
We will continue to provide updates as we work towards a solution.
Posted Jul 01, 2025 - 10:13 AEST

Identified

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.
Posted Jul 01, 2025 - 09:55 AEST

Update

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.
Posted Jul 01, 2025 - 09:11 AEST

Investigating

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.
Posted Jul 01, 2025 - 09:06 AEST
This incident affected: Payment Processing - API (XML API, Java API), Payment Processing - Web (SecureFrame, DirectPost, SecureBill), Payment processing - IVR, and Payment processing - Batch.