存储信用卡，替代使用信用卡保险库
显然我很想使用信用卡保险库来存储卡片。但我们的商业模式不允许这样做。
例如：我们的客户是公司，他们在我们的软件中创建帐户。每个帐户都有自己的一组用户。他们希望通过自己的网关向用户的信用卡收费。另一方面，我们也为他们的用户提供服务。因此，我们需要通过我们自己的网关（这是不同的）向他们的卡收费。
也就是说，我们都需要在不同的网关上对同一张卡进行收费。更不用说我们客户的网关可能没有信用卡保险库。因此，这使得使用传统的信用卡金库变得不可能。
据我们所知，唯一可行的解决方案是将卡存储在我们自己的数据库中。如果可能的话我想避免这种情况。
有谁知道是否有第三方保险库可以让您存储敏感信息并将该信息提取出来？或者我所描述的问题是否有替代解决方案？
我还没有找到一个信用卡保险库，可以让您存储卡信息并检索它（读取和写入）。
我确信我不是第一个遇到这种情况的人，非常感谢任何帮助。谢谢。
Obviously I'd love to use a credit card vault to store cards. But our business model doesn't allow for this.
For example: our clients are corporations, they create accounts in our software. Each account has its own set of users. They want to charge their user's credit card through their own gateway. On the other hand, we service their users as well. So we will need to charge their cards through our own gateway (which is different).
That said, we both need to charge the same card on different gateways. Not to mention it is possible that our client's gateway won't have a credit card vault. So this makes using a traditional credit card vault impossible.
The only feasible solution, as far as we can tell, is to store the card in our own database. I'd like to avoid this if possible.
Does anyone know if there are 3rd party vaults that let you store sensitive information, and pull that information out? Or if there is an alternate solution to the problem I'm describing?
I've yet to find a credit card vault that lets you store the card information and also retrieve it (read & write).
I'm sure I'm not the first person to encounter this, any help is greatly appreciated. Thanks.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
对于任何对我们决定做什么感到好奇的人。我们决定通过信用卡保险库支持支付网关。每张卡都与每个网关一起存储。因此，如果我们在网关 #1 上对卡进行收费，它就会存储在网关 #1 的信用卡保险库中。如果我们在网关 #2 上对同一张卡进行收费，我们要求用户再次输入他们的卡并将卡存储在那里。
经过一些研究后，将卡存储在我们的服务器上根本不是一个选择，而且与之相关的风险超过了收益。 PCI 合规性是我们的客户依赖我们提供的服务。
我们考虑的另一个解决方案是选择一个主要网关（例如authorize.net）并使用共享信用卡保险库。任何想要接受银行卡的客户都需要在那里开设一个帐户。这将为我们提供一个存储信用卡的地方。
For anyone curious about what we decided to do. We decided to support payment gateways with a credit card vault. Each card is stored with each gateway. So if we charge a card on gateway #1, it gets stored in gateway #1's credit card vault. If we charge that same card on gateway #2 we require the user to enter their card again and store the card there.
After doing some research, storing cards on our server was simply not an option and the risk associated with it outweighed the benefits. PCI compliance is something our clients relied on us to provide.
The other solution we considered was picking a major gateway such as authorize.net and using a shared credit card vault. Any customer that wanted to accept cards would be required to setup an account there. This would give us a single place to store credit cards.
您可以查看 spreedly.com
它们允许向不同的网关充电。
You can check out spreedly.com
They allow charging to different Gateways.