在 Rails 中使用 Braintree，我可以在本地存储哪些内容，同时仍符合 PCI 标准？
如果我依靠 Braintree 进行支付处理，我可以存储哪些信用卡信息，同时仍符合 PCI 合规性？
我问这个问题的原因是，作为一个简单的优化，如果客户已经使用信用卡从我的商店购买了商品，我可以向他们显示信用卡的最后 4 位数字以及卡类型，而无需进行对 BrainTree 的 API 调用。如果他们想换卡或购物，我就必须打电话，但对于那一页，我不会。
问题是，我是否可以存储：
- 信用卡的最后 4 位数字
- 、卡类型
- 以及持卡人姓名
，或者哪里有我可以查看的 PCI 合规性“注意事项”列表？
What credit card information am I allowed to store while still being PCI compliant if I am relying on braintree for payment processing?
The reason I am asking is because, as a simple optimization, if a customer has already bought something from my store with a credit card, I can show them the last 4 digits of their credit card, and the card type, without having to make an API call to BrainTree. I'd have to make the call if they wanted to change the card or make a purchase, but for that one page, I wouldn't.
Question is, am I allowed to store:
- the last 4 digits of the credit card
- and the card type
- and possible the cardholder name
Or where is there a list of PCI compliance "do's and don'ts" I can check out?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
是的，存放这些东西很好。
查看PCI 快速参考指南，简要概述您应该做什么和不应该做什么做。
Yeah, it's fine to store those things.
Check out the PCI Quick Reference Guide for a brief overview of what you should and shouldn't do.
正如已经说过的，可以存储该数据。
关于“注意事项”，值得查看开放 Web 应用程序安全项目 (owasp.org)。特别是，请查看他们的 OWASP 指南（可在此处 http://prdownloads.sourceforge 获取。 net/owasp/OWASPGuide2.0.1.pdf?download）了解如何开发安全的 Web 应用程序。它们从第 53 页开始涵盖 PCI 合规性和最佳实践。
As has already been said, it's ok to store that data.
Regarding "dos and don'ts", it would be worth it to check out the Open Web Application Security Project (owasp.org). In particular, look at their OWASP guide (available here http://prdownloads.sourceforge.net/owasp/OWASPGuide2.0.1.pdf?download) on how to develop secure web applications. They cover PCI compliance and best practices starting on page 53.
我会使用诸如 attr_encrypted gem 之类的东西来保护数据库中的数据（请参阅 https://github.com/shuber/attr_encrypted ）。
I would use something like attr_encrypted gem to protect that data in the database (see https://github.com/shuber/attr_encrypted).