Posted: March 16, 2016 at 10:35 am
Hi, ——————————————————– What you’re about to read is very technical in nature – we understand that. Please contact the parties responsible for your PayPal integration, or your third party vendor (for example, shopping cart provider, and so on) to review this email. They’re best positioned to help you make the changes outlined in this email and in the 2016 Merchant Security Roadmap Microsite. What do I need to do to as a merchant? We’ve outlined the steps to take to ensure your integration is up to date. We’re letting you know about these changes now because we don’t want you to experience a disruption of service when they go into effect. Step 1: Consult with someone who understands your integration. We encourage you to consult with the parties that set up your integration, which could be a consultant or third party shopping cart. You may also need to find someone who can assist with making your integration changes. Step 2: Understand how these changes affect your integration. Based on our records, we’ve identified areas that require your attention. It’s not a complete list, but does provide changes we feel you need to make to be ready for the security upgrades. If the chart shows “Yes”, it means our records indicate that you may require changes to be compatible with that security upgrade. Change Do I need to make a change? Step 4: Make the appropriate changes by each “Act by” date*. It’s important to have your changes in place by the “Act by” date for each change event. Step 5: Future-proof your integration. We recommend that you go through the “Best Practices section on our 2016 Merchant Security Roadmap Microsite. Why is PayPal making these changes? Protecting customer information is PayPal’s top priority. We support industry standards, such as crypto-industry’s mandate to upgrade SSL certificates to SHA-256, and Payment Card Industry (PCI) Council’s TLS 1.2 mandate. We also surpass those standards by investing and building some of the finest protection available. By addressing these changes this year, we believe it helps future-proof your integration and reduce the need to invest in changing your integration in the near future. |
|
Hi, We updated Event Espresso some time ago to be use HTTP 1.1. You may want to follow up with your web host to ensure that they are using the new certificates: https://eventespresso.com/topic/paypal-ipn-service-upgrade-anything-i-have-to-do/#post-172408 — |
|
Hi there, No change needed to Event Espresso, however you will need to verify that your server has been upgraded to PayPal’s specifications. You can share the information from PayPal with your hosting provider and ask them if they’ve already made the upgrades in PayPal’s list. Further to the above, PayPal Sandbox is already requiring the upgrades (PayPal live will roll out the upgrades in June). So if you have a site on your server where you can test Event Espresso using a PayPal Sandbox account, you can verify whether your server has the necessary upgrades. When you test PayPal sandbox on a server that does not have the necessary upgrades, it will log an error that says:
|
|
The support post ‘PayPal 2016 merchant security upgrades’ is closed to new replies.
Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.