I've worked with quite a few payments platforms over my career. Most of them are terrible, but even the good ones require adopting their conceptual model. Somet

I've worked with quite a few payments platforms over my career. Most of them are terrible, but even the good ones require adopting their conceptual model. Sometimes that can require some adjustment, especially if you already have preconceived notions of how you want billing to work. Example: I was dumbfounded that Stripe lets you update a balance, but offers no way to do it atomically. Support was clueless. However, on the IRC channel someone suggested creating invoices instead of bumping the balance, which in retrospect is a much better idea than maintaining the history in my database (although it ties me deeper to their system). You really have to "bend like a reed" and conform to their patterns. And whatever you do, don't try to create an abstraction across multiple billing systems until after you've built up some expertise.