If you don't write your own billing system, either: >Option one: The group managing your billing system is going to take a cut of your revenue, and if you're

If you don't write your own billing system, either: >Option one: The group managing your billing system is going to take a cut of your revenue, and if you're really big, that's unacceptable. One example: Stripe takes about 3% [1]. If you're a major commerce company like Ebay which made roughly 10 billion dollars [1] last year and you used stripe (and lets say you did no negotiation and just used their defaults, unlikely but possible) that's 300 million dollars plus change you're leaving on the table by outsourcing. This means if you're in a position like that and it costs you less than 300 million dollars to build and maintain your billing system (and keep in mind 300 million buys you a team of 2,000 engineers and managers all working at fully loaded costs of 150k), then you're not going to outsource. >Option two: You're going to use an open source solution. Risk aversion is the critical point here: If your billing fails, or gives out product for free, in many cases, you no longer have a business. You cannot afford to get billing wrong, and so, in an environment where no "It just werks" open source solution exists, this isn't really a choice most management types can stomach. [1]https://memberful.com/blog/stripe-vs-paypal/ https://memberful.com/blog/stripe-vs-paypal/ [2]https://www.statista.com/statistics/507881/ebays-annual-net-revenue/ https://www.statista.com/statistics/507881/ebays-annual-net-...