News for hackers. Stuff that matters.
Re:Ask HN: Liability due to lack of SSL by SyneRyder on Saturday August 08, 2015 @12:59PM (#10027878)
I'd say an even bigger question is, why is he even doing it that way at all, and not using a service like Stripe, Braintree, Shopify or similar? They've invested in polished checkout experiences, it's what they do, and it moves the burden of PCI compliance, PII storage, SSL etc to the service. When Stripe exists, why would you even go down the merchant account route anymore?

Scaring them with the bad stuff might not be effective, people don't react well to being told they're doing everything wrong. Perhaps showing them an easier solution that reduces their admin hassles & could potentially increase their sales is a better way to approach this.

Re:Ask HN: Liability due to lack of SSL by jtdowney on Saturday August 08, 2015 @04:17PM (#10028544)
Both Stripe and Braintree require you to use SSL (really TLS) on your checkout pages. They also both require you maintain PCI compliance (although you likely qualify for a reduce set of requirements).
Re:Ask HN: Liability due to lack of SSL by jordsmi on Sunday August 09, 2015 @02:46PM (#10031045)
They 'require' it, but it is still possible to use the service without SSL. At least it was possible on stripe a few months ago. I'm not sure if they end up cutting you off after they notice the non ssl traffic, but I setup some test apps that worked fine without ssl.