4 ms·
Great list, thank you. One option is to always have more than one payment processor activated. Splitting payments across providers early on doesn’t have to
by j45 4y ago
Great list, thank you.
One option is to always have more than one payment processor activated.
Splitting payments across providers early on doesn’t have to be a bad thing.
There are libraries focused in billing and payment management and leaving the payment processing only to stripe, etc. These libraries that can handle multiple payment providers and help reduce dependency on the a single payment provider for payment management functionality.
It’s always felt like a risk.
One stand alone library that I’m looking at is https://killbill.io/ https://killbill.io/
If there are alternatives to this that folks have experience with - it would be great if you could share
- anton-stigg 4y agoHey, there's Stigg (http://stigg.io/ http://stigg.io/) and its like an abstraction layer on top of billing for SaaS. I think it counts as an alternative to killbill in some way.
- j45 4y agoThank you, didn’t know this existed