>I don't like outsourcing subscription logic at all. It's not difficult to do yourself, yet expensive to outsource I disagree, and I say this as someone who ju

>I don't like outsourcing subscription logic at all. It's not difficult to do yourself, yet expensive to outsource I disagree, and I say this as someone who just finished writing a recurring billing engine. If your needs are simple (basic plans that vary in price but not necessarily in length) and you don't have much need for being able to precisely control things like add-ons, discounts, etc, then going with something like Stripe, Recurly, or Braintree is the best option. If you need custom logic, which we did, definitely roll your own. But it's a lot trickier to do than you'd expect. I'll give you an example of a case we need to support: handling a case where a user purchases a monthly subscription, upgrades to a yearly subscription of a different plan, but mid-way through decides they don't like it (during the trial period) and want to rollback to the monthly subscription. Writing generic logic to handle refunds, billing dates, etc is tricky, but doable. In my mind there's no need to go through the pain of writing the whole thing yourself if the use case is simple and you don't need complex logic.