2016-2018 Merchant Security Roadmap Microsite

As a leader in payments, PayPal continually invests in technology to protect our customers’ information. Security and safety are our top priorities, and we are in the process of implementing a series of security upgrades throughout 2016 - 2018. These upgrades ensure our security measures continue to be a model for best practice and incorporate industry standards, including those set by the Payment Card Industry (PCI) Security Standards Council.

It is critical that your systems support these new standards by the dates listed to avoid any disruption of service.

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

IP Address Update for PayPal Secure FTP Servers

If your integration is set up to systematically exchange files with PayPal’s Secure FTP Reporting / Batch Servers, please note that the IP addresses for these servers have changed. If your integration is hardcoded to the previous IP addresses, you will need to upgrade immediately to avoid any disruption of service. For information, click here.

Complete as of May 12, 2016


SSL Certificate Upgrade

PayPal is in the process of upgrading the SSL certificates used to secure our web sites and API endpoints. These new certificates will be signed using the SHA-256 algorithm and VeriSign's 2048-bit G5 Root Certificate. You will need to ensure that your environment supports the use of the SHA-256 signing algorithm and discontinue the use of SSL connections that rely on the VeriSign G2 Root Certificate. For information, click here.

Complete as of October 18, 2016


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 2017. You will need to verify that your environment supports TLS 1.2 and HTTP/1.1, and if necessary make appropriate updates. For information, click here.

Complete as of June 28, 2018


IPN Verification Postback to HTTPS

If you are using PayPal’s Instant Payment Notification (IPN) service, you will need to ensure that HTTPS is used when posting the message back to PayPal for verification. HTTP postbacks will no longer be supported. For information, click here.

Act by June, 2018*


Discontinue Use of GET Method for Classic NVP/SOAP APIs

PayPal will no longer support the use of the GET HTTP request method for our classic NVP/SOAP APIs. If you currently use any of these APIs, you will need to ensure that your API requests only use the POST HTTP request method. For information, click here.

Act by June, 2018*


Merchant API Certificate Credentials Upgrade

The API certificate credentials issued by PayPal for use with the Classic API are being upgraded to SHA-256 signed 2048-bit certificates. If you currently connect to PayPal using API certificate credentials, you will need to generate a new API certificate via your account profile and use it for all API requests. For information, click here.

Act by September, 2018* (depending on your certificate expiration date)

Security Best Practice

Future-proofing your integration is a constant challenge, and PayPal is here to help. For a review of security best practices, click here.