SecurePay Australia incident

SecurePay - Service Degradation - Transaction Processing

Notice Resolved View vendor source →

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

Started
Jan 18, 2024, 01:27 AM UTC
Resolved
Jan 18, 2024, 04:29 AM UTC
Duration
3h 1m
Detected by Pingoru
Jan 18, 2024, 01:27 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 Jan 18, 2024, 01:27 AM UTC

    We have identified an issue currently affecting SecurePay transactions. Our technical team is engaged and investigating further. If you have any questions, please contact our Customer Experience team on 1300 786 756 option 2.

  2. monitoring Jan 18, 2024, 01:34 AM UTC

    We have identified an issue resulting in transaction processing service degradation between 12.08 - 12.15PM. Service has been restored and we're currently monitoring the platform. If you have any questions, please contact our Customer Experience team on 1300 786 756 option 2.

  3. monitoring Jan 18, 2024, 01:42 AM UTC

    We are continuing to monitor for any further issues.

  4. resolved Jan 18, 2024, 04:29 AM UTC

    This incident which identified 510 Error Code affecting transaction processing has been resolved. Service has been restored and we're currently monitoring the platform. If you have any questions, please contact our Customer Experience team on 1300 786 756 option 2.