So, I'm going to try multiple SSL sites based on host name, each in their own IIS web pointing to same mojo install directory. Each site will have a cheap $30 SSL cert which appears required. For the sites that will truly need SSL I'll use better certs.

My question is regarding the PayPal/Google Checkout/AuthorizeNet integration. Since it appears the keys and settings for these processing providers appear in the web.config does that mean that if I have 10 sites running on a single install they each CAN'T have their own AuthorizeNet settings for example? Can I have multiple AuthorizeNet accounts in a single mojo install, one for each site? Or ideally, a unique account for each module instance. For example, some clients may have two stores, each going to a different AuthorizeNet account. Is this possible?

I looked around but have a feeling this may not work the way I'm hoping. An alternative can and may be custom modules where I can set the variables myself, per application - but let me know. Thanks again!

Hi Eric,

Yes, in that scenario where each site has its own IIS web site, host name and ssl cert, in theory I see no problems, though I have not tried this scenario. 

If you notice in the ecommerce configuration doc, all the params have a Site1- prefix, so those settings only apply to the site with SiteID = 1. You can add separate settings for each site based on the SiteID in the mp_Sites table

So basically copy and paste the ecommerce config setting for each site and change the site prefix.

Hope it helps,

Joe