Recurly 与 SaaS 套件
根据一些经验丰富的开发人员的阅读和输入，我似乎只能在 Recurly 和 RailsKits.com SaaS Kit 之间做出选择。我希望从社区中的人们那里获得一些更广泛的经验，了解您可能经历过的优点和缺点。
我真的很想确保我在这里进行了同类比较。
首先，我提供的服务有两个订阅级别：每月 1 美元和 5 美元，经常性。这些费用可以按月、按年或每三年支付（较长订阅级别可享受一些折扣）。显然，我需要将交易成本保持在尽可能低的水平，但我需要维持这一点，并确保定期计费是可靠的且没有问题。
我将在 Rails 3 上构建这个。
这个包看起来很复杂，因为你通过 Recurly 获得了更强大的管理功能集，但我可以使用 SaaS 套件+（例如）https://merchant-apply.com/tesly 使其值得。
我已经回顾了 Chargify 与 Recurly 的对比，Recurly 似乎是我的特定模型的获胜者，所以这就是为什么我在这一点上消除了许多其他选项。
如果您以前遇到过这种情况，什么对您有用或者您在这方面有一些实际的投入？
From some reading and input from a couple of seasoned developers, it appears that I'm down to a choice between Recurly and RailsKits.com SaaS Kit. I'm hopeful to get some broader experiences from folks in the community here as to the pros and cons perhaps you've experienced.
I'd really like to be sure that I put together an apples-to-apples comparison here.
First, I'm offering a service that has two subscription levels of about $1 and $5 / month recurring. These may be paid in either monthly, yearly or every three years (get some discounts at the longer subscription levels). I obviously need to keep transactional costs as low as possible, but I need to maintain this and be sure that recurring billing is reliable and not problematic.
I'll be building this atop Rails 3.
The bag seems mixed as you get a more robust admin feature set it seems with Recurly, yet I may be able to save enough with a SaaS Kit + (for example) https://merchant-apply.com/tesly to make it worth it.
I have reviewed Chargify vs Recurly and Recurly seems to be the winner for my particular model and so that's why I've kinda eliminated many other options at this point.
If you've faced this before, what has worked for you or do you have some practical input in this regard?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我在 Recurly 工作，所以我会尽量不将其作为推销:)
正如我在上面的评论中指出的，PCI 合规性可能很棘手、耗时且昂贵，所以请检查每个产品并了解需要什么为了您的业务。您可以在 http://docs.recurly.com/security/pci-compliance/< 上查看有关 Recurly PCI 合规性要求的文档/a>. SaaS Kit 通过将支付信息存储在网关上，减少了 PCI 合规性的一些要素，但这意味着您无法轻松切换支付网关 - 大多数网关不允许您随身携带数据。如果您选择将 Authorize.net 的 CIM 服务与 SaaS Kit 一起使用，则每月将额外支付 20 美元的信用卡存储网关费用。
我还建议您查看每个产品的 API 文档。根据您与 Recurly 的集成复杂性，某些商家永远不需要使用 API（而是使用 Recurly 内的托管结账页面和管理虚拟控制台），但其他商家将拥有涉及使用 API 的更复杂的计费场景。每个产品的文档应该让您很好地了解它们的使用起来有多么容易。
当您继续寻找时，我很乐意回答您的任何问题！
I work at Recurly, so I'll try to not make this a sales pitch :)
As I noted in the comments above, PCI compliance can be tricky, time-consuming, and expensive, so please check each product and see what is required for your business. You can see documentation on Recurly's PCI compliance requirements at http://docs.recurly.com/security/pci-compliance/. SaaS Kit reduces some elements of PCI compliance by storing the payment information with the gateway, but this means you cannot easily switch payment gateways - most gateways will not allow you to take your data with you. If you choose to use Authorize.net's CIM service with SaaS Kit, this will be an additional $20/month gateway fee for the credit card storage.
I also recommend you take a look at the API docs of each product. Depending on your integration complexity with Recurly, some merchants never need to work with the API (instead using hosted checkout pages and the admin virtual console inside Recurly), but other merchants will have a more complex billing scenario that involves use of the API. The docs for each product should give you a good idea of how easy they will be to work with.
I'd be happy to answer any questions you have as you continue to look!