Re Against SaaS Kit

Question

From some reading and input from several experienced developers, it looks like I got to the choice between Recurly and the RailsKits.com SaaS Kit. I hope to gain more experience from the people in the community here, as about the pros and cons that you may have experienced.

I really would like to be sure that I have put together a comparison of apples and apples.

Firstly, I offer a service that has two subscription levels of about $ 1 and $ 5 per month. They can be paid monthly, annually or every three years (receive discounts on longer subscription levels). I obviously need to keep transaction costs as low as possible, but I need to maintain this and be sure that recurring billing is reliable and not problematic.

I will build this on top of Rails 3.

The bag seems to be mixed, since you get a more robust set of admin functions, it seems with Recurly, but I can save enough with the SaaS Kit + (for example) https://merchant-apply.com/tesly to make it worthy.

I reviewed Chargig vs Recurly and Recurly seems to be the winner for my particular model and therefore for some reason eliminated many other options at this stage.

If you have come across this before, what worked for you or do you have a practical contribution in this regard?

Answer 1

I work in Recurly, so I will try not to make this an advertising field :)

As I noted in the comments above, PCI compliance can be complicated, time-consuming, and expensive, so please check each product and see what is required for your business. You can read the REUTERI PCI compliance documentation at http://docs.recurly.com/security/pci-compliance/ . The SaaS Kit reduces some PCI compliance elements by storing payment information with a gateway, but that means you cannot easily switch payment gateways - most gateways will not let you take your data with you. If you decide to use the Authorize.net CIM service with the SaaS Kit, this will be an additional charge for access to credit cards for $ 20 / month.

I also recommend that you take a look at the API docs for each product. Depending on the complexity of integrating with Recurly, some merchants will never need to work with the API (instead, they use the hosting hosting verification pages and the virtual admin console inside Recurly), but other merchants will have a more complex billing scenario that involves using the API. The documents for each product should give you an idea of ​​how easy it will work.

I would be happy to answer any of your questions while you keep watching!