I've seen the other thread called 'what does Upgrade to SHA-256 mean for us' but it doesnt actually have an answer to the question does it?
I use the integrated Paypal Express Checkout on V14. I'm expecting that this means I have nothing to worry about... but does anyone know? Are there any announcements from Sellerdeck regarding this?
I use the integrated Paypal Express Checkout on V14. I'm expecting that this means I have nothing to worry about... but does anyone know? Are there any announcements from Sellerdeck regarding this?
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?
Here are the steps you’ll need to take to ensure your integration is up to date and you don’t experience a disruption of service when the changes happen.
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. Here are the key areas requiring your attention.
• If the chart shows “Yes”, you may require changes to be compatible with that security upgrade.
• If you see a “No,” our data shows that you are already compliant or do not use that functionality.
There may be other changes you need to make, but please pay particular attention to the following areas:
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 about these changes. Detailed information about 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.
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?
Here are the steps you’ll need to take to ensure your integration is up to date and you don’t experience a disruption of service when the changes happen.
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. Here are the key areas requiring your attention.
• If the chart shows “Yes”, you may require changes to be compatible with that security upgrade.
• If you see a “No,” our data shows that you are already compliant or do not use that functionality.
There may be other changes you need to make, but please pay particular attention to the following areas:
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 about these changes. Detailed information about 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.
Comment