You can not host your own certificate on Business Catalyst at this stage.
However, every site comes with a secure URL e.g. yoursite.worldsecuresystems.com. You can find yours listed under Admin -> Manage Domains. So, you get an SSL certificate without having to pay for it every year.
Total Tosh this one, sorry
If you do not design and build your websites properly, lots of factors cause this.
A smooth, easy to use cart process, going to the worldsecuresystems to make payment on the main form and then either off to the payment gateway or using seamless payment and then a nice thank you page, good options clear showing what happens and what the person will do next.
Good aspects of information such as security etc.
No Problem at all, we work hard on our eCommerce sites to do all that and bar the real issues with the BC eCommerce like some of the bugs etc our clients enjoy good sales using BC.
Are you refering to what I said? Because I've done A/B testing between a domain ssl and a shared ssl going to a different domain and it was a tremendous difference in conversion rates. Same exact site, only difference was the domain switch. Afterwards, we did an extensive survey and the switch in domain DOES make a buyer feel less secure and, in the buyer's eyes, seems "less professional" and "shady"... their words, not mine.
If the site has not been done in a good way, Probably will.
But we have had our clients think this, do the tests and found the opposite because the experience is a lot better. It is not ONE thing, do a lot of elements right and this does not matter.
The only issue we have had with it is breaking out of worldsecuresystems etc but we have that sorted these days and the BC enginers have put a few improvements on that and more to come too.
You can not A/B test this on a BC site anyway because you do not have an option to not go to worldsecuresystems and have https://yourdomain.com.
While with a good user experience can help I do have to say that with URLs changing will worry some users. I have had a case where I would not make a purchase because the domain changes. A good user experience is great to have and can definitely help users feel secure. However, there are still cases when a custom secure domain would be preferable.
Craftyalien is correct. We have a regular hosting solution and then we also use the Business Catalyst solution. We offer a storefront option for both. When giving a client the option and explaining the differences, they ALWAYS baulk at the thought of not having their own secure certificate on their site. This is BEFORE we even design the site according to the concept you mentioned earlier. It is the clients and site visitor's PERCEPTION that counts, not the developers. While I agree that the site is JUST as secure (if not more secure) the problem is the client and the user have an issue with it no matter how well the site is planned and developed. I believe Business Catalyst needs to truly considering opening up to allowing SSL installations for each site.
More then one of our clients have gone from Magento and other open source sollutions to our BC setup and trippling their sales.
Like I said, it has a lot to do with how you build the user experience.
You moved your client to BC, obviously with a new design & checkout process. And for all we know, perhaps there was some marketing involved too. You have zero idea how the change in domain name for secure connections is affecting the sales. No idea at all. If and when BC allow this, take the same design, same checkout process, and A/B test it with an SSL & a redirect. Then monitor how many carts you drop, and come back & post the stats & tell us that the change in domain is irrelevant.
It's been proven that when the domain name changes, trust is reduced. When trust is reduced, sales are reduced. That's a fact, and it's not rocket science.
BC really need to address this and provide a solution for customers to use an SSL on their own domain.
Though correct setup of analytics and viewing the abonrates and contacting our clients on this to help improve our framework we do actually thank you.
And the difference is not there. I have other eCommerce sites using different systems even in similar fields as the other sites.
I still strongly stand that there will be very little difference.
Do you realise that even not under https a page taking payment is still used by simply putting lock icon on the form? It is true. HTTPS or not the same form and page got the same application rate from tests before.
Your making a lot of assumptions on what I have and have not done. I have put extensive time into the eCommerce aspect of BC and research before, after and during.
I know this is an older thread and hopefully a post will "ping" those that are on it to see if this can be resurrected. I'd like to encourage ABC to offer the ability (even if this is at an additional cost to the customer) to allow us to install their own SSL Certificate on the site so that we can have https://www.sitename.com.
I understand that by using the shared SSL Cert, ABC saves the customer from having to purchase their own Certifcate, which is nice. However, from a branding perspective, if a client wants to offer a https:// expeirence for their visitors across the entire site, this is not possible without making the URL change (and breaking the brand) when the site loads.
There could be a variety of reasons why a client would want to have https://www.sitename.com showing when the page loads. They may be collecting user name and password information on their home page to allow members to log in to a secure zone and want to ensure that visitors informtion is protected. The client could also be in a sensitive industry such as helathcare, insurance or banking and offer visitors (customers) the assurance that they are on a secure site. Whatver the case, it would be nice to have this as an option, and may open up an additional revenue stream for ABC as I have several customers that would be willing to pay for this enhancement.
I do a lot of work with community banks and find the ABC system is a great, easy to use and simple (yet powerful) CMS that enables the marketing managers to keep their site updated. We have got "around" the site-wide SSL issue with some internal landing pages where customers can enter login inforation to access their online banking accounts (which is on a different system, NOT on ABC). However, if this is a requiremnet that the bank has to be "full https" on their site, we cannot go with the ABC system and end up developing on a different system. I'd prefer to have all of my clients using ABC, making it easier for me to supprot and more economical for the client.
Fingers crossed this can be revisited and something can be done that will create a win-win here for everone.
I would not hope or expect any movement on this, this year or early next. With the infrastructure work on the system this year and then the role out of delayed features to come after that... This if considered would be a long way off.
Europe, Middle East and Africa