SecurePay Australia incident

SecurePay - Service Degradation - Fiserv Transaction Processing

Notice Resolved View vendor source →

SecurePay Australia experienced a notice incident on March 14, 2025 affecting Payment Processing - API (XML API, Java API) and Payment Processing - Web (SecureFrame, DirectPost, SecureBill) and 1 more component, lasting 56m. The incident has been resolved; the full update timeline is below.

Started
Mar 14, 2025, 02:08 AM UTC
Resolved
Mar 14, 2025, 03:05 AM UTC
Duration
56m
Detected by Pingoru
Mar 14, 2025, 02:08 AM UTC

Affected components

Payment Processing - API (XML API, Java API)Payment Processing - Web (SecureFrame, DirectPost, SecureBill)Payment processing - IVRPayment processing - BatchMerchant PortalSecurePay Test EnvironmentPayment Processing - SecurePay API

Update timeline

  1. identified Mar 14, 2025, 02:08 AM UTC

    We have identified an issue currently affecting a section of SecurePay Transactions. Merchants using Fiserv or First Data as their acquirer are experiencing declined transactions with 123 and 124 response codes. Fiserv have confirmed they're currently investigating the issue. If you have any questions, please contact our Customer Experience team on 1300 786 756 option 2.

  2. resolved Mar 14, 2025, 03:05 AM UTC

    Fiserv have confirmed the issue has been resolved. Transactions are now processing as per normal. During this time, transactions may have declined with 123, 124, 126 and 915 response codes. If you have any questions, please contact our Customer Experience team on 1300 786 756 option 2.