In an effort to provide additional time to our customers to ensure TLS 1.2 readiness, we have extended the timeline for accepting TLS 1.0 and TLS 1.1 communications until June 18th, 2018. After this date, we will no longer support communications made with the TLS 1.0 and TLS 1.1 protocols. Please ensure that you are prepared for this new cut-off date by referring to the How the Upgrade Impacts You section below.

The Transport Layer Security (TLS) protocol encrypts and authenticates the data that is passed between communicating applications and their end users. For example, when you enter your login credentials on a website, TLS prevents a third-party from stealing the information that is exchanged during the login process. 

The PCI (Payment Card Industry) Security Standards Council, which defines security and safety rules for the payments industry, no longer considers TLS 1.0 and TLS 1.1 to be a secure form of encryption because it is vulnerable to various types of attacks. As a result, all service providers and merchants who process or transmit credit card data must take the necessary measures to ensure that their systems and applications are upgraded to accept the TLS 1.2 protocol.

For additional information on TLS and and the risks that are present when using TLS versions 1.0 and 1.1, please refer to the PCI Security Standards Council’s Information Supplement on Migrating from SSL and Early TLS.

We will be deactivating TLS 1.0 and TLS 1.1 traffic in our UAT environments on the following dates:

• October 16th (9am-5pm EST)
• November 13th (9am EST) through November 15th (5pm EST)
• December 4th (9am EST) through December 6th (5pm EST)
• January 22nd (9am EST) through January 24th (5pm EST)
• February 12th (9am EST) through February 14th (5pm EST)
• February 26th (9am EST) through February 28th (5pm EST)

We will be permanently deactivating support for TLS 1.0 and TLS 1.1 on March 15, 2018. Please ensure you have tested your systems for TLS 1.2 readiness prior to this date.

If you run one of the following versions of Java, it is important that you take action before March 31st, 2018 to continue to communicate with CardConnect's services. 

Your OpenSSL version must be 1.0.1 or higher.

Common Server Platforms that Depend on OpenSSL 

• Linux
• Mac OS X
• Node.js
• Ruby

TLS Support varies based on your Windows Kernel

• Uses a crypto library called Microsoft Secure Channel (Schannel)

CardPointe Integrated Terminals are not impacted by the upgrade to TLS 1.2. If you are a Terminal API user, please refer to the CardPointe Integrated Terminal and API/Gateway section for additional information.

The Web Tokenizer is not impacted by the upgrade to TLS 1.2.

The iFrame Tokenizer is not impacted by the upgrade to TLS 1.2.

Refer to the table below to determine if action is required on your part based on your version of the .NET framework.

Download and Configure PANpadUp 

To download the latest version of PANpadUp, click here. The zip file contains the following files:

Refer to the table below to determine if action is required on your part based on your version of the .NET framework.

Upon updating to the new version of Desktop Tokenizer, PANpadUp, or DLL, we recommend a full regression test of the new applications in your environment in order to ensure compatibility of all implemented changes for TLS 1.2 support. This includes all required tokenization scenarios in UAT (User Acceptance Testing) and Production. 

Support of TLS 1.2 is strongly correlated to which .NET version is running within the Windows environment. Please coordinate with a network administrator to verify and confirm that the .NET version supports TLS 1.2. If running .NET 4.0, then an update to .NET 4.5 will be required.

If testing is executed with either the Desktop Tokenizer or PanPadUp while running a .NET version that does not support TLS 1.2, then the CardConnect application will prompt the user with the appropriate action before any testing can proceed.

Your browser is now ready to support the TLS 1.2 protocol.

Your browser is now ready to support the TLS 1.2 protocol.

Your browser is now ready to support the TLS 1.2 protocol.

The following libraries do not support TLS 1.2:

• SChannel XP / 2003
• SChannel Vista / 2008
• SChannel 8 / 2012
• Secure Transport OS X 10.2-10.8 / iOS 1-4

Configuring Windows SChannel Settings 

If you are using a version of Windows SChannel that is compatible with TLS 1.2 and are unsure how to configure your client-side settings to ensure TLS compliance, a 3rd-party tool exists that can be used to help you enable or disable various system-wide options. For more information, click here.