SecurePay Australia Outage History

SecurePay Australia is up right now

SecurePay Australia had 6 outages in the last 2 years totaling 11h 42m of downtime — averaging 0.2 incidents per month.

There were 6 SecurePay Australia outages since May 21, 2025 totaling 11h 42m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://securepay.statuspage.io

Critical May 19, 2026

Payment IVR Outage

Detected by Pingoru
May 19, 2026, 11:50 PM UTC
Resolved
May 20, 2026, 03:46 AM UTC
Duration
3h 55m
Affected: Payment processing - IVR
Timeline · 4 updates
  1. investigating May 19, 2026, 11:50 PM UTC

    We have identified that customers' payment IVRs are unable to connect as of approximately 08:20 am AEST. Callers may be able to ring the number but later disconnected when attempting to pay over the phone. We are currently investigation this issue. We apologise for the inconvenience.

  2. investigating May 20, 2026, 12:23 AM UTC

    Our team is continuing to work with our telephony vendor to resolve this issue. This is also impacting our Support phone number. To contact us during this issue, please dial landline +61 3 9245 6751 to speak to our team.

  3. monitoring May 20, 2026, 02:55 AM UTC

    A fix has been implemented by our provider, and calls are being routed as normal. Our team is monitoring the service to ensure no further issues are in play. Our support number 1300 786 756 is once again available.

  4. resolved May 20, 2026, 03:46 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice April 13, 2026

Payment IVR Degradation

Detected by Pingoru
Apr 13, 2026, 03:16 AM UTC
Resolved
Apr 13, 2026, 04:44 AM UTC
Duration
1h 27m
Affected: Payment processing - IVR
Timeline · 4 updates
  1. investigating Apr 13, 2026, 03:16 AM UTC

    We have identified that customers' payment IVRs are unable to connect from 11:00 am AEST. Callers may be able to ring the number but later disconnected when attempting to pay over the phone. We are currently investigation this issue. Sorry for the inconvenience.

  2. identified Apr 13, 2026, 03:36 AM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Apr 13, 2026, 03:51 AM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Apr 13, 2026, 04:44 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 21, 2026

Transaction Processing Issue - ANZ Acquired

Detected by Pingoru
Feb 21, 2026, 08:57 AM UTC
Resolved
Feb 21, 2026, 10:33 AM UTC
Duration
1h 35m
Affected: Payment Processing - API (XML API, Java API)Payment Processing - Web (SecureFrame, DirectPost, SecureBill)Payment processing - IVRPayment processing - BatchPayment Processing - SecurePay API
Timeline · 2 updates
  1. identified Feb 21, 2026, 08:57 AM UTC

    Our partner has confirmed they are experiencing degradation on their bank link and are investigating the issue. Merchants with ANZ for their acquirer are experiencing some errors while payment processing. We are investigating with the Vendor and will provide updates once available.

  2. resolved Feb 21, 2026, 10:33 AM UTC

    We've received confirmation that the issue has been resolved by our vendor, and transactions are now processing as expected.

Read the full incident report →

Notice September 28, 2025

SecurePay Website Unavailable - No Impact To Transaction Processing

Detected by Pingoru
Sep 28, 2025, 11:27 PM UTC
Resolved
Sep 29, 2025, 12:21 AM UTC
Duration
53m
Timeline · 2 updates
  1. investigating Sep 28, 2025, 11:27 PM UTC

    SecurePay's website is unavailable. This does NOT affect the Merchant Portal, nor does it affect transaction processing. The merchant portal is still accessible via https://login.securepay.com.au/v4/ We're working on bringing our website back up.

  2. resolved Sep 29, 2025, 12:21 AM UTC

    SecurePay is available now. This incident has been resolved.

Read the full incident report →

Major June 30, 2025

SecurePay - Service Degradation - Fiserv Transaction Processing

Detected by Pingoru
Jun 30, 2025, 11:06 PM UTC
Resolved
Jul 01, 2025, 02:11 AM UTC
Duration
3h 4m
Affected: Payment Processing - API (XML API, Java API)Payment Processing - Web (SecureFrame, DirectPost, SecureBill)Payment processing - IVRPayment processing - Batch
Timeline · 7 updates
  1. 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.

  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.

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

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

  5. identified Jul 01, 2025, 12:49 AM UTC

    A fix is being implemented, a further update will be posted when the fix is live.

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

  7. resolved Jul 01, 2025, 02:11 AM UTC

    All services are stable.

Read the full incident report →

Minor May 21, 2025

SecurePay Direct Post Degradation

Detected by Pingoru
May 21, 2025, 06:16 AM UTC
Resolved
May 21, 2025, 07:01 AM UTC
Duration
45m
Affected: Payment Processing - Web (SecureFrame, DirectPost, SecureBill)
Timeline · 3 updates
  1. identified May 21, 2025, 06:16 AM UTC

    SecurePay Direct Post is currently affected by a degradation. Some end users may receive an "invalid request" message after attempting to submit a payment, and the transaction will not be processed. Our team is working to resolve the issue.

  2. monitoring May 21, 2025, 06:41 AM UTC

    A fix has been implemented and our team is monitoring the service. Customers should be able to transact as normal.

  3. resolved May 21, 2025, 07:01 AM UTC

    After a period of monitoring, we have confirmed that the issue is resolved.

Read the full incident report →