Global Startup Funding +18% QoQAgentic Workflows: Primary FocusFintech Infrastructure: ExpandingFoundation Model Cost -38% YoYClimate Tech: Sector WatchAutonomous Systems: AcceleratingCompute Demand +67% QoQHealthTech Innovation: Critical PathD2C Brands: Emerging MarketsDeep Tech: Active MonitoringEdge AI Deployment: Growth PhasePre-Seed Deals +210% AdoptionGlobal Startup Funding +18% QoQAgentic Workflows: Primary FocusFintech Infrastructure: ExpandingFoundation Model Cost -38% YoYClimate Tech: Sector WatchAutonomous Systems: AcceleratingCompute Demand +67% QoQHealthTech Innovation: Critical PathD2C Brands: Emerging MarketsDeep Tech: Active MonitoringEdge AI Deployment: Growth PhasePre-Seed Deals +210% Adoption
Back to Library
CASE STUDYNov 2024

How Stripe Started: Two Brothers, One API, and the Bet That Payments Were Broken

Patrick and John Collison built Stripe because accepting payments online was unreasonably hard. Fifteen years later, it processes over $1 trillion annually.

In 2009, Patrick Collison was 20 years old. His brother John was 19. They had dropped out of MIT and Harvard respectively, moved to Palo Alto, and decided that the way businesses accepted online payments was fundamentally broken.

At the time, if you wanted to accept credit card payments on your website, you had to deal with merchant accounts, payment gateways, PCI compliance, and a mountain of paperwork. The process took weeks. Sometimes months. It was designed for large corporations, not for developers building internet products.

The Collisons thought this was absurd. Their pitch was simple: what if you could start accepting payments with seven lines of code?

The First Version

Stripe launched in 2011 after two years of quiet development. The initial product was almost comically simple compared to the incumbents. A single API. Copy the code into your website. Start charging credit cards. That was it.

No merchant account applications. No weeks of paperwork. No phone calls with sales representatives. Just code.

The developer community went insane for it. Not because the underlying payment processing was revolutionary. It was not. What was revolutionary was the developer experience. Stripe treated payments like a software problem, not a banking problem.

What Made Stripe Different

They sold to developers, not to CFOs. Every other payment company marketed to business executives. Stripe marketed to the person writing the code. They understood that in the internet era, the developer is often the decision-maker for infrastructure choices.

The documentation was the product. Stripe's API docs were, and still are, considered the gold standard of technical documentation. Clean. Clear. With working code examples in every major language. This was not an accident. It was a strategic choice.

They expanded horizontally, not vertically. Instead of going deeper into payments, Stripe expanded into billing, invoicing, fraud prevention, incorporation, treasury management, and lending. They became the financial infrastructure for the internet, not just a payment processor.

The Numbers Today

Stripe processes over $1 trillion in payments annually. It is valued at $65 billion after its 2023 fundraise. It powers payments for Amazon, Google, Shopify, and millions of startups. About 80% of Americans have used Stripe without knowing it.

What Founders Can Learn

The Stripe story is not about payments. It is about recognizing when an existing industry has been designed for the wrong customer. Payments were designed for banks and large merchants. Stripe redesigned them for developers and startups.

Ask yourself: what industry are you looking at where the product was designed for the customer of 20 years ago, not the customer of today? That gap is where massive companies get built.

Interested in what we are building? Apply through the Founder Intake Terminal.