ASPDNSF just officially killed their DNN line as of this morning (12/14/2009). I spoke with the ASPDNSF sales team and the decision was made because DNN Corp is allegedly not working towards PCI PABP certification. ASPDNSF is still offering the product on a case by case basis and they are still supporting the product for existing customers.

DNN again finds itself without a powerhouse Ecommerce provider. Quite frankly, I think I've decided to forgo DNN for sites with Ecommerce needs. It's just become too much of a hassle. The pains are now outweighing the benefits of using an CMS w/ eCommerce.

Regards,
Tom

Yes, at least on DNN.

ASPDNSF ML/64 seems to be the way to go, and build out using it as the basis.

PCI compliance is for pretty much anyone wanting to get a merchant account.  Even if you're sending customers off to a gateway site to pay (like Auth.net's server payment method), you're liable for being compliant, it's just a lot easier under those circumstances.

You can still get around it entirely using only payment methods like PayPal or Google Checkout (for now), but conversion rates with 'boomerang' payment methods are terrible compared to letting customers pay on your site.  If you don't want to lose an enormous fraction of customers who decide to buy on your site, you want to keep them there to pay, and that requires PCI compliance.