ShopSite Knowledgebase :: February 2009 email from Authorize.net regarding end of support for SSL 2.0 protocol

Knowledgebase Home

Search the Knowledgebase

Browse by Category

Knowledgebase Home > Payment Processing

February 2009 email from Authorize.net regarding end of support for SSL 2.0 protocol

Product: ALL
Version: ALL
Platform: ALL

Will my ShopSite's integration with Authorize.net continue to work after they end support for connections to their APIs via the SSL 2.0 protocol? Does this affect my ShopSite? Is there anything that I need to do?

Solution ID: S5531

In February 2009, ShopSite Inc. received a notice from Authorize.net to developers who create software that integrates with the Authorize.net payment gateway service stating that in mid-to-late March 2009 they would end support for connections to their payment gateway via the SSL 2.0 protocol, and that all future API interactions with their payment gateway APIs should be via SSL 3.0/TLS 1.0 protocols.

ShopSite v6.0 and newer already uses an SSL library to connect to Authorize.net that supports the SSL 3.0/TLS 1.0 protocols, so these versions of ShopSite should continue to work with the Authorize.net payment gateway after this change to the Authorize.net system.

ShopSite v5.x and older used a binary executable provided by Authorize.net to connect to their services. It is unknown what protocols that these Authorize.net-provided binaries support, so merchants using the Authorize.net payment gateway in these older versions of ShopSite should be prepared to upgrade to ShopSite v6 or newer if their Authorize.net service through their ShopSite is interrupted by this change to the Authorize.net system.

A portion of the email from Authorize.net is as follows:

==========================================
Subject: Important System Notice

Dear Authorize.Net Developer:

During the week of March 16 - 20, 2009, Authorize.Net will be deprecating all legacy support for the SSL 2.0 protocol. Changes have recently been made to the Payment Card Industry Data Security Standard (PCI DSS) which have made the use of SSL 2.0 a PCI DSS violation.

Due to this change, it is critical that you update any applications or integrations that may be using the SSL 2.0 protocol to support the more current SSL 3.0/TLS 1.0 protocols. Failure to upgrade your applications or integrations may result in a lost ability to successfully process transactions via the Authorize.Net Payment Gateway.

Sincerely,
Authorize.Net

No related articles were found.