Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Yup, this was a lesson I learned the hard way when I built out billing for our SaaS product. I had spent weeks thinking about user accounts, team accounts, subscription, integration with Stripe, how the UI would look, how I would verify VAT numbers for European customers, etc etc etc. In the end I threw all the code away because not a single customer that we had would have used self-checkout billing anyway, everything happens via email, purchase orders, billing portals like Ariba, etc. Monthly subscriptions are far and few between, pay-per-use is something that almost no customer would be interested in. Some customers actually wanted multi-year subscriptions, which Stripe doesn't even support.

It's emails and spreadsheets all the way down if you're building a product for an Enterprise audience.



Based upon this series of postings, it sounds like the problems in the original tweet are the result of decoupled enterprise payment systems, rather than the opposite. As if someone somewhere forgot to manually flip some flag or that they paid wasn't properly distributed throughout the byzantine distributed system.


The GGP used the wrong term. What he describes is a system that is overridable, not decoupled.

You are right in that decoupled systems aren't good.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: