这个问题讨论了不同的支付处理器和它们的成本,但我想知道如果我想接受信用卡支付,我需要做什么?

假设我需要为客户存储信用卡号码,因此依赖信用卡处理器来完成繁重工作的明显解决方案是不可用的。

PCI数据安全,这显然是存储信用卡信息的标准,有一堆一般的要求,但如何实现它们呢?

像Visa这样有自己最佳实践的供应商呢?

我需要用钥匙卡进入机器吗?那保护它不被大楼里的黑客入侵呢?甚至如果有人拿到了包含sql server数据文件的备份文件呢?

备份呢?周围还有其他数据的物理副本吗?

Tip: If you get a merchant account, you should negotiate that they charge you "interchange-plus" instead of tiered pricing. With tiered pricing, they will charge you different rates based on what type of Visa/MC is used -- ie. they charge you more for cards with big rewards attached to them. Interchange plus billing means you only pay the processor what Visa/MC charges them, plus a flat fee. (Amex and Discover charge their own rates directly to merchants, so this doesn't apply to those cards. You'll find Amex rates to be in the 3% range and Discover could be as low as 1%. Visa/MC is in the 2% range). This service is supposed to do the negotiation for you (I haven't used it, this is not an ad, and I'm not affiliated with the website, but this service is greatly needed.)

这篇博文给出了一个完整的处理信用卡的纲要(特别是在英国)。


也许我问错了问题,但我在寻找这样的建议:

使用SecurID或eToken为物理盒添加额外的密码层。 确保盒子在一个有物理锁或键码组合的房间里。


当前回答

一定要了解PCI所需的额外工作和预算。PCI可能需要巨额的外部审计费用和内部努力/支持。此外,要注意可能单方面对你征收的罚款/处罚,通常与“违法行为”的规模不成比例。

其他回答

一定要了解PCI所需的额外工作和预算。PCI可能需要巨额的外部审计费用和内部努力/支持。此外,要注意可能单方面对你征收的罚款/处罚,通常与“违法行为”的规模不成比例。

整个过程有很多。最简单的方法是使用类似paypal的服务,这样你就不会实际处理任何信用卡数据。除此之外,要获得批准在你的网站上提供信用卡服务,还有很多事情要做。你可能应该和你的银行谈谈,以及给你发商户ID的人帮助你设置这个过程。

As others have mentioned the easiest way into this area is with the use of Paypal, Google checkout or Nochex. However if you intend to to a significant amount of business you may wish to look up "upgrading" to higher level site integrations services such as WorldPay, NetBanx (UK) or Neteller (US). All of these services are reasonably easy to set up. And I know that Netbanx offers convenient integration into some of the off the shelf shopping cart solutions such as Intershop (because I wrote some of them). Beyond that you are looking at direct integration with the banking systems (and their APAX systems) but thats hard and at that point you also need to prove to the Credit card companies that you are handling the credit card numbers securely (probably not worth considering if you are not taking $100k's worth per month).

从第一个到最后一个的成本/好处是,早期的选择更容易(更快/更便宜)设置,让你为每笔交易支付相当高的手续费。后期的设置成本要高得多,但从长远来看你付出的更少。

大多数非专用解决方案的另一个优点是,您不需要保持加密的信用卡号码的安全。那是别人的问题:-)

Keep in mind that using SSL to send a card number from a browser to a server is like covering your credit card number with your thumb when you hand your card to a cashier in a restaurant: your thumb (SSL) prevents other customers in the restaurant (the Net) from seeing the card, but once the card is in the hands of the cashier (a web server) the card is no longer protected by the SSL exchange, and the cashier could be doing anything with that card. Access to a saved card number can only be stopped by the security on the web server. Ie, most card thefts on the net aren't done during transmission, they're done by breaking through poor server security and stealing databases.

为什么要为PCI遵从性而烦恼??你最多可以省下百分之一的手续费。在这种情况下,你必须确保这是你想要在开发初期和随着时间的推移跟上最新需求的时间所做的事情。

在我们的例子中,使用订阅保存网关并将其与商家帐户配对是最有意义的。订阅保存网关允许您跳过所有PCI合规性,只做适当的事务处理。

我们使用TrustCommerce作为我们的门户,并对他们的服务/定价感到满意。他们有很多语言的代码,使得集成非常容易。