Important Notice for Authorize.Net Users
Merchants were made aware of the plan by Authorize.Net to remove TLS versions prior to 1.2 throughout 2017 and the time for the changes to take effect are right around the corner on February 28, 2018.
To avoid any interruptions in card acceptance, businesses need to update to TLS version 1.2 no later than this date. Without these protocols in place, your business might be unable to process payments after February 28, 2018.
Temporary Disablement of TLS 1.0/1.1 Will Help Merchants Identify if They Need to Upgrade
All Authorize.Net users should have been notified that Authorize.Net will temporarily disable all older TLS protocols for a few hours on January 30 and February 8 to help merchants identify if they have an older version that needs to be updated to TLS 1.2.
If your business is using one of the older TLS protocols, then you will not be able to process transactions for a short period of time on both January 30 and February 8.
Please see the timeframes below:
- January 30 between 9:00 am and 1:00 pm PST – Akamai-enabled API connections
- February 8 between 11:00 am and 1:00 pm PST – All other API connections
How Does It Affect My Business?
Without taking the measures to ensure your version of TLS meets the proper PCI standards, you may be unable to process transactions. This could greatly impact your business.
What Do I Need to Do?
Call your website developer, web-hosting provider, or software/POS provider to ask them:
- “Does my website, shopping cart, software, or POS support TLS version 1.2?”
- If not, your provider will need to enable the proper protocols to support TLS 1.2 before the February deadline
- If changed, you should test your system for proper functionality.
To Learn More About This Update:
Contact us online or call 1-800-621-8931.
Subscribe to Card Talk
Our monthly newsletter delivers the latest payments news straight to your inbox