It’s simple to make sure you are ready for the TLS v1.2/SHA-2 migration. Select the scenario below that matches how you use Converge.

Converge Website - Test Your Operating System and Browser 
Converge API - Test Your Application Environment and Conducting a Test Transaction
Converge e-commerce
Fanfare Gift 

Converge Website - Validating Your Operating System and Browser

If you are using the Converge website to process your transactions, you will just need to make sure that your operating system and browser are up to date.

IMPORTANT: To continue processing with Converge, you must support SHA-2 and TLS v1.2 by January 31, 2018.

The following browsers and versions support both TLS v1.2/SHA-2 technology:

  • Google Chrome, version 38 and higher
  • Mozilla Firefox, version 27 and higher; and ESR version 31.0 and higher
  • Internet Explorer, version 11 and higher
  • Safari, version 7 and higher
  • Opera, version 12.18 and higher

It’s important to know the following operating systems support both TLS v1.2 and SHA-2:

  • Microsoft Windows 7 and higher
  • Microsoft Windows Server 2008 R2 and higher
  • OS X Mavericks (version 10.9) and higher
  • Android 5.0 and higher
  • iOS 5 and higher
  • Windows Phone 8.1, Windows 10 Mobile  

After verifying your web browser and operating system versions, please visit the new, more secure Converge link: You should see the Converge login page.

If you receive an error, please re-check your browser and operating systems.

*Tip: Don’t forget to bookmark the new URL for easy reference.

Converge API - Testing Your Application Environment/Conducting a Test Transaction

There are two components you will need to test:

Step 1: Validate your operating system and application execution environment

Step 2: Conduct a test transaction using the demo URL 

Step 1: Validating Your Operating System and Application Execution Environment

If you are using the Converge API (application programming interface), you will need to check your application environment. Please click here for more information

Step 2: Conducting a Test Transaction using the Demo URL

To test your transaction environment and code changes, Elavon has created a PCI DSS v3.1 compliant endpoint for testing that only allows connections over TLS v1.2 and compatibility with SHA-2.  To test your code, please use the following API URLs.


You will need to use the following credentials for your testing:
  • Merchant ID: 000127
  • User ID: ssltest

Please note: The terminal may not be configured exactly like the devices currently in use. The “test” should only be used to validate a simple transaction like CCSALE or CCAUTH to ensure that your environment can correctly connect to the compliant endpoint.

The following request can be used to test both SHA-2 and TLS v1.2: 

If you submit the following example Request:"<txn><ssl_merchant_id>000127</ssl_merchant_id><ssl_user_id>ssltest</ssl_user_id>

You should get the following Response upon a successful test:

Transaction Production Information/Environment:

Once you have fully tested your environment and code, Elavon has created a new PCI DSS v3.1 compliant production environment. Please use the following API URLs for the new production environment.


Your existing credentials are still valid and should be used.

Converge e-commerce
If you are using Converge for e-commerce and use an “off-the-shelf” shopping cart, you will need to contact your e-commerce solution provider to ensure compatibility with the higher security protocols.

Fanfare Gift
If you have Fanfare Gift with Converge, you will need to make sure you are on the latest version of your browser to access the following Fanfare websites: