Written by Rob Hudson
« Go back
18 May 2018  |  Product

Enforcing HTTPS on Your Website

1 minute read

Starting in July, the Chrome browser will start marking any unencrypted HTTP page as “not secure”. We run through the impact and the changes you can make if you don't use HTTPS already.

HTTPS, the secure version of HTTP, is a protocol that helps keep people secure by encrypting the communications between their browser and your server.

Until now it was still possible to rely on the less secure HTTP on your website and still be able to accept payments. The payment information is always protected because the connection between the checkout and our server is encrypted, protecting sensitive data such as credit card details.

This is however about to change. Starting in July, the Chrome browser will start marking any unencrypted HTTP page as “not secure”.

How Chrome will display HTTP pages

This won’t have an impact on the actual security: as mentioned our checkout does not use HTTP and data is encrypted no matter what.

This may however have an impact on conversion, especially if you use our Overlay Checkout or Inline Checkout. Buyers may believe that their payment details are not secure, or that the website is not the official website but a phishing clone instead.

If you haven’t done so already, we highly recommend that you switch to HTTPS before July for three reasons: it may decrease your revenue otherwise, it’s best practice anyway and it’s fairly simple and economical to use.

Even if this is only Chrome, their browser market share is large enough to have a direct impact, and it can be expected that other browsers such as Firefox, Edge and Safari follow.

It is also best practice to use HTTPS in general, to protect the data that your visitors share whilst on your website.

To get started we’d recommend checking out projects like Let’s Encrypt and SSL For Free which provide free SSL certificates. There are also numerous commercial versions of SSL certificates you can choose from.

You can learn more about the upcoming changes in Chrome on their blog.