© Copyright 2006-2019 Helcim Inc.
All Rights Reserved.
Overview
Elavon is sending emails to merchants using Converge, saying that there are upcoming changes to the certificates and IP addresses that may impact them.
Terminology
Converge Web Site
Old operating systems and servers will not support SHA2 or TLS1.2. For example if you're using Windows XP you would not be able to use the converge website anymore. They have to be using both a browser that's supported and an operating system that is supported. Here's a list of Browsers and operating systems that will work with the website:
Compatible Browsers
Compatible Operating Systems
NOTE: helcim.com has already switched to the new SHA2 and TLS1.2. Which means if they can browse Helcim.com on their computer, the Converge changes will work for their computer. However their ecommerce could still be impacted, see below:
Converge API and E-Commerce
If they are sending transaction using the Converge API, they will have to have their developer verify that it will work with SHA2 and TLS1.2. Their server will also have to be up-to-date. You can provide them the link down below that they can give to their developer so they can verify that it will work.
If they are using a third-party shopping cart provider (see link below, any of them where the gateway is "VirtualMerchant", e.g. Shopify), they will have to ask their shopping cart provider if their cart will support SHA2 and TLS1.2.
https://www.helcim.com/ca/virtual-terminal/compatible-shopping-carts/
Hard-Coded IP's and Firewalls
Most shopping carts and custom API codes should be sending the transactions to the Converge API directly at (https://www.myvirtualmerchant.com/VirtualMerchant/process.do). If so, there is no impact. In the event that they programmed their code to talk to the IP addresses directly (not recommended), they will either have to manually update the IP's in their software or change it to use an URL.
Original Email:
Link that is in the email: http://www.besha2ready.ca/converge