存储信用卡信息的替代方案
可能的重复：
存储信用卡详细信息
我正在努力为用户可以登录和使用的网站创建一个架构购买产品。我的老板希望结帐页面能够记住用户的信用卡信息，这样他们就不必像亚马逊那样每次都输入它。
出于多种原因，我不想将信用卡信息存储在数据库中；我拒绝这样做。但我的老板坚持要求网站记住用户的信用卡信息。
那么，如何才能实现这一点呢？显然，这种情况正在发生，除非像亚马逊这样的网站正在存储用户的信用卡信息并使其极其安全。
Possible Duplicate:
Storing credit card details
I'm working on creating an architecture for a site where users can login and buy products. My boss would like the checkout page to remember the user's credit card info so they don't have to enter it every time, like Amazon.
I don't want to store credit card info in a database for a variety of reasons; I refuse to do it. But my boss insists on the site remembering the user's credit card info.
So, how can this be accomplished? It obviously is being done, unless sites like Amazon are storing user's credit card info and making it extremely secure.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
有些公司确实存储信用卡信息。如果他们负责，他们就会遵守支付卡行业数据安全标准。这可能非常昂贵，因此公司通常与第三方合作来处理这些交易。
Some companies do indeed store credit card information. If they're responsible, they conform to the Payment Card Industry Data Security Standards. This can be quite expensive, so companies often partner with third parties to handle these transactions.
您可以使用Authorize.NET 的客户信息管理器 CIM 等服务。许多其他支付网关也提供类似的解决方案。您将付款信息存储在其中一次，然后使用付款配置文件 ID 而不是实际的付款信息来发出未来的付款请求。提供类似服务的另一家热门公司是 Braintree Payment Solutions。
You could use a service like Authorize.NET's Customer Information Manager CIM. Many other payment gateways offer similar solutions. You store the payment information with them once, then make future requests for payments using a payment profile ID instead of the actual payment information. Another popular company that offers similar services is Braintree Payment Solutions.
为什么不加密它并制作一个解密程序，一次只允许一个CC被访问呢？也许类似的东西会起作用。
我想甚至在此之前，您就必须问自己用户是否想要这种类型的功能。我可能想要保存我的 CC 信息的唯一网站是 Amazon.com、PapaJohns.com，或许还有其他一两个网站。如果你销售泳池设备、门、音响设备或类似的东西，你的老板就是个白痴。
Why not encrypt it and make a decryption program that will only allow one CC at a time to be accessed? Maybe something like that would work.
I guess even before that, you have to ask yourself whether or not the user even wants that type of functionality. The only web sites that I might want to keep my CC info stored on are Amazon.com, PapaJohns.com, and maybe one or two others. If you are selling pool equipment, doors, stereo equipment, or something like that, your boss is an idiot.