How Stripe Became the Financial Infrastructure of the Internet
From two brothers with a simple payment API to the dominant payment infrastructure company. The business model, the moat, and the question of whether Stripe will ever go public.
The Original Insight That Changed Payments
In 2010, Patrick and John Collison, brothers who were 21 and 19 respectively, identified a problem that seemed mundane but was actually enormous: accepting payments online was absurdly complicated. Legacy payment processors required weeks of paperwork, opaque approval processes, technical integration that took months, and fee structures that made no sense for startups. The dominant players, PayPal, Authorize.net, traditional merchant acquirers, had been built for a brick-and-mortar world and retrofitted for the internet. None of them had been built natively for developers. The Collisons' insight was to make payment acceptance a seven-line code snippet. Their original API was elegant in a way that payments had never been: you could copy the integration code directly from the documentation and have a working payment flow in hours, not weeks. By winning developers, Stripe became embedded in products before those products had customers, creating switching costs that only grew over time.
Stripe did not compete on price or features in the traditional sense. It competed on developer experience, a category most financial companies did not know existed. Once a developer integrated Stripe into a product, every customization, every webhook, every piece of business logic built around the Stripe API was a reason not to migrate to a competitor.
The Expansion Playbook
What makes Stripe's story analytically interesting is the discipline of its expansion. Most fintech companies expand by moving into adjacent consumer products. Stripe consistently stayed focused on business customers and went deeper into the payments and financial services stack rather than broader into consumer. Stripe Atlas (global business formation), Stripe Treasury (banking-as-a-service), Stripe Radar (fraud detection), Stripe Connect (marketplace payments), Stripe Billing (subscription management), Stripe Issuing (card issuance), each product expanded the Stripe relationship with existing customers while deepening switching costs. A company using Stripe for payments, fraud detection, banking, and marketplace payouts faces an enormous migration challenge to leave. It is not one integration to replace, it is dozens. The business model is elegantly simple: approximately 2.9% plus $0.30 per online transaction, with volume discounts negotiated for large customers. Revenue grows automatically as the businesses using Stripe grow, without requiring additional sales spend. That is a structurally attractive economics model.
The Valuation History and the IPO Question
Stripe's private valuation has been volatile in ways that tell you something about both the company and the broader VC market. The company raised at a $95 billion valuation in 2021, fell to $50 billion in 2023, a 47% markdown reflecting rising rates and declining growth multiples, and recovered to approximately $65-70 billion by 2025 as it approached profitability and revenue growth re-accelerated. The 2021-to-2023 compression was not about Stripe's business fundamentally changing. It was about what the market was willing to pay for a dollar of future earnings as interest rates rose from 0% to 5%. The IPO question is one the company has carefully avoided answering. Patrick Collison has consistently said Stripe will go public when it makes sense for the company. The company has the financial profile to sustain private status indefinitely, having approached EBITDA profitability in 2024. The question is not if but when, and that timeline is controlled entirely by the Collisons.