What is changing:

As a means to improve the security of electronic payments, Payment Card Industry - Data Security Standard (PCI DSS) will be requiring all merchants, payment providers and e-commerce partners to adopt the latest TLS v1.2 encryption methodology in order to safeguard transactions and payment data.

How does this impact me?

In order to remain compliant and to keep processing through Paysafe you will have to use the TLS 1.2 security protocol to connect to the Paysafe processing endpoints.

This affects all merchants using TLS 1.0 and 1.1 version on any of our endpoints.

What is the effective date:

TLS 1.0 and 1.1 will be removed from our Beta environment on: February 28th, 2018
TLS 1.0 and 1.1 will be removed from our Production environment on: Friday March 23rd ,2018

What do I have to do? :

Either:
Update your preferred browsers to the latest version. Please see some of the recommended browsers below:

Internet Explorer 11
Google Chrome 30 or higher
Mozilla Firefox 27 or higher
Safari 8 or higher
Or:

If you are connecting to Paysafe via an API you will need to use one of the below cipher suites:

TLSv1.2:                                                 

|       TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA - strong        

|       TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA - strong        

|       TLS_RSA_WITH_AES_128_CBC_SHA - strong              

|       TLS_RSA_WITH_AES_256_CBC_SHA - strong              

|       TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA - strong        

|       TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA - strong        

|       TLS_RSA_WITH_AES_128_CBC_SHA - strong              

|       TLS_RSA_WITH_AES_256_CBC_SHA - strong                                                          

|       TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA - strong        

|       TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 - strong     

|       TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 - strong     

|       TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA - strong        

|       TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 - strong     

|       TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 - strong     

|       TLS_RSA_WITH_AES_128_CBC_SHA - strong              

|       TLS_RSA_WITH_AES_128_CBC_SHA256 - strong           

|       TLS_RSA_WITH_AES_128_GCM_SHA256 - strong           

|       TLS_RSA_WITH_AES_256_CBC_SHA - strong              

|       TLS_RSA_WITH_AES_256_CBC_SHA256 - strong           

|       TLS_RSA_WITH_AES_256_GCM_SHA384 - strong           

 

If I need to make code changes how can I test using TLS 1.2 ?

How can I be sure my code will still work when you turn off TLS1.0 and 1.1

Our test environment api.test.netbanx.com is already TLS1.2 capable (as is the live production). Therefore it is already available for testing. 

Paysafe will switch off support for TLS v1.0 and v1.1 on Friday 23rd March 2018
We will be removing TLS v1.0 and v1.1 from our Beta environment on Wednesday 28th February 2018, and replacing it with TLS v1.2, allowing you time to test the new version before the removal date
 

If you have any questions, please do not hesitate to contact Paysafe Merchant Support or your Account Manager. When emailing, make sure to have your originating ip address in the email so that we can assess your request as soon as possible.

Email: technicalsupport@paysafe.com