3 ms·
In my experience, it should be no more difficult than sending recurring emails. You should have all the data (PaymentProcessorCustomerID, LastBillingDate, etc)
by candiddevmike 6y ago
In my experience, it should be no more difficult than sending recurring emails. You should have all the data (PaymentProcessorCustomerID, LastBillingDate, etc), run it like you would a email with a retry queue.
- abfan1127 6y agoits more than that. The "What ifs" get out of control pretty quickly. Prorating, canceling, expired/canceled cards, tend to create a ton of end cases. For instance, a person pays for Feb 15 to Mar 14, the card expires March 1, then the person requests a cancellation Mar 7 and wants a refund. Its not impossible, it just takes a lot of time and effort to weasel out all of these end cases.
- candiddevmike 6y agoIn the example you gave, how would stripe billing solve that? This seems like you'd need some kind of manual interaction regardless? For all the end cases, you manually handle them until they happen with enough frequency to require automation. A simple recurring billing system is absolutely fine for most businesses, and as you scale you can add more bells and whistles to it.
- abfan1127 6y agoI think you're right in this case. I haven't looked at the problem in about 10-15 years (before Stripe had recurring). I remember there being a ton of end cases I had to deal with. We ended up going with Recurly due to it.