Scam or Not Paypal

[MaggieMay]

I deleted my Name and Business Name. Not sure about this e-mail.

Any Help that anyone can offer, please and Thanks

Hugs Maggie

New payment security standards coming into effect Security and safety are our top priorities. We’re in the process of implementing a series of security upgrades this year. These upgrades ensure our security measures continue to be a model for best practice and incorporate industry standards. Most importantly, the upgrades will allow us to continue to provide the highest level of security available for our customers. Here’s the schedule for our security upgrades. If, you see a “YES” next to a security change, our records indicate you may be impacted if appropriate changes aren’t made to your systems. In those cases, we highly recommend that your integration is upgraded to accept these new security measures as soon as possible.      Change （click hyperlink for more details） Change required? Dates Complexity IP Address Update for PayPal Secure FTP Servers No May 12 2016 Medium SSL Certificate Upgrade to SHA-256 PayPal is unable to determine if your systems are SHA-256 compatible. Please go to 2016-2017 Merchant Security Roadmap Microsite to verify your status. June 17 2016 June to August - Testing September 30 2016 - Full cutover High TLS 1.2 AND HTTP/1.1 Upgrade Yes June 30 2017 High IPN Verification Postback to HTTPS No June 30 2017 Low Discontinue Use of GET Method of Classic NVP/SOAP No June 30 2017 Low Merchant API Certificate Credential Upgrade No Act before your current certificate expires. Certificates are due to expire after January 2018. We’ll work with you to generate a new certificate before January 2018 Medium Scheduled change dates provided in this email and the PayPal 2016 - 2017 Merchant Security Roadmap are subject to change. You’ll be notified of any changes to these plans. Critical SHA-256 testing to occur from June to August To ensure compliance with industry standards, we strongly encourage you to have your systems SHA-256 compatible by June 17 2016. After this date, we’ll be conducting critical testing throughout August to prepare for the full cutover to SHA-256 on September 30 2016. If you haven’t upgraded to SHA-256 by June 17 2016, you will experience service interruptions during testing. If you’re not certain whether your systems are SHA-256 compatible, please go to the 2016-2017 Merchant Security Roadmap Microsite to verify your status. We also encourage you to contact your web hosting company, e-commerce software provider, in-house web programmer or system administrator for assistance. We’ll send you a separate email in the next couple of weeks with more details on our testing procedures.    For more information on all our security upgrades, please refer to the following FAQs or our 2016-2017 Merchant Security Roadmap Microsite. How do I make these changes? The details on the required changes and how to implement them can be found on our 2016-2017 Merchant Security Roadmap Microsite. We encourage you to contact your web hosting company, e-commerce software provider, in-house web programmer or system administrator for assistance with these changes, if needed. What will happen if I don’t make the changes by the due date? If you have not made the necessary changes by the deadlines, you won't be able to accept payments with PayPal until you do so. The exception is change #1: IP Address Update for PayPal Secure FTP Servers, which will limit access to reports from PayPal’s SFTP server if the change is not made. We encourage you to contact your web hosting company, e-commerce software provider, in-house web programmer or system administrator for assistance with these changes. If not supported, please contact us by clicking the Help & Contact link at the bottom of any PayPal page or by visiting theTechnical Support Portal to submit a ticket. Select “Security Changes (TLS/Certificate)” within theProduct drop-down.  As a leading payment provider, we’re committed to continually investing and innovating to deliver to customers the strongest protection possible. Thank you for your support of our commitment to maintain the highest security standards for all our global customers.   Was this email helpful? Please click here to let us know how we're doing at keeping you informed. Help Contact Fees Security   Features   Shop Please do not reply to this email. We're unable to respond to inquiries sent to this address. For immediate answers to your questions, visit our Help Centre by clicking Help located on any PayPal page or email. PayPal is committed to your privacy, learn more about our privacy policy. Copyright © 2016 PayPal Inc., 500 King St. W, Toronto, ON M5V 1L9. All rights reserved.

Edited June 10, 2016 by MaggieMay
for to write a few things before posting

[Moonstar]

I would call Paypal directly + ask them about it. you never know nowadays  

[MaggieMay]

I sent am e-mail to spoof@paypal.com

 

[kandlekrazy]

I never do anything that involves $ from an email link.  Not even from my bank.  If I get an email, most likely there is a message on the site in my inbox.

Go directly to Paypal whenever you get a message and you will have the same message in your inbox.  If you don't have the message, it's someone else

trying to get your info.  Paypal rarely emails but the spoof@paypal.com will let you know if it was them.

[Candybee]

What kandlekrazy said. Go to your Paypal account and see if you have the same email in your message box. If its there, you will know that Paypal sent it.

 

If in doubt, call them and ask.

 

Edited June 10, 2016 by Candybee

[TallTayl]

Sometimes the sender's address is a dead giveaway. Good of you to forward to phishing.

[Midas251]

Yea i would follow KandleKrazy's advice. Don't risk it, do not click any links, Go to Paypal and contact them through their phone number or there website.

Edited June 10, 2016 by Midas251

[MaggieMay]

Thanks everyone for your advice. Its soooo appreciated.

I did follow the advice to check my paypal notifications and there is nothing, notta!!!!