We received the note below last week from PayPal. Does the current PayPal plugin with aMember handle these issues or is development involved? We're using version 4.3.6 of aMember Pro. Thanks. 2016 merchant security upgrades We recently announced several security upgrades planned for this year, some of which may require you to make changes to your integration. You’re receiving this email because we’ve identified areas of your integration that may need to be upgraded. 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. If you see a “No,” that means our data shows that you are already compliant or do not use that functionality. We want to call out that the information provided in this email may not reflect all the changes you need to make. Please assess your integration with the emphasis being on the items we’ve identified below: Change Do I need to make a change? SSL Certificate Upgrade to SHA-256 Yes TLS 1.2 and HTTP/1.1 Upgrade Yes IPN Verification Postback to HTTPS No IP Address Update for PayPal Secure FTP Servers No Merchant API Certificate Credential Upgrade No Discontinue Use of GET Method for Classic NVP/SOAP APIs No Step 3: Get the technical details on these changes. Detailed information of each of the changes and a location to test your integration are available on our 2016 Merchant Security Roadmap Microsite. Select the hyperlinks in the chart for information about specific change events. 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. If you have any questions, visit our Help Center by clicking Help on any PayPal page. If you require further assistance, please call us at (866) 445-3186. Thank you for your support of our commitment to maintain the highest security standards for all of our global customers. *Scheduled change dates, including “Act by” dates, provided in this email and the PayPal 2016 Merchant Security Roadmap are subject to change. You’ll be notified immediately of any changes to these plans. Was this email helpful? Please click here to let us know how we're doing at keeping you informed.