TLS 1.2 and HTTP/1.1 Upgrade
PayPal is upgrading the protocols used to secure all external connections made to our systems. Transport Layer Security version 1.2 (TLS 1.2) and Hypertext Transfer Protocol version 1.1 (HTTP/1.1) will become mandatory for communication with PayPal in 2018.
You will need to verify that your environment supports TLS 1.2 and HTTP/1.1, and if necessary make appropriate updates.Merchant Security Roadmap
The information that follows is of a highly technical nature and should be reviewed by one of the following:
- Your web hosting company
- Your e-commerce software provider
- Your in-house web programmer/system administrator
In a Nutshell...
Merchants and partners use HTTPS to securely connect with PayPal’s servers. We use the Transport Layer Security (TLS) protocol to encrypt these communications. To ensure the security of our systems and adhere to industry best practices, PayPal is updating its services to require TLS 1.2 for all HTTPS connections. At this time, PayPal will also require HTTP/1.1 for all connections.
What do I need to do?
Sandbox Endpoints - Ready Now
The PayPal Sandbox endpoints have been configured with the latest security standards to which the Production endpoints will be moving. You can use these endpoints to verify that your code supports the required standards prior to the Production endpoints getting updated. These endpoints only allow TLS 1.2 and HTTP/1.1 connections:
Payflow Pilot Testing Endpoints
The Payflow testing endpoints will only allow TLS 1.2 and HTTP/1.1 connections:
Production Endpoints - Ready Now
The Production endpoints will only allow TLS 1.2 and HTTP/1.1 connections:
Verify your systems at https://tlstest.paypal.com!
Use our testing environment to verify that your servers support the latest security standards: https://tlstest.paypal.com. The testing environment will present a ‘PayPal_Connection_OK’ message if you’ve completed the server update correctly.
- On success: A successful connection to https://tlstest.paypal.com will return an HTTP 200 response with the following text in the body: " "
- On failure: One of the following errors will occur depending on what your system does not support:
- HTTPS – tlstest.paypal.com will return an HTTP 400 response with the following text in the body:
- HTTP/1.1 - tlstest.paypal.com will return an HTTP 400 response with the following text in the body:"ERROR! Connection is using HTTP/1.0 protocol. Please use HTTP/1.1"
- TLS 1.2 (SHA-256) - An SSL connection error will be thrown by your code.
For additional help, we have put together language-specific testing notes for common environments. We expect significant impact to Java environments, including Android. Other environments, including .NET, PHP, Ruby, Python and Node.js, may also be affected. For complete details, see:Language-Specific Testing Notes
Yes. As you may be aware, the Payment Card Industry Security Standards Council (PCI Council) recently extended the deadline payment processors have to make these changes from 2016 to 2018. To ensure we continue to set the bar in providing the highest security standards available while also accommodating the needs of our customers, PayPal has made the decision to move our date for requiring TLS1.2 to June 26, 2018.
The following endpoints were made available for testing against the new standards before the Sandbox endpoints were updated. Now that the Sandbox endpoints have been updated, these test endpoints should not be used and will go away on February 29, 2016.
PayPal is committed to providing the highest level of security to protect customer and transactional data, and we work closely with our merchant community to do the same. In response to feedback from several merchants, PayPal did not strictly enforce some of these vital security upgrades prior to the June 2017 deadline. However, in order to provide the most secure experience for all of our customers, PayPal must proceed with implementing these upgrades in the first half of 2018. In early 2018, we will conduct brief rounds of testing which will emulate the upgraded security experience so that merchants can understand the areas of their integration that still require work. Dates for these tests and full deployment will be published on this site at least two weeks prior to implementation.