How To Update Your V8 Elavon/Converge/Virtual Merchant Gateway To Use Their New TLS 1.2 API URLs

How To Update Your V8 Elavon/Converge/Virtual Merchant Gateway To Use Their New TLS 1.2 API URLs

Recently Converge has announced about their upcoming SHA 2/TLS 1.2 migration occurring on October 31st, 2017.

For this purpose, any VPCart customers (v8) that are using this Elavon/Converge/Virtual Merchant gateway (Direct Post) will need to immediately update the Converge gateway location URLs to use the new ones.

Please follow these steps below :

1. Login to your VPCart administration.

2. Go to top menu and mouse over to : Advanced Settings > Software Configuration.



3. Try to enter xvmdp into the search box and click the Search button.



4. In the list of result, locate config xvmdp_DEMO_GATEWAY_LOCATION, please update the value to : https://api.demo.convergepay.com/VirtualMerchantDemo/process.do



5. In the list of result, locate config xvmdp_GATEWAY_LOCATION, please update the value to : https://api.convergepay.com/VirtualMerchant/process.do



6. Click Continue button.

After this, any payments on your VPCart site using the Converge gateway will use the new API URLs.

For Business Ready Plan customers, we can update the above for you, please submit a helpdesk ticket to us for this.

For customers that use Virtual Merchant/Converge/Elavon gateway on older versions (V7, V650, V6.00,V5) we would suggest you to upgrade to latest version V8 and download the latest Converge gateway from : https://www.vpasp.com/sales/epdownload800.asp

If older versions customers that use Converge gateway and do not yet planning for upgrade to latest VPCart version, you can submit a ticket into our helpdesk and we can quote on updating your Converge gateway files to latest API URLs.


Times Viewed:
2889
Added By:
Wilson Keneshiro
Date Created:
6/16/2017
Last Updated:
2/27/2020