How the Collison Brothers ConqueredOnline Payments Without Anyone Noticing
Patrick and John Collison built Stripe by solving a problem nobody else thought mattered: developer friction.
Opening
Two kids from Ireland couldn't figure out how to accept credit cards online. So they built a $95 billion company instead.
In 2010, if you wanted to process payments, you called a bank. You filled out twenty forms. You waited three months. You integrated with systems that felt like archaeological artefacts. Everyone accepted this because everyone assumed it couldn't be better.
Patrick and John Collison saw things differently.
The 20-Year-Old Who Broke Payments
Patrick Collison was 20, coding in Dublin, trying to build a web service. The payment integration was so painful he nearly gave up. Every developer he knew was drowning in the same quicksand: XML APIs from 1997, sales calls that led nowhere, documentation written by people who'd clearly never touched code.
Two kids from Ireland couldn't figure out how to accept credit cards online. So they built a $95 billion company instead.
He wasn't thinking about becoming an entrepreneur. He was studying functional programming languages like Haskell at MIT. But looking at payment infrastructure, he spotted something everyone else had missed.
The technology worked. The experience was torture.
Legacy processors had solutions, sure. But you needed a law degree to understand their contracts and a PhD in archaeology to decode their APIs. A single payment request looked like a Cold War encryption manual.
Patrick pulled his younger brother John (studying maths and physics at Trinity College Dublin) into the madness. Two college kids were going to fix payments.
Every other processor optimised for sales teams and bank relationships. The Collisons thought about the developer at 3am, pulling their hair out over a checkout flow.
Y Combinator and the Developer Gamble
They applied to Y Combinator in 2009. Paul Graham's accelerator was still finding its footing. The Collisons got in, moved to San Francisco, and made a bet that seemed obvious in hindsight but was radical at the time.
They built payment processing for developers first.
Every other processor optimised for sales teams and bank relationships. They thought like financial institutions. Risk management, compliance frameworks, enterprise partnerships. All important. All missing the point.
The Collisons thought about the developer at 3am, pulling their hair out over a checkout flow. What would make that person's life better? Clean documentation. No sales calls. No forms. No three-month approval gauntlet.
The best infrastructure disappears. You flip a switch and expect light. That's what Stripe accomplished for payments.
Just sign up and start processing payments in minutes.
They launched in 2011 with seven lines of code. That's all you needed to accept credit cards. Seven lines versus three months of paperwork. The contrast was absurd.
Two kids from Ireland couldn't figure out how to accept credit cards online. So they built a $95 billion company instead.
When Developers Become Your Sales Team
Here's where Stripe's strategy turned brilliant. Developers don't just buy products. They evangelise products. Build something that solves their problem elegantly, and they become your unpaid marketing department.
They blog about it. They recommend it in Stack Overflow threads. They mention it at meetups. Word spreads through engineering circles faster than gossip at a village pub.
Stripe became the status symbol of well-built startups. Using Stripe meant you had good taste in infrastructure. It meant you cared about user experience. It meant you weren't some cowboy operation held together with duct tape and prayers.
The network effect worked both directions. More startups meant more data. More data meant better fraud detection, smoother onboarding, fewer edge cases. Stripe could iterate obsessively because they were talking directly to their users instead of hiding behind call centres.
Meanwhile, legacy processors were still making developers fill out forms in triplicate.
The Private Company Advantage
By 2012, Stripe had raised money from Sequoia, Andreessen Horowitz, Y Combinator. Growth was explosive. The obvious move was going public, letting founders and early investors cash out.
The Collisons chose differently.
Staying private gave them something more valuable than a high stock price: optionality. No quarterly earnings calls. No institutional shareholders demanding short-term profits. They could invest in infrastructure that took years to pay off. They could expand into markets that seemed marginal but were actually massive.
They could focus on being genuinely good instead of managing perception.
Over the next decade, Stripe became the internet's payment plumbing. Not just scrappy startups, but Shopify, Amazon, Uber. Not because Stripe was flashy, but because it worked. Reliably. At scale. Built by people who understood how the internet actually functions.
Every other processor optimised for sales teams and bank relationships. The Collisons thought about the developer at 3am, pulling their hair out over a checkout flow.
The $95 Billion Validation
By 2023, secondary markets valued Stripe at $95 billion. The company was generating billions in annual revenue. They'd built their own payment network, fraud detection systems, banking partnerships. They'd become the invisible infrastructure powering modern commerce.
Competitors tried to match Stripe's developer experience. They hired good engineers, improved their APIs. Square built genuinely excellent products. But none captured Stripe's brand cachet among developers. None felt authentically built by engineers for engineers.
The Collisons had made a bet that seemed insane: build something so good that developers love it, stay focused on that mission even when you have money to diversify, resist public market pressure, and you'll eventually become indispensable.
They were right.
The Invisibility of Success
Today, Stripe powers payments for millions of businesses without most people knowing it exists. You've probably used Stripe hundreds of times without realising. That anonymity isn't a bug. It's the feature.
The best infrastructure disappears. You don't think about the wiring in your house. You flip a switch and expect light. That's what Stripe accomplished for payments.
Two Irish kids who couldn't get a simple integration working built a $95 billion company by making payment processing so seamless that nobody has to think about it anymore.
Turns out the biggest problems are often hiding in plain sight, disguised as "just how things work."
The best infrastructure disappears. You flip a switch and expect light. That's what Stripe accomplished for payments.
End of file
The next one drops Sunday at 7am.
One long-form story a week, plus the tools, frameworks and tactics I’m using to run my own media business. Written from the operator’s seat — not the consultant’s.
No threads. No spam. Reply anytime — I read every one.
