# SSL / HTTPS for Paypal **URL:** \ **Category:** RapidWeaver Classic\ **Created:** [September 22, 2017, 11:14am UTC](https://forums.realmacsoftware.com/t/ssl-https-for-paypal/16343 "2017-09-22T11:14:25Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![manofdogz](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/manofdogz/32/26314_2.png) [@manofdogz](https://forums.realmacsoftware.com/u/manofdogz)\ **Post date:** [September 22, 2017, 11:14am UTC](https://forums.realmacsoftware.com/t/ssl-https-for-paypal/16343/1 "2017-09-22T11:14:25Z")
Does anyone have a definitive answer as to whether a simple paypal button requires https? my feeling is that as the transaction and personal data is on Paypal servers, SSL should not be necessary. However, there are conflicting views out there! I jave raised a similar question last year but not answers - maybe someone is clearer now. ---
**Author:** ![willwood](https://avatars.discourse-cdn.com/v4/letter/w/bc8723/32.png) [@willwood](https://forums.realmacsoftware.com/u/willwood)\ **Post date:** [September 22, 2017, 11:33am UTC](https://forums.realmacsoftware.com/t/ssl-https-for-paypal/16343/2 "2017-09-22T11:33:59Z")
Currently (September 2017) I don’t think you do. Because after the button is pressed, the customer is taken through to the PayPal website to enter their data and complete the transaction. SSL would be required if you are collecting data before the customer goes through to PayPal. And you would also need to be something termed ‘PCI compliant’ too. For a simple button or ‘[PayPal.me](http://PayPal.me)’ link, you do not appear to require SSL. Ultimately that may change in future, if PayPal updates their policy for ‘buy now’ buttons or web browser software determines a site matches the criteria for needing a security certificate. ---
**Author:** ![dylan](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/dylan/32/5109_2.png) [@dylan](https://forums.realmacsoftware.com/u/dylan)\ **Post date:** [September 22, 2017, 11:45am UTC](https://forums.realmacsoftware.com/t/ssl-https-for-paypal/16343/3 "2017-09-22T11:45:45Z")
Just an add on to what Will said: [https://developer.paypal.com/docs/classic/paypal-payments-standard/integration-guide/encryptedwebpayments/](https://developer.paypal.com/docs/classic/paypal-payments-standard/integration-guide/encryptedwebpayments/) ---
**Author:** ![1611mac](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/1611mac/32/5675_2.png) [@1611mac](https://forums.realmacsoftware.com/u/1611mac)\ **Post date:** [September 22, 2017, 12:29pm UTC](https://forums.realmacsoftware.com/t/ssl-https-for-paypal/16343/4 "2017-09-22T12:29:52Z")
However, you might like to konw that: - Chrome will note your site soon as not being SSL and even though checkout is secure customers may not understand that and avoid purchase. - There are two levels of SSL. Most free and low end ones are “shared.” This would be fine for your Paypal checkout. If you ever have your own cart and private info is taken on your site you need a “private” SSL account. For details just search web for “shared vs private ssl” ---
**Author:** ![manofdogz](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/manofdogz/32/26314_2.png) [@manofdogz](https://forums.realmacsoftware.com/u/manofdogz)\ **Post date:** [September 22, 2017, 12:34pm UTC](https://forums.realmacsoftware.com/t/ssl-https-for-paypal/16343/5 "2017-09-22T12:34:43Z")
> [@1611mac](#): > > …even though checkout is secure customers may not understand that and avoid purchase. I think this gets to the heart of the issue. As suspected, a Paypal button doesn’t need SSL, but perception of the buyer is clearly very important. Seeing as Google is clear in it’s intention to rank secure sites higher it may be best to run with it. Another expense for the client but that’s the way it is. ---
**Author:** ![teefers](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/teefers/32/8173_2.png) [@teefers](https://forums.realmacsoftware.com/u/teefers)\ **Post date:** [September 22, 2017, 1:03pm UTC](https://forums.realmacsoftware.com/t/ssl-https-for-paypal/16343/6 "2017-09-22T13:03:12Z")
Next month, with the new release of Chrome users will get a **not secure** warning if you collect **any** input on the page. That includes a email address, name etc. Many hosting companies are offering free certificates from let’s encrypt ([https://letsencrypt.org](https://letsencrypt.org)). You can also use a **free** CloudFlare account to add ssl(HTTPS). > [@HTTPS on a shoestring budget](http://forums.realmacsoftware.com/t/https-on-a-shoestring-budget/16211): > > If you haven’t yet converted, Chrome will be starting next month to give security warnings if you have ANY user input field on your site and are not HTTPS. They sent out an email earlier to owners (search console) of sites that will be affected. Chris Coyler CSS Tricks newsletter has an article on a quick and free way to help with a step by step guide on setting up CloudFlare. ---
**Author:** ![dylan](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/dylan/32/5109_2.png) [@dylan](https://forums.realmacsoftware.com/u/dylan)\ **Post date:** [September 22, 2017, 1:08pm UTC](https://forums.realmacsoftware.com/t/ssl-https-for-paypal/16343/7 "2017-09-22T13:08:16Z")
I’d say start putting SSL on every site you do as a standard. It ain’t much more of a task anyway.