The below information was provided to the Fattmerchant team from Authorize.net to assist merchants in updating their TLS software version. This bulletin is for merchants who have an ecommerce site using TLS/SSL versions 1.0 or below.
The Payment Card Industry Security Standards Council (PCI SSC) is extending the migration completion date to 30 June 2018 for transitioning from SSL and TLS 1.0 to a secure version of TLS (currently v1.1 or higher). Please visit the PCI Security Standard Councils website by clicking here to read further on the risks associated to the older TLS versions.
In preparation for this requirement, Authorize.Net disabled TLS 1.0 and TLS 1.1 on February 28, 2018. This affect merchants who currently use Authorize.net to process or as a gateway for their ecommerce sites.
Please contact your web developer or payment solution provider, as well as your web hosting company, to confirm that they can support TLS 1.2 for your API connections.
Please note that if the TLS version is not updated by the deadline you will not be able to process.
Note: If you are not using the current version of your web browser, please take a few moments to upgrade it now. Browsers released prior to 2014 may not support TLS 1.2. You can check your browser's TLS support by clicking here.
If you have any questions about this email or the upcoming TLS disablement, please refer to our TLS FAQs.
The following links can be given to the web/host developer to guide them through the update.
For SDK users please ensure that you have pulled and are using the most recent update for any SDK via Github and that TLS 1.2 is enabled and being used.
If you have any further questions on TLS and what it is and how if affects you please visit this link.
Please contact your web developer to assure you are operating on TLS versions 1.1 or higher.
If you have any questions or need assistance please contact Fattmerchant’s support team at (855) 550-3288 ext 2.