4 ms·
The exact details of PCI are pretty complex, but, roughly the answer is that any system that touches credit card numbers has to be PCI compliant. This means th
by boucher 15y ago
The exact details of PCI are pretty complex, but, roughly the answer is that any system that touches credit card numbers has to be PCI compliant.
This means that if you take credit cards on your website, you need to be PCI compliant. But the exact requirements differ depending on your setup, and what Stripe helps you do is ensure the credit card information never hits a server owned by you. This drastically reduces the scope of your compliance to a simple questionnaire.
As for being outside the US, not quite yet. We're working hard on that front though, so stay tuned.
- deleted 15y ago[deleted]
- abcd_f 15y agoI was first going to say how's that the CC #s from my web form are not hitting my server, but then looked at your Docs - and what you did is ingenious - the form is mine, but it is submitted to your site. The curl example on the front page is rather misleading. It was the only thing I actually read through on that page and I walked away with an impression that that code snippet needs to go to my server. Just the 2c worth of UX feedback :)
- boucher 15y agoThanks for the feedback. We'll work on clearer examples.
- bullcity 15y agoI'm not sure I understand the PCI implications of using the API. If I use the Create a New Charge example on the homepage in my code, aren't the credit card details going through my server? *Edit: Nevermind. After reading through the API, I learned you can use a token instead of the card details.
- deleted 15y ago[deleted]