SecurePay system upgrade to TLS 1.2

Scheduled Maintenance Report for SecurePay

Completed

Due to a large number of Merchants that have not been able to make the required changes, we are postponing this change to the 13th June 2018. This is only to provide an additional timeframe so merchants can make required changes before cutover to TLS 1.2
A new mainanance message will be sent out with updated details shortly.

Posted May 28, 2018 - 08:44 AEST

In progress

Scheduled maintenance is currently in progress. We will provide updates as necessary.

Posted May 28, 2018 - 08:00 AEST

Scheduled

SecurePay is upgrading its systems to the latest security standards. All merchant API communications with SecurePay will need to use TLS 1.2.

Find out more - https://www.securepay.com.au/developers/tlsv1.2-upgrade-information/

All SecurePay services will be available during this maintenance window.

Posted Aug 21, 2017 - 09:44 AEST

This scheduled maintenance affected: Payment Processing - API (XML API, Java API), Payment Processing - Web (SecureFrame, DirectPost, SecureBill), Payment processing - Batch, and Merchant Portal.