3 ms·
Agreed, making the plans hard to modify definitely makes sense, but then I feel like I need another abstraction on top of Stripe. Have you come across any good
by servercobra 8y ago
Agreed, making the plans hard to modify definitely makes sense, but then I feel like I need another abstraction on top of Stripe. Have you come across any good ways for handling this?
- kwindla 8y agoNo, haven't seen anything. Everything looks like a hammer, of course, but to me this just feels like a general software engineering thing, if that makes sense -- building an abstraction on top of a library service. Our plan is to evolve the plans literal in our code into this abstraction (it already kind of is). Next step is probably to add something a little like feature flags, but we're still thinking this through.
- nicodjimenez 8y agoIs there any downside to just using the payments api and not use any of the other stripe features? Subscriptions can be implemented manually right?
- kwindla 8y agoYes, subscriptions can be implemented manually. We did that two years ago before Stripe had the full “Billing” API. One big win you get with Billing, though, is automatic generation of invoices each subscription period. It’s nice not to have to write that code, and the automatic invoices tie in nicely to a few other things Stripe can do better than we can, like automatic retries of payments that fail.
- nicodjimenez 8y agoAt the cost of how much complexity? Is it worth it if you want to stay maximally flexible in how you charge?