Stripe

Two lines of code

Before Stripe, accepting a credit card on the internet was a bureaucratic ordeal. A developer had to register a merchant account, negotiate with a payment gateway, handle PCI compliance paperwork, and stitch together a half-dozen APIs that were designed for point-of-sale terminals, not web applications. The process took weeks and often required a phone call to a bank.

Patrick and John Collison saw this friction firsthand while building side projects as teenagers in Limerick, Ireland. Their insight was not that payments were hard — everyone knew that — but that the difficulty was entirely artificial. The underlying card networks already worked. What was missing was a clean abstraction layer that let a developer move money with the same ease they could send an HTTP request.

The result was an API so simple it became a meme in Silicon Valley: add two lines of code and start accepting payments. No merchant account, no gateway contract, no weeks of paperwork. Stripe handled compliance, fraud detection, and bank relationships behind a single endpoint. For developers, it felt like magic. For the payments industry, it was an existential challenge to decades of entrenched middlemen.

YC and the Collison brothers

Patrick Collison was nineteen when he and John entered Y Combinator in the summer of 2010. They had already sold their first company, Auctomatic, to a Canadian firm for a reported $5 million while still in their teens. The YC partners did not need much convincing: the Collisons were technical founders attacking a market that touched every internet business on the planet.

YC’s $18,000 check was symbolic. What mattered was the network. Through YC, the Collisons met Peter Thiel, who led an early angel round alongside Elon Musk, Max Levchin, and other PayPal alumni. The irony was deliberate: the people who had built the first wave of internet payments were now betting that Stripe would render their own creation’s developer experience obsolete.

The people who had built the first wave of internet payments were now betting that Stripe would render their own creation’s developer experience obsolete.

Sequoia Capital came in at the seed stage with $2 million at a $20 million valuation, unusual confidence for a company with almost no revenue. Michael Moritz, who had backed Google and Yahoo, reportedly told colleagues that Stripe reminded him of the early Google API — a product so clearly superior that distribution would take care of itself.

Growing through developer adoption

Stripe did not hire a sales team for its first several years. It didn’t need one. The company grew through word of mouth among developers who recommended it on Hacker News threads, in Stack Overflow answers, and in Slack channels. Every new developer who integrated Stripe became an unpaid evangelist, because switching back to the old way of processing payments was unthinkable once you had experienced the alternative.

By 2012, Stripe had enough traction that Sequoia returned to lead the Series A: $18 million at a $100 million valuation. The round valued Stripe at roughly fifty times its annualized revenue, a multiple that only made sense if you believed the company would become infrastructure — not just a product but a layer of the internet stack, like AWS for payments.

That bet proved correct. Stripe expanded from simple card processing into subscriptions, invoicing, fraud prevention, issuing, treasury, and eventually an entire financial operating system. Each new product deepened the moat: once a company ran its billing, payouts, and compliance through Stripe, switching costs were enormous. By 2021, Stripe was processing over $817 billion in annual payment volume for more than a million businesses worldwide, valued at $95 billion.

What founders can learn

The Stripe story is, at its core, a case study in building a product so good that fundraising becomes a formality. The Collisons did not raise their seed round by pitching a slide deck about market size. They raised it by handing investors a laptop and showing them what it felt like to integrate Stripe versus the existing alternatives. The product was the pitch.

Three lessons stand out. First, developer-first products can create enormous businesses when the developers in question control purchasing decisions. Stripe succeeded because individual engineers chose it, then their companies ratified the choice. Second, the best distribution strategy is often no distribution strategy at all — if the product is a genuine order-of-magnitude improvement, word of mouth scales faster than any sales team. Third, the Collisons understood that payments were not a feature but a platform. By positioning Stripe as infrastructure from day one, they ensured that growth compounded rather than plateaued.

The best distribution strategy is often no distribution strategy at all — if the product is a genuine order-of-magnitude improvement, word of mouth scales faster than any sales team.

For founders exploring their own fundraising journey, Stripe is a reminder that technical moats matter. Investors at every stage — from YC to Sequoia to Tiger Global — were not betting on a payments company. They were betting on the idea that the best developer experience would eventually capture the largest share of internet commerce. They were right.

Key funding rounds