If you don't want to use an external processor, this is hard. The security issues are huge, and I can't seriously imagine a bank allowing you to do it. I would strongly recommend you use Paypal, Google Checkout or WorldPay, or whatever payment processing system is provided/recommended by your bank.
There's absolutely no reason you need to deal with storing credit card data on your servers if all you want to do is accept credit cards. Lots of folks that have never implemented a non Paypal/Google Checkout system will try to scare you with talk of it being a terribly huge task, but your code just needs to take an encrypted CC from the client and pass it to the gateway. It never needs to live in your DB and your risk is minimized because of it.
I'd say the line between using Paypal buttons and using a gateway is simply a choice of if you want the customer to check out on your site or on someone else's. That's it. It's not that much more risk, since all you need to do is buy an SSL cert and use a reputable cart system like Magento, Ubercart for Drupal, etc. There will always be effort involved.
I'd rummage around on Visa for the answer, digging up a reliable third party company; I would not by any means write my own CC authorization code; to my mind, that sounds like a great big invite to hackers.
Paypay is reasonably reliable, I know that.
Check out Amazon, Ebay, Yahoo, etc., for their solutions. They might license out their shopping cart software(for a fee, of course).
If your company is sufficiently established that it can get an internet merchant account from a bank, do so if your transaction volumes are greater than "very, very small". If you're turning over more than £1000 per month (or say $1000/month USD or something), then get a merchant account.
If you're NOT turning over that much, then first figure out how to get your turnover that high, because otherwise you're not going to be in business for long.
Internet merchant accounts not charge much less commission than the aforementioned "Hold on to the cash" PSPs, but they also give you the money sooner and are generally far more reasonable to work with.
There are many gateway providers which can work with the banks and the banks themselves typically offer their own. You can choose whatever combination best suits you from a technical perspective.
Disclaimer: This information is based on my limited experience integrating payment providers IN THE UK. It may not apply to other countries (or even here!)
如果我在美国，我会使用 google checkout。 它非常便宜，是我（和许多客户）信任的品牌。
除此之外，还有很多可能性。 不过，远离 Digital River 拥有的任何东西。 看起来FastSpring比较好，但是贵。
IF I were in the US, I'd use google checkout. It's quite cheap and it's a brand I (and many customers) trust.
Other than that, there's a bunch of possibilities. Stay away from anything owned by Digital River, though. Seems that FastSpring is relatively good, but expensive.
A merchant account can be had from most banks; of course, in order to get one, you need to be a registered business, and satisfy several other criteria which differ depending on the bank.
Secondly, you need to choose a payment processor. I would recommend Authorize.net if your customers are US-based. I've worked with them before, and had good success.
Not all banks, and not all payment processors work together, so double check if they will work well together.
Once you have them set up, your payment processor will give you an API allowing you to integrate with their payment services. If you use common ecommerce software, their most likely will be plugins or code existing to integrate with the major payment processors.
Make sure your website is secure - you will be responsible for any leaked customer data.
There's a lot of complexity in accepting credit cards, which is why PayPal and Google Checkout are so popular -- they take care of much of the complexity for you.
Another company that offers even more than PayPal is Kagi. I strongly recommend you watch their short promotional video, because it outlines all the components needed to process credit cards the way you want to -- payment gateways, payment processors, merchant accounts, etc.; I think it might convince you to go with a different approach.
发布评论
评论（9）
那里有很多解决方案。 首先是：Authorize.net 和 支付技术
There are a lot of solutions out there. A couple to start with: Authorize.net and Payment Tech
如果您不想使用外部处理器，这很难。 安全问题是巨大的，我无法认真想象银行会允许你这样做。 我强烈建议您使用 Paypal、Google Checkout 或 WorldPay，或您的银行提供/推荐的任何付款处理系统。
If you don't want to use an external processor, this is hard. The security issues are huge, and I can't seriously imagine a bank allowing you to do it. I would strongly recommend you use Paypal, Google Checkout or WorldPay, or whatever payment processing system is provided/recommended by your bank.
如果您只想接受信用卡，那么您绝对没有理由需要在服务器上存储信用卡数据。 许多从未实现过非 Paypal/Google Checkout 系统的人会试图吓唬您，说这是一项非常艰巨的任务，但您的代码只需要从客户端获取加密的 CC 并将其传递到网关即可。 它永远不需要存在于您的数据库中，并且因此您的风险被最小化。
我想说的是，使用 Paypal 按钮和使用网关之间的界限只是您希望客户在您的网站还是其他人的网站上结账的选择。 就是这样。 这并没有那么大的风险，因为您所需要做的就是购买 SSL 证书并使用信誉良好的购物车系统，例如 Magento、Ubercart for Drupal 等。总会有一些努力。
There's absolutely no reason you need to deal with storing credit card data on your servers if all you want to do is accept credit cards. Lots of folks that have never implemented a non Paypal/Google Checkout system will try to scare you with talk of it being a terribly huge task, but your code just needs to take an encrypted CC from the client and pass it to the gateway. It never needs to live in your DB and your risk is minimized because of it.
I'd say the line between using Paypal buttons and using a gateway is simply a choice of if you want the customer to check out on your site or on someone else's. That's it. It's not that much more risk, since all you need to do is buy an SSL cert and use a reputable cart system like Magento, Ubercart for Drupal, etc. There will always be effort involved.
我会在 Visa 上翻遍寻找答案，找到一家可靠的第三方公司； 我绝对不会编写自己的 CC 授权代码； 在我看来，这听起来像是对黑客的一个巨大邀请。
Paypay 相当可靠，我知道这一点。
查看 Amazon、Ebay、Yahoo 等的解决方案。 他们可能会授权他们的购物车软件（当然是收费的）。
I'd rummage around on Visa for the answer, digging up a reliable third party company; I would not by any means write my own CC authorization code; to my mind, that sounds like a great big invite to hackers.
Paypay is reasonably reliable, I know that.
Check out Amazon, Ebay, Yahoo, etc., for their solutions. They might license out their shopping cart software(for a fee, of course).
完全取决于你是谁。
如果您的公司已经足够成熟，可以从银行获得互联网商家帐户，并且您的交易量大于“非常非常小”，则可以这样做。 如果您每月的营业额超过 1000 英镑（或者说每月 1000 美元或其他），那么就获得一个商家帐户。
如果你的营业额没有那么多，那么首先要弄清楚如何让你的营业额达到那么高，因为否则你的生意就不会长久。
互联网商家帐户收取的佣金并不比前面提到的“保留现金”PSP 少得多，但它们也会更快地给您钱，而且通常合作起来更合理。
有许多网关提供商可以与银行合作，而银行本身通常也提供自己的网关。 您可以从技术角度选择最适合您的组合。
免责声明：此信息基于我在英国整合支付提供商的有限经验。 它可能不适用于其他国家（甚至在这里！）
Depends entirely on who you are.
If your company is sufficiently established that it can get an internet merchant account from a bank, do so if your transaction volumes are greater than "very, very small". If you're turning over more than £1000 per month (or say $1000/month USD or something), then get a merchant account.
If you're NOT turning over that much, then first figure out how to get your turnover that high, because otherwise you're not going to be in business for long.
Internet merchant accounts not charge much less commission than the aforementioned "Hold on to the cash" PSPs, but they also give you the money sooner and are generally far more reasonable to work with.
There are many gateway providers which can work with the banks and the banks themselves typically offer their own. You can choose whatever combination best suits you from a technical perspective.
Disclaimer: This information is based on my limited experience integrating payment providers IN THE UK. It may not apply to other countries (or even here!)
如果我在美国，我会使用 google checkout。 它非常便宜，是我（和许多客户）信任的品牌。
除此之外，还有很多可能性。 不过，远离 Digital River 拥有的任何东西。 看起来FastSpring比较好，但是贵。
IF I were in the US, I'd use google checkout. It's quite cheap and it's a brand I (and many customers) trust.
Other than that, there's a bunch of possibilities. Stay away from anything owned by Digital River, though. Seems that FastSpring is relatively good, but expensive.
我已经实施过几次 Authorize.NET。 效果很好，我相信他们的价格也很合理。
您确实需要管理自己的 SSL 证书等，并遵守 PCI 标准，但这只是为了摆脱 Paypal 的罪恶而付出的很小的代价。
I've implemented Authorize.NET a couple times. It works very well, and I believe their rates are reasonable.
You do need to manage your own SSL certificate etc, and comply with PCI standards, but its a small price to pay to get away from the evils of paypal.
如果您的现金流量偏小（
大多数银行都可以开设商家账户； 当然，为了获得这一资格，您需要成为一家注册企业，并满足其他几项标准，这些标准因银行而异。
其次，您需要选择支付处理器。 如果您的客户位于美国，我会推荐 Authorize.net。 我以前曾与他们合作过，并取得了很好的成功。
并非所有银行和支付处理商都能协同工作，因此请仔细检查它们是否能够很好地协同工作。
设置完成后，您的支付处理器将为您提供一个 API，允许您与其支付服务集成。 如果您使用常见的电子商务软件，它们很可能是与主要支付处理器集成的现有插件或代码。
确保您的网站安全 - 您将对任何泄露的客户数据负责。
祝你好运！
If your cash flow is on the small side (
A merchant account can be had from most banks; of course, in order to get one, you need to be a registered business, and satisfy several other criteria which differ depending on the bank.
Secondly, you need to choose a payment processor. I would recommend Authorize.net if your customers are US-based. I've worked with them before, and had good success.
Not all banks, and not all payment processors work together, so double check if they will work well together.
Once you have them set up, your payment processor will give you an API allowing you to integrate with their payment services. If you use common ecommerce software, their most likely will be plugins or code existing to integrate with the major payment processors.
Make sure your website is secure - you will be responsible for any leaked customer data.
Good Luck!
接受信用卡的过程非常复杂，这就是 PayPal 和 Google Checkout 如此受欢迎的原因——它们会为您解决大部分复杂问题。
另一家提供比 PayPal 更多服务的公司是 Kagi。 我强烈建议您观看他们的简短的宣传视频，因为它概述了处理所需的所有组件以您想要的方式使用信用卡——支付网关、支付处理器、商家帐户等； 我认为这可能会说服您采用不同的方法。
There's a lot of complexity in accepting credit cards, which is why PayPal and Google Checkout are so popular -- they take care of much of the complexity for you.
Another company that offers even more than PayPal is Kagi. I strongly recommend you watch their short promotional video, because it outlines all the components needed to process credit cards the way you want to -- payment gateways, payment processors, merchant accounts, etc.; I think it might convince you to go with a different approach.