TLS 1.2 Helcim Legacy Virtual Terminal and Gateway Migration
TLS is the protocol used to make a secure connection when visiting “HTTPS” websites or making server-to-server connections (formerly SSL), with the most up-to-date version of TLS being 1.2.
What is happening
In order to remain PCI-DSS compliant, we’re making changes to the Helcim (Legacy) Virtual Terminal and Gateway. Older versions of TLS (1.0 and 1.1) are being deactivated on June 30, 2018. This will not impact our new merchant platform, Helcim Commerce, as it is already exclusively using TLS 1.2
What you need to do by June 30, 2018
You are receiving this email because our systems detected that your business made a connection to the legacy Helcim Virtual Terminal or Gateway using TLS1.1 or TLS1.0 in the past 6 months. This means that your ability to accept payments may be interrupted unless you make the needed changes.
If you login manually to Virtual Terminal
If you manually login to the Helcim Virtual Terminal to process your payments, no changes are needed. Modern web-browsers including Chrome, Internet Explorer, Safari and Firefox already support TLS1.2.
If you use the Hosted Payment Pages or Helcim.js
If you’re accepting transactions using the Hosted Payment Pages or Helcim.js, no changes should be needed as the TLS1.2 connection is established between your customers’ web-browser and our server. If you’re using the hosted payment pages or Helcim.js v1 in an unconventional way, please contact our support team to see if your payments will be interrupted.
If you Integrate Via Payment Gateway API
IMPORTANT! If you’re processing transactions using the legacy Helcim Payment Gateway API, you will need to make sure that your server is establishing a TLS 1.2 connection when sending POST data. This page contains code samples in PHP and C# to test your server. Failure to update your code will cause your server to no longer be able to connect to Helcim.
Linux vs. Windows Servers
By default, most Linux servers will automatically use the latest TLS standard (1.2) when making a CURL network connection. When it comes to Windows Servers however, we've seen numerous instances where Windows Servers will default to older standards, such as SSLv3 or TLS 1.0. Merchants using Windows Servers making gateway API transactions are the most likely to be impacted. Please refer to the code samples on how to force a TLS 1.2 connection using C#.
About Code Samples
The code samples on the right are made for you to download and execute on your server to see if it can successfully establish a TLS 1.2 connection. Please note that the URL used in the code is for Helcim Commerce, not the legacy Helcim Gateway. The reason for this URL is because Helcim Commerce only accepts TLS 1.2 connections, and therefore is a good API to use to see if a connection can be succesfully established. The code samples do not process any payments, instead they just connect to Helcim. Once you've been able to successfully establish a connection, you should update your current Helcim (legacy) Gateway code to force the TLS 1.2 connection, but leave the legacy URL unchanged (https://gateway.helcim.com/).
Now is a good time to switch to Helcim Commerce
Now would be a good time to consider switching your processing over to Helcim Commerce! Helcim Commerce is our new merchant platform that features mobile apps, invoicing, better recurring payments and even a hosted online store. All existing Helcim merchants can access Helcim Commerce without impacting their current pricing. We can also migrate your data from the legacy Helcim Virtual Terminal to Helcim Commerce. Please contact our support team to get migrated.
We’re here to help
Feel free to reach out if you have any questions or need any assistance. You can reach our Support Team by phone at 1-877-643-5246 or e-mail at email@example.com.
Helcim Support Team
Email: firstname.lastname@example.org Phone: 1-877-643-5246