4 ms·
Sorry, but this is bad form. If you're going to accuse Stripe of not being upfront with its customers, you should at least put a disclaimer that you work for W
by reitzensteinm 14y ago
Sorry, but this is bad form.
If you're going to accuse Stripe of not being upfront with its customers, you should at least put a disclaimer that you work for WePay at the top of your post.
Being specific on the details wouldn't hurt, either.
- lsh123 14y agoI've been quoted as WePay employee on HN quite a few times including yesterday :) Regarding PCI compliance, we have a very different opinion about security and compliance. You can compare these two articles and judge by yourself: https://answers.stripe.com/questions/what-exactly-do-i-need-to-do-on-my-end-for-pci-compliance https://answers.stripe.com/questions/what-exactly-do-i-need-... https://www.wepay.com/developer/security https://www.wepay.com/developer/security
- tptacek 14y agoI don't understand the point you're trying to make with your comparison. Stripe's answer to PCI compliance is "use Stripe.js to make sure credit cards don't hit your server and then send your QSA to us". Yours is...? Stripe's answer is, as these things go, a very good answer.