The Boy Who Had to Pitch for Internet
Patrick Collison was thirteen years old when he made his first pitch. The audience was his parents, the ask was satellite internet, and the setting was rural Ireland, where a reliable connection to the outside world was something you had to argue for rather than assume. He got the satellite dish, and through it he found programming, a discovery that would eventually reshape how money moves across the internet.
Growing up without consistent connectivity sharpened something in Patrick: a precise, almost physical understanding of what access could unlock for someone willing to reach for it. When the satellite connection finally arrived, he dove into code. His younger brother John came along behind him, and the two of them developed in parallel, as siblings and as collaborators, each pushing the other deeper into the mechanics of how software worked and what it could build.
By the time the Collisons crossed the Atlantic in 2006, Patrick at eighteen and John at sixteen, they had already crossed more than an ocean. Their first startup, Auctomatic, was a tracking and management tool for eBay sellers, and they sold it for $5 million before either of them had finished university. Patrick had enrolled at MIT; John was on his way to Harvard. Both would eventually leave their respective institutions behind, pulled toward the work itself rather than the credential it conferred.
That exit reframes everything that came after. When Stripe appeared, it would be easy to read the Collisons as young founders riding early luck, two brothers who happened to find themselves in the right place at the right time. The Auctomatic sale tells a more precise story: these were people who had already identified a market friction, built a product around it, found paying users, and completed a transaction. They understood the full arc from idea to company to exit. Stripe, when it came, was a sequel built on proven instincts.
Patrick has spoken about his Irish upbringing as foundational to how he thinks about technology and access. The boy who had to make a formal case for a satellite dish grew into a founder with a deep intuition for what it feels like when infrastructure fails you, and what changes when it finally works. That intuition, formed years before any startup existed, sits at the core of what Stripe would become: a company built by people who had encountered friction from the inside, and who had spent years thinking hard about what the world looks like once you clear it away.
A Bus Ride Back from Berkeley Changed Everything
That instinct for broken infrastructure met its test case in 2009, when the brothers attended a Y Combinator Startup School event at UC Berkeley. On the way back from that event, John floated the idea: build a prototype of an easy way to move money online. The suggestion was quiet, almost offhand, which made it all the more telling. The most obvious ideas often announce themselves like that, calmly, as though they had simply been waiting for someone to say them out loud.
What made the idea feel both obvious and audacious was what actually lay behind it. Taking a payment online in 2009 was, for any developer building a business, a weeks-long ordeal. A merchant account had to be opened, a process requiring a formal application, business documentation, and the goodwill of a banking partner. That merchant account then had to be connected to a payment gateway, a separate integration that came with its own set of credentials, its own documentation, and its own failure modes. Once a customer was ready to pay, the typical experience shunted them away from the website they were already on and out to a third-party checkout page, a jarring redirect that broke the flow of the transaction and, often enough, the transaction itself. The whole pipeline, from first line of integration code to live payments, could take a month to stand up.
For large companies with dedicated engineering and compliance teams, that friction was a tax they could absorb. For the developer with an idea and a weekend, it was closer to a wall. Every small business, every independent creator, every early-stage startup that wanted to charge customers for something faced the same gauntlet, a payment infrastructure built for banks, interpreted by developers, and experienced by founders as a grinding bureaucratic exercise before any real work could begin.
John's suggestion on the ride back from Berkeley named that problem plainly. The question was whether someone could collapse all of it, the merchant accounts, the gateway integrations, the checkout redirects, into something a developer could simply drop into their code and have working the same afternoon. It was a genuine question, because the technical and regulatory complexity underneath payments was substantial, and the incumbents who had tried to simplify it had largely stopped at making it slightly less miserable rather than rethinking it from the ground up. The Collisons decided the question was worth answering properly, and that decision, made on a bus ride home from a startup event, became the founding act of Stripe.
SLASHDEVSLASHFINANCE and Other Early Indignities
The Collisons believed an answer existed, and by the summer of 2010 they were deep enough into building it that they needed a company to put it inside. Their original name was /dev/payments, a reference legible to any Unix programmer and completely opaque to everyone else, which, given their target audience, suited them fine. Delaware had other ideas. The state does not allow leading slashes in corporate names, so the company was forced to incorporate as SLASHDEVSLASHFINANCE, a name that managed to be both bureaucratically compliant and entirely absurd. It was the kind of early-days detail that reveals how improvisational the whole enterprise still was: two brothers in their early twenties, building something ambitious, temporarily saddled with a corporate identity that sounded like a bad password.
The search for a real name was equally makeshift, and equally revealing. Patrick and his colleagues assembled a list of candidates by emailing the owners of .com domains to shrink the search space to names they could actually acquire. PayDemon made the list. So did PayForge. Neither stuck, and with no clear winner emerging, the team set a deadline: if something better hadn't surfaced by December 20, 2010, they would go with Stripe. Patrick had been reading The Little Kingdom, Mike Moore's history of Apple, and recognised the same logic the founders there had used, name it or the calendar names it for you. When the owner of Stripe.com replied to their email with a price inside their budget, the decision made itself.
By then, Patrick was 22 and John was 20, and the company they were naming had already been shaped by Y Combinator's Summer 2010 batch, where the product sharpened and the ambition found language. The mission they settled on was broad enough to be genuinely aspirational and specific enough to mean something: to increase the GDP of the internet. The framing said something important about how they understood the problem. Online commerce was not stalling because of a lack of demand or a shortage of ideas, it was stalling because the financial plumbing beneath it was so difficult to connect that vast numbers of potential businesses simply never got started. Every integration that took a month was a business that might not survive long enough to complete it. Stripe's stated purpose was to fix that, and the name on the door, plain and short and finally free of leading slashes, reflected the same instinct: make the hard thing simple enough that it disappears.
Seven Lines of Code Did What a Month of Work Used to
The framing said something important about how they saw the customer. Finance teams had never been the audience. Developers were, and that distinction drove every decision about what Stripe's product would actually look like.
The central achievement was compression. What had previously taken a month of integration work, merchant account applications, gateway setups, the whole bureaucratic machinery of getting a business ready to accept a card payment, Stripe collapsed into seven lines of code. A developer could read the documentation, drop in the snippet, and be live. The friction that had defined online payments for years simply ceased to exist for anyone building on Stripe.
The API was clean in a way that felt almost conspicuously considered. Client libraries covered the common web languages, so developers could work in whatever environment they already used. Card data routed directly to Stripe's secure environment, which meant the merchant never had to handle sensitive payment information or worry about the compliance obligations that came with it. Recurring billing and card storage were built in natively, not bolted on as afterthoughts. Pricing was a single flat rate: 2.9% plus $0.30 per transaction, no monthly fees, no tiered complexity, no need to call a sales team. Payouts rolled into the merchant's bank account on a predictable schedule. Every element of the product answered a specific grievance that developers had carried for years, and the answer in each case was the same: we made it simpler.
The product thesis, stated plainly, was that any developer should be able to start accepting payments in minutes. Aimed squarely at builders rather than procurement officers or finance departments, that thesis was also a strategic bet, that the people who chose the payment infrastructure for a new product were the people writing it, and that winning their loyalty early meant being embedded before a company ever grew large enough to have a CFO with opinions about vendors.
The public launch came on September 29, 2011, when Patrick Collison submitted a link to Hacker News with the title
The Seed Round That Reads Like a Who's Who
That Hacker News post went up into a world that had already, quietly, placed a large bet on Stripe. Earlier in 2011, the company had closed a $2 million seed round whose investor list reads less like a cap table and more like a reunion of the architects of the previous internet era: Elon Musk, PayPal founder Peter Thiel, Irish entrepreneur Liam Casey, Sequoia Capital, Andreessen Horowitz, and SV Angel all signed on. The names mattered for reasons beyond the money. Thiel had co-founded PayPal and understood, from direct and painful experience, exactly how broken online payments were. Musk had tried to build an internet bank at X.com before it merged into PayPal. Sequoia and Andreessen Horowitz had between them funded much of the infrastructure the web already ran on. When people who had spent a decade fighting the same problem decided to back two brothers in their early twenties rather than solve it themselves, that was a considered judgment about who had finally cracked it.
The signal those names sent to the broader market was hard to overstate. Silicon Valley runs on pattern recognition, and the pattern here was unmistakable: the people who knew the most about internet payments believed Stripe had identified something real and large. That $2 million gave the Collisons the runway to move from a scrappy Y Combinator product into something with genuine infrastructure behind it, and the credibility to attract the kind of developer talent that would spend the next decade building out what those seven lines of code had promised.
Stripe's first acquisition arrived in March 2013, and its modesty was part of the point. The company bought Kickoff, a small chat and task-management application, which looked from the outside like an odd early move for a payments company. Looked at differently, it made a kind of quiet sense: Stripe had always been building for the people who build things, and owning more of the operational layer around the transaction, the coordination, the workflow, the connective tissue, hinted at an ambition that went well beyond processing a card charge cleanly. The core product was the entry point; the question Stripe was already asking was how much of what surrounds a transaction it could eventually own.
From Five Million Businesses to $1.9 Trillion
Owning more of the operational layer around payments was a natural extension of that instinct. What followed over the next decade was a case study in what happens when a piece of infrastructure quietly becomes load-bearing for an entire economy. The numbers accumulated almost without drama, each one larger than the last, until the aggregate became genuinely difficult to hold in the mind at once.
By 2025, Stripe was processing over $1.9 trillion in payment volume annually, serving five million businesses in the process. The customer list had grown from scrappy developer-led startups to some of the largest companies on earth, including Ford and Amazon, with operations reaching across almost 50 countries. Revenue came in at $5.1 billion in 2024. The company that Patrick Collison once incorporated under the name SLASHDEVSLASHFINANCE, because Delaware refused a leading slash, had become a quiet pillar of the global economy.
The valuation arc tells its own story. Stripe peaked at $95 billion in 2021, a figure that drew the kind of breathless coverage that tends to age badly, and for a time it did, the broader tech correction pulled valuations across the industry down hard. Stripe's held, and then climbed. By 2025, the company carried a valuation of approximately $159 billion, cementing its position as the largest privately held fintech company in the world. It has stayed private through all of it, a deliberate choice that has kept the Collisons free from the quarterly pressures that shape so many companies of comparable size.
The 8,500 employees working across dual headquarters in South San Francisco and Dublin represent the full span of what the company has become: part Silicon Valley infrastructure play, part Irish success story, entirely its own thing. The Dublin anchor is worth noting because it reflects something genuine about where the founders came from and what they built toward, a company with real roots on both sides of the Atlantic, serving businesses on nearly every continent.
The numbers land differently once you understand the problem they solved. Every dollar of that $1.9 trillion passed through infrastructure that, before Stripe, would have required weeks of integration work, a merchant account, a gateway setup, and a checkout flow that pushed customers off-site and away from the experience a developer had spent months building. The friction was so ordinary that most people in the industry had stopped noticing it. The Collisons noticed, reduced the whole thing to seven lines of code, and built a company worth more than most of the world's largest banks on the back of that single, clarifying observation.
Increasing the GDP of the Internet, One Transaction at a Time
The friction was so ordinary that most people had stopped questioning it. Stripe's achievement was to make the friction visible by removing it, and in doing so, reveal just how much it had been costing.
The phrase Patrick Collison has used to describe the company's purpose, to increase the GDP of the internet, sounds like a mission statement until you map it against specifics. Every business that signed up to Stripe and started taking payments that same day, rather than weeks later, could generate revenue sooner. Every developer who spent seven lines of code instead of a month of integration work could redirect that time toward building something else. Multiplied across five million businesses in almost fifty countries, the compounding effect on what the internet actually produces is what the mission is describing, precisely and literally.
Stripe's product ecosystem has grown well beyond the original payment API. As of May 2025, it spans four broad categories: payment services, money management and embedded finance tools, revenue and finance automation products, and platform infrastructure and extensions. The surface area has expanded considerably, but the underlying logic remains the one the Collisons arrived at from the beginning, that businesses ought to focus on what they are building, while Stripe manages the financial plumbing beneath them.
That logic came from a specific kind of experience. Patrick Collison grew up in rural Ireland without reliable internet, and the years he spent on the wrong side of that access gap gave him something precise: a feel for what barriers cost in time, in opportunity, in things that simply never get built. The satellite internet he eventually talked his parents into at age 13 gave him programming, and programming gave him a view of what the internet could do for people who could actually reach it. The payment problem he and John identified was, underneath the technical language, the same kind of problem, a barrier that looked like a plumbing issue but functioned as an economic one, keeping businesses on the wrong side of a threshold they should have been able to cross in an afternoon.
The company they built to clear that threshold has become one of the quieter pieces of consequential financial infrastructure in the world. Dual-headquartered in South San Francisco and Dublin, with 8,500 employees and customers ranging from independent developers to Ford and Amazon, Stripe sits inside the global economy in a way most of its users never think about, which is, of course, exactly the point. Good infrastructure disappears. You build on top of it and forget it's there.
The GDP of anything measures the total value of what gets produced. Every transaction that now happens because the barrier to accepting a payment was low enough to clear, a small business in Dublin, a freelance developer in Lagos, a startup in São Paulo that launched in a weekend, that is what the mission is counting. The friction the Collisons removed was real and specific, and so is what grew up in its place.
Comments (0)