Hi Greg,

Thank you for the follow up.  So you're indicating that with Authorize.net, the credit card details are collected on the checkout page.  They are then sent on using secure methods.  However - from the shopper entering them, through to them being received at the DNN server they are encrypted right, unless the checkout page is using https?   Is this a major security risk?  The banks here wouldn't allow me to run a site like that.  If a page is collecting credit card details (like the check out page) then it has to be operating under https.

So my original question was, is there any way to force DNN to use https for the checkout page?

I'll be dealing with this one over the next couple weeks... I'm hoping to use a modified version of the Authorize.net Provider with a custom auction module. I'm thinking that any page that collects and/or sends Credit Card or other sensitive should check a setting to see if SSL is enabled/required and if so redirect to the same page but using https.

Curious what change you have planned? I'd definitely be happy to work with someone on this and donate code to the project.

---

David O'Leary
Efficion Consulting