4 ms·
Is there any downside (other than a little more work for the implementer) to just using their main payment processing API, and to implement subscription billing
by nathcd 6y ago
Is there any downside (other than a little more work for the implementer) to just using their main payment processing API, and to implement subscription billing with a cronjob? This is what sr.ht does [1], at least as of a year ago. If doing it manually now means saving a bunch of money, seems like a no-brainer.
[1] https://cmpwn.com/@sir/103074952842876982 https://cmpwn.com/@sir/103074952842876982
- drchiu 6y agoWe did that for a couple of SAAS. In fact, we even extracted this out to an internal library with a web UI. If anyone is interested, let me know and I’d be happy to open source it. It’ll have to be run in its own server and process. But for full disclosure, my latest project just bit the bullet and accepted the extra 0.5%. Wanted to see how it goes. Could always switch if I found the need.
- tomsi 6y agoWe'd definitely be interested since we are currently evaluating our options
- corentin88 6y agoInterested as well!
- driverdan 6y agoThe downside is that you have to write and maintain the code and infrastructure to do it. You have to do the math for your business to decide if those costs are lower than the 0.5% fee.