The Authorize.Net Developer Blog

Posts from Authorize.Net employees, community members and experts about integrating with the Authorize.Net Payment Gateway: sample code, tutorials, and problem-solving techniques, just to name a few.

TLS 1.1 and 1.0 Disabled in Sandbox on April 30, 2017 - Updated 2X

by Administrator Administrator ‎04-17-2017 01:38 PM - edited ‎08-02-2017 12:40 PM (62,484 Views)

8/2/2017 - Updated producttion date to February 28, 2018


4/27/2017 - Updated production date of Sept 18, 2017.




As you may be aware, new PCI DSS requirements state that all payment systems must disable early TLS by 2018.


In preparation for this requirement, Authorize.Net plans to disable TLS 1.0 and TLS 1.1 on the following dates:


  • Sandbox -- April 30, 2017
  • Production – February 28, 2018

We are disabling the sandbox in advance of production to allow you to time to test your solution and ensure you are no longer using TLS 1.0 or 1.1.


Please check the code for your solutions and systems to confirm that they can default to TLS 1.2 for your API connections.


You can review our API Best Practices for details about TLS 1.2 platform support, cipher recommendations, and other integration suggestions:


by Tri
on ‎05-01-2017 07:08 AM

today is 5/1/2017, can you please confirm if disbaled TLS 1.0 and TSL 1.1 on sandbox?

by DavidH
on ‎05-01-2017 09:41 AM

I'm also wondering if the older TLS versions have been disabled yet. Because according to , as of Mon, 01 May 2017 15:53:53 UTC, TLS 1.0 and 1.1 are still enabled.

by Administrator Administrator
‎05-01-2017 01:58 PM - edited ‎05-01-2017 02:27 PM

Hello @DavidH @Tri


Yes, updates to remove TLS 1.0 and 1.1 in the sandbox are now complete