如果您使用Google Checkout，是否还需要在Rails中使用ActiveMerchant/Spree/某些支付网关？
如果您使用 Google Checkout，是否仍需要使用 ActiveMerchant/Spree/某些支付网关，或者 Google 是否像 ActiveMerchant/Spree 一样充当网关？
另外，使用 Google Checkout 是否有任何缺点可以通过使用 ActiveMerchant 来解决？
另外，除了 Google Checkout 之外，还提供 PayPal 是个好主意吗？
If you use Google Checkout, do you still need to use ActiveMerchant/Spree/some payment gateway or does Google act as the gateway the same way that ActiveMerchant/Spree would?
Also, are there any disadvantages to using Google Checkout that might be solved by using ActiveMerchant?
Also, is it a good idea to offer PayPal in addition to Google Checkout?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
Google Checkout 和 PayPal 都与“传统”支付处理解决方案不同，因为它们不需要几乎相同数量的设置工作即可启动。 它们结合了信用卡处理和商家帐户传统上独立的角色。 其优点包括更简单的实施和更便宜的费率。 缺点是他们往往控制更多的体验 - 例如，Google Checkout 和 PayPal 都有自己的登录系统，您的用户可能会将其视为支付工作流程的一部分。 如果您对 Google Checkout 或 PayPal 不满意（例如，两者都有关于扣留向商家付款的恐怖故事），那么您通常会遇到比在付款处理者和商家帐户托管人之间分配角色更困难的情况。
如果您想采用完全定制的解决方案，我建议您使用 ActiveMerchant。 它主要为包括 PayPal 在内的各种信用卡处理公司提供统一、易于使用的 API。
最后，最重要的因素是您的客户是否满意。 许多非美国销售将严重偏向 PayPal 或使用手机支付； 早期采用技术的人群更有可能拥有使用 Google Checkout 所需的 Google 帐户，而大多数其他主要位于美国的在线商店最好接受信用卡。
Google Checkout and PayPal both differ from "traditional" payment processing solutions in that they don't require nearly the same amount of setup work to get going. They combine the traditionally separate roles of credit card processing and merchant accounts. The upsides include a simpler implementation and cheaper rates. The downside is that they tend to control much more of the experience - Google Checkout and PayPal both have their own login systems, for example, which your users would likely see as part of the payment workflow. If you were unhappy with Google Checkout or PayPal (both have horror stories about withholding payments to merchants, for example) you'd generally have a harder time than if the roles were split between the payment processor and the merchant account host.
If you want to go with a fully customized solution, I'd recommend ActiveMerchant. It primarily provides a unified, easy-to-use API for various credit card processing companies, including PayPal.
In the end, the most important factor is what your customers are comfortable with. A lot of non-US based sales would skew heavily towards PayPal or use cell phone payments; an early adopter technology crowd would be more likely to have the Google accounts necessary to use Google checkout, whereas most other predominantly US-based online shops would be best served accepting credit cards.
Spree 尚不支持 Google Checkout，但有可能添加对其的支持。 它实际上是一个实施起来相当复杂的标准，但 Spree 已经添加了对 Paypal 等效项（网站支付标准）的支持。一旦核心团队中有人需要为付费客户提供支持，很可能会向 Spree 添加支持。
应该注意的是，ActiveMerchant 为您提供了一些有关 Paypal 等服务的帮助，但它不会提供一切。 Spree 使用 ActiveMerchant 进行 IPN 处理，但这种支持归结为一些方便的包装器。 大多数必要的逻辑仍然需要在 ActiveMerchant 之外实现。 因此，如果您的电子商务解决方案已经为您打算使用的支付服务提供支持，那么它会很有帮助。
Spree does not yet support Google Checkout but it would be possible to add support for it. Its actually a fairly complicated standard to implement but Spree has already added support for the Paypal equivalent (Website Payments Standard.) Support will likely be added to Spree once someone on the core team needs it for a paying client.
It should be noted that ActiveMerchant gives you some help with services such as Paypal but it will not provide everything. Spree uses ActiveMerchant for its IPN handling but this support boils down to some convenient wrappers. Most of the necessary logic still needs to be implemented outside of ActiveMerchant. So its helpful if your e-commerce solution already provides support for the payments service you intend to use.
Spree 现在使用以下扩展处理 Google Checkout：http://github.com/railsdog/spree-谷歌结帐
Spree now handles Google Checkout with the following extension: http://github.com/railsdog/spree-google-checkout