在 Rails 中实施我们的计费系统:Paypal、纯商家帐户/网关,还是 Chargify 之类的东西?
我看到了一些与 API 细节和 paypal 相关的问题。一般来说,如果我打算将 Rails 应用程序作为基于订阅的服务提供,那么 Rails 上可用的不同支付系统的优缺点是什么?
我主要关心的是:
- 避免 PCI 合规性,并且不在我们的服务器上存储任何信用卡
- 定期付款的简单 API
- 看起来很专业(例如,没有在任何地方显示某人 paypal 品牌)
Paypal 似乎有一些满足上述标准的“PRO”服务,但我很好奇直接使用像 Authorize.NET 这样的网关?
除此之外,布伦特里还提供什么?
查里菲呢?它似乎是像 Authorize.net 这样的网关之上的一层,并添加了仪表板和报告。
如果网关或支付处理器为我存储信用卡,如果我想让 10,000 名客户使用新的计费服务,会发生什么情况?他们都必须重新输入付款信息吗?是否有适当的程序,以便不同的提供商可以在它们之间移动我的客户/信用卡数据库?
I've seen a few questions related to API specifics and paypal. Generally speaking if I'm going to offer my rails app as a subscription based service, what are the pros and cons of the different payment systems available on rails?
My main concerns are:
- Avoiding PCI compliance, and not storing any credit cards on our servers
- Easy API with recurring payments
- Looking professional (not showing someone paypal branding anywhere as an example)
Paypal seems to have some "PRO" services that meet the above criteria, but I was curious about using a gateway like Authorize.NET directly?
What does Braintree offer above and beyond these?
What about Charify? It seems to be a layer on-top of gateways like Authorize.net with added dashboards and reports.
If the gateway or payment processor is storing credit cards for me, what happens if I want to take my 10,000 customers with me to a new billing service? Do they all have to enter payment info all over again? Is there a procedure in place so that different providers can move my customer / Credit Card database between them?
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(2)
我们使用了 Chargify,它的优点有以下几个:
。因此,我强烈建议将 Chargify 与 Authorize.net 结合使用。
缺点:
We've used Chargify and it's great for a couple of reasons:
So I highly recommend using Chargify with Authorize.net
Cons:
我推荐这篇文章澄清其中许多问题。
I recommend this write-up which will clear up many of these questions.