Thu Mar 16, 2017 4:35 am
I've searched at PayPal and at E-Junkie and I cannot see what is causing this notification:
Thank you for your help.
Moderator: Bernie from RV'ing in Western USA
Thank you Jenny and Martin for these good notes. I would not know these things; but can now ask her (later today).
Hm... The one comment makes me wonder why PayPal asked her to contact the seller.
"This error message generally means that your card issuer is declining the payment, you can try 'More Funding Options' to attempt the payment with another card. "
I've found a PayPal email from Feb 17, 2017 that says much that I do not understand and wonder if this could be part of this lady's difficulty:
PayPal security upgrade progress.
As a leading payment provider, security is our number one priority and PayPal continually invests and innovates to deliver the strongest protection possible. In some instances, this means adapting to our environments and upgrading merchant integrations to the current industry standards, like those set by the Payment Card Industry (PCI) Security Standards Council. We appreciate your patience and support of protecting our customers and their payments.
To better assist customers with these security updates, we’ve created the following materials to further clarify this technical update:
2016-2017 Merchant Security Roadmap
TLS 1.2 and HTTP/1.1 Upgrade Roadmap
PayPal security guidelines and best practices
We also encourage you to speak with your web hosting company, e-commerce software provider or in-house web programmer/system administrator for further assistance in implementing these changes, if needed.
Scheduled change dates provided in this email and on the TLS 1.2 and HTTP/1.1 Upgrade Microsite are subject to change. Please monitor our TLS 1.2 and HTTP/1.1 Upgrade Microsite for the most up-to-date information.
Below are a few key points concerning security updates we will begin implementing after June 30, 2017 and we strongly recommend your systems be compatible to ensure your business is not disrupted:
The PayPal Sandbox, or testing environment, has been upgraded to allow only TLS 1.2 and HTTP/1.1 connections.
All production endpoints will be updated to accept only TLS 1.2 and HTTP/1.1 connections after June 30, 2017. Please note that if you haven’t made the necessary upgrades to your systems to become compliant, your business will be unable to accept payments with PayPal until the required changes have been made.
A verification endpoint is available, which can be found at https://tlstest.paypal.com and has the latest security standards so customers can quickly check if their systems are ready to accept transactions after June 30, 2017.
There are four remaining areas that our security upgrades will impact and we’ve identified the areas that need your attention. The chart below shows whether you’ll need to make changes, or if your business is already compliant or doesn’t use that functionality:
TLS 1.2 and HTTP/1.1 Upgrade – Complete by June 30, 2017
Update Needed: Yes
IPN Verification Postback to HTTPS – Complete by June 30, 2017
Update Needed: No
Discontinue Use of GET Method for Classic NVP/SOAP API’s – Complete by June 30, 2017
Update Needed: No
Merchant API Certificate Credentials Upgrade – Complete by January 1, 2018
Please note that this may be completed earlier based on the expiration date of your certificate
Update Needed: No
IP Address Update for PayPal Secure FTP Servers – Completed as of May 12, 2016
SSL Certificate Upgrade – Completed as of October 18, 2016
If there are any questions or concerns, please contact your account manager.
I so apologize for not understanding what I'm seeing here.
I have had another English customer who was not able to buy a download and now I have a similar note from 2CheckOut as the PayPal note above.
Is this SSL bit the same as the https in this Wish List thread?
Here is the 2CO note:
Dear Valued Merchant,
From protecting the identity of our Merchants to securing your customers' transactions, our focus here at 2Checkout is to process your payments securely and efficiently while adhering to the latest changes and updates within the payments industry.
The Payment Card Industry (PCI) Security Standards Council (SSC) has released its latest data security standard (DSS) 3.1, which mandates all businesses move away from Secure Sockets Layer (SSL) web encryption because it's no longer considered strong enough. Therefore, starting June 1, 2017, 2Checkout will no longer support SSL 3.0 and TLS 1.0. This means that all API requests, Vendor Admin sessions and standard checkout processes will need to use TLS 1.1 or TLS 1.2.
As a Merchant, please check to ensure your connectivity will not be affected – you may need to make updates to your servers, programming language and even the browser you are using immediately. Supported browsers are outlined below. For more details on this change, please check out this blog post.
The 2Checkout Sandbox environment, sandbox.2checkout.com, has already been changed to support only TLS1.1 and TLS1.2. Tests can be performed today with your shopping cart integration and API calls against that environment prior to the June 1st deadline.
Please check your system to see if any action is needed to support this update. Your applications may be unable to connect to 2Checkout services after the changes are implemented in production.
As always, you may reach us at techsuppport at 2heckout .com with any questions.
Thank you for your business,
|Similar Topics||Statistics||Last post|
Will using paypal alone make me loose customers?
by Kenesha from Sydenham Wed Mar 15, 2017 4:41 pm
| by Robert from Mc Gregor
Tue Mar 21, 2017 6:06 pm
Custome Paypal Button
by Kathy from Mintaro Sun Jun 04, 2017 7:15 am
| by Kathy from Mintaro
Tue Jun 06, 2017 1:20 pm
Paypals New Rules
by Jacki from Macleod Thu Dec 21, 2017 7:49 pm
| by Debs from SiteSell
Sat Feb 10, 2018 11:47 am
Users browsing this forum: No registered users and 1 guest