|
|
| | Ask HN: Can someone explain PCI compliance to me in a nutshell? | |
6 points by tapan_pandita on Feb 6, 2013 | hide | past | favorite | 3 comments
|
| | What I basically need to do is pass on credit card info (credit card no., cvv, expiry) to a third party that will charge the card. Let's assume I cannot integrate stripe or another such service. I would also want to be able to store the card info for recurring payments. What is the PCI compliant way of doing this? I know that for PCI compliance, I am not allowed to save the cvv or other such data (even if encrypted), but there might be a gap in my understanding. Any PCI compliance experts here who can clarify on this?<p>tl;dr: Need to save credit card info (credit card number, expiry date, cvv) for recurring payments, what is the PCI compliant way to do it? |
|
Consider applying for YC's Spring batch! Applications are open till Feb 11.
Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact
|
Then, even after that, you have regular reports to do, etc., etc. Being, and staying, PCI compliant can be a huge time sink.
All of that said, would a service like Spreedly[2] work for you? I believe they can handle recurring payments / subscriptions, and they take care of making sure everything is PCI compliant, so you don't have to do all of that work. Unless billing and credit card processing is a core competency for your company, I can't help but think you'd be better off outsourcing that bit.
[1]: https://www.pcisecuritystandards.org/security_standards/gett...
[2]: http://spreedly.com/