A Word About SSL

SSL or Secure Sockets Layer is an important aspect of your online store that you may not be paying enough attention to. In the past, online shopping was not as popular as it could have been due to two main reason: fear of something new and trust issues.

While the growth of eCommerce has picked up relatively fast over the last couple of years, security is still a main concern for online buyers. People have gotten used to purchasing items from the internet and credit cards offer liability limits. But it seems that websites that take extra precaution to protect its customers still get better usage than those that don’t.

It is well known that trust seals help increase conversions. Logos from Better Business Bureau, VeriSign and Trust-e are some of the common ones favored by merchants. But you don’t really have to subscribe to a specific brand of trust provider. Sometimes, a simple SSL would do the trick.

An SSL web certificate encrypts information before it is passed over the web. It increases data integrity and protects transaction details as they are transferred. This is a must-have for any website that processes credit card transactions.

Most users today are well aware of its existence. They either look for the https or the padlock icon before processing any purchases online. One thing to remember about SSL certificates as an online store owner is that you need to stay on top of it. You need to make sure it is updated, otherwise, the users will receive a warning advising them to leave the site.

SSL was originally developed by Netscape and was released to the public in February 1995. The updated version is now called the TLS or the Transport Layer Security, which basically offers the same cryptographic protocols and security measures as its predecessor.

Comments

i have been pleased after reading this blog the knowledge which has been provided via this blog is simply tremendous. i really appreciate the blogger for doing this effort.

[Sehar Sadia]

I'm trying to use the confluence word plugin with the url directive and the url i use is to an apache server that is use ssl with self signed certificate.. the problem is with the plugin not knowing how to work with unsigned or self signed certificates.