recurly

What people need is a self-hosted, open source API that's as usable as chargebee or recurly, for instance.

We currently support Stripe and Braintree, with Recurly support going live in the next few days.

We then download the CSV data from Recurly and work out how much VAT should be attributed to the specific invoice.

Email me at ben at recurly dot com if you would like to chat.

You need your own merchant account to use Recurly or any of their competitors.

There's no reason that Chargebee, Recurly could not be emulated in open source software.

Chargify only supports Authorize.net, whereas Spreedly and Recurly support a few more options.

On the payments side: Recurly might be what you're looking for.

I like that you've added Braintree, Chargify & Recurly but can you tell us what makes you better than the aforementioned products?

The problem with subscription startups like chargebee, recurly, etc.

Both Chargify and Recurly are PCI compliant.

That aside, thanks for the book, I am buying it as I am sure that the advice will be relevant for the payment platform I will use (hesitating betweek Chargify and Recurly right now).

Many people look at Open Source and say "Why would I pay ChargeBee or Recurly $300 or $3000 per month when this is free?" Seems like a no brainer.

That's not to say that it's not a well-defined standard that you're going to end up having to follow in some way, but rather that statements like "Both Litle and Recurly flat out say that you need SAQ A-EP" have more wiggle-room than it would sound like, depending on the rest of the deal you're presenting them with.

This allows to write full integration specs for scenarios involving libraries like Stripe/Recurly.js etc, but using mocked calls.

It's fantastic, especially since Recurly's built-in reports don't seem to jive with reality (for instance by ignoring coupons on subscriptions).

Also, it isn't clear to me whether the accounts are stored in Recurly, or whether they are stored within the payment gateway.