How the Collison Brothers Conquered Online Payments Without Anyone Noticing

In 2010, payment processing was a solved problem. Or so everyone thought. You wanted to accept credit cards online? You called a bank, filled out twenty forms, waited three months for approval, and integrated with a clunky legacy system that broke every time the wind changed direction. It was expensive, complicated, and utterly miserable. But it was the industry standard.

Nobody was angry about it because nobody knew it could be better. That's where Patrick and John Collison came in.

The two Irish brothers didn't invent payment processing. They invented the idea that payment processing could be good.

The Irish Immigrant Kid Who Coded in Haskell

Patrick Collison was 20 years old, living in Dublin, when he realised that online payments were a catastrophe. He'd been trying to build a web service and wanted to accept credit cards. The process was so nightmarish that he basically couldn't do it. He looked at other developers facing the same problem and realised they were all drowning in the same friction.

He wasn't an entrepreneur. He was a kid who was interested in functional programming. He went to MIT for college. He was learning Haskell and thinking deeply about programming language design. By all accounts, he could have become an academic or a pure software engineer. Instead, he looked at the payment infrastructure and saw a massive, obvious gap.

The gap wasn't technical in the sense of "nobody has built this yet." Legacy payment processors had solutions. The gap was experiential. You had to fill out forms. You had to talk to sales people. You had to integrate XML APIs designed in 1997. A single request to process a payment looked like something from a Cold War spy manual.

Patrick brought his younger brother John into the idea. John had been studying maths and physics at Trinity College Dublin. Now the two of them were going to build a payment company.

Y Combinator and the Developer-First Bet

In 2009, they applied to Y Combinator. Paul Graham's accelerator was still new, still scrappy. Stripe got in. They moved to San Francisco. And they did something genuinely novel: they decided to build payment processing for developers first.

This sounds obvious in retrospect. It shouldn't have been novel. But every payment processor at that time was optimised around sales teams and bank relationships. They thought like financial institutions. They thought about risk and compliance (important, sure) but forgot about the actual person who had to integrate the system.

The Collisons thought about the developer sitting at 3am, trying to get a checkout flow working. What would make that person's life better? A cleaner API. Documentation that actually explained things. No sales call required to get started. No forms. No three-month approval process. Just sign up, read the docs, start processing payments in minutes.

So they built an API that was so simple and well-designed that developers actually wanted to use it. This wasn't trickery. It wasn't marketing smoke. It was just better engineering.

They launched in 2011 with a stunningly simple idea: a seven-line code snippet that would let any developer accept credit cards. Seven lines. That's it. Compared to the previous standard of three months and a binder full of contracts, it was magical.

The Network Effects of Developer Love

Here's where Stripe's strategy became genuinely brilliant. Developers don't just buy products; they recommend products to other developers. If you build something that solves a problem elegantly, developers become your sales force. They tell other developers. They blog about it. They recommend it in Stack Overflow threads. Word of mouth becomes viral in engineering circles.

Stripe became the status symbol of a well-built startup. If you were using Stripe, it meant you had good taste in infrastructure. It meant you cared about your customer experience. It meant you weren't a scrappy hack that was just trying to squeeze money out of people.

The network effect worked both ways. As more startups adopted Stripe, Stripe got better. They could see what products worked, what payment patterns emerged, where the rough edges were. They iterated obsessively. They hired the best engineers from the best companies. They built features that solved real problems because they could talk directly to their users.

Meanwhile, the legacy payment processors were still selling through call centres.

The Private Company Strategy

By 2012, Stripe had raised money from top-tier venture capitalists. Sequoia, Andreessen Horowitz, Y Combinator. They were growing explosively. The obvious next step was to go public and let founders and early investors cash out.

Stripe didn't do that. Patrick and John Collison decided to stay private. They had enough money. They didn't need a public market. And most importantly, staying private gave them something far more valuable than a high stock price: optionality.

Every quarter, Stripe didn't have to answer to institutional shareholders demanding short-term profitability. They could invest in long-term infrastructure. They could build products that took years to pay off. They could expand into markets that seemed marginal but were actually massive. They could stay focused on being genuinely good instead of managing perception.

Over the next decade, Stripe became the infrastructure layer for the internet. Not just startups, but established companies. Shopify integrated Stripe. Amazon integrated Stripe. Uber integrated Stripe. Not because Stripe was the flashiest option, but because it worked reliably, scaled painlessly, and felt like it was built by people who actually understood how the internet works.

The Road to $95 Billion

By 2023, Stripe was valued at $95 billion in a secondary market. Not publicly traded, but its value was undeniable. The company was generating billions in revenue annually. It had built its own payment network, its own fraud detection system, its own banking partnerships. It had become the plumbing of modern commerce.

Competing payment processors had tried to match Stripe's developer experience. They'd hired good engineers. They'd improved their APIs. Some of them—Square, particularly—had built genuinely excellent products. But none of them had Stripe's brand cachet among developers. None of them felt like they were built by engineers for engineers.

The Collisons had made a bet that seemed insane at the time: that if you built something so good that developers loved it, if you stayed focused on that mission even when you had the money to diversify, if you resisted the pressure to go public and prioritise short-term earnings, you would eventually become invaluable.

They were right.

The Larger Lesson

Stripe's story offers a template that countless tech companies have tried to copy. Build the best product in your category. Listen obsessively to your users. Hire exceptional engineers. Resist the pressure to move into adjacent categories unless it genuinely serves your mission. Stay long-term greedy instead of short-term greedy.

The difference between Stripe and companies that tried to follow this playbook is that the Collisons actually executed. They didn't cut corners. They didn't compromise. They had the patience to let their strategy work.

Today, Stripe is one of the most powerful companies in payments without most people knowing it exists. You've probably used Stripe a hundred times without realising it. That anonymity, that invisibility, is actually a sign of success. The best infrastructure disappears. You don't think about the wiring in your house. You just flip a switch and expect the light to come on.

That's what Stripe accomplished. Two Irish kids who couldn't get a payment processor to work built a $95 billion company by making payment processing so good that nobody has to think about it anymore.

Not bad for a solution to a problem people didn't know they had.