Stripe

Stripe is the payments infrastructure company that lets any business accept money online with a few lines of code. Founded in 2010 by Irish brothers Patrick and John Collison, it turned a months-long banking ordeal into an afternoon's integration, and every story below traces back to the same choice: win developers first, then compound that wedge into the financial rails beneath the internet.

Counter-Positioning: seven lines of code against a sales-led incumbent stack

The problem. In 2010, accepting payments online meant applying for a merchant account through a bank, passing underwriting, and wiring up a clunky gateway like Authorize.net or PayPal's redirect flow, a process that took weeks and treated the developer as an afterthought. PayPal, the default, pulled customers off-site and was notorious for freezing accounts. Incumbents optimized for enterprise sales, opaque contracts, and slow underwriting.

The approach. Stripe reframed payments as an API problem, not a banking problem, and sold bottom-up to the engineer, not the CFO. Its pitch was literally "seven lines of code": paste a snippet, get instant sandbox keys, and start charging cards the same afternoon, with no sales call and no bank meeting. It abstracted underwriting, PCI compliance, and fraud behind a single clean API.

How it solved it. The incumbents could not follow without cannibalizing their own sales forces and rebuilding legacy tech, the textbook counter-positioning asymmetry. The wedge worked fast: Stripe took Elon Musk, Peter Thiel, and Andreessen Horowitz money in 2011, and by 2023 it processed over $1 trillion in total payment volume, roughly 1% of global GDP, a milestone it hit 15 years after founding versus the 23 years PayPal took.

Platform & Ecosystem: Connect turned Stripe into the rails beneath other platforms

The problem. Payments for a single merchant is one thing, but marketplaces and platforms like ride-hailing apps and grocery-delivery services have to split money across many parties, onboard sellers, handle KYC, and pay out drivers, all across dozens of countries. Building that plumbing in-house is a multi-quarter project and a licensing nightmare.

The approach. Stripe launched Connect, a product that lets a platform embed payments and move money between multiple parties, handling identity verification, compliance, payment splitting, and payouts across 35+ countries. Instead of being a checkout tool for one store, Stripe became the payments engine other companies build their own products on top of.

How it solved it. Shopify, DoorDash, Lyft, and Instacart run their payments on Stripe Connect. When Lyft used Connect to build Express Pay, letting drivers cash out within hours of a ride, over 40% of all Lyft payouts flowed through it within six months. Stripe stopped being a vendor and became infrastructure: the rails beneath other platforms.

Land and Expand: one checkout integration, then a full financial stack

The problem. A payments API alone is a thin, commoditizable slice of a business's needs. To grow revenue per customer and deepen the relationship, Stripe had to sell more than the initial charge-a-card call, without forcing customers through a new integration each time.

The approach. Stripe used the single checkout integration as a beachhead, then expanded the same account into Billing (subscriptions), Radar (fraud), Connect (marketplaces), Atlas (incorporation), Issuing (card creation), Terminal (in-person), and Tax. Each new product reused the existing integration and customer relationship, so adopting the next one was a toggle, not a migration.

How it solved it. The expansion compounded directly into results: Stripe attributed its 2023 growth partly to billing and tax services alongside enterprise adoption, and total payment volume grew again to $1.4 trillion in 2024, up 38%, the year Stripe reported its first profitable year. Cross-selling into the installed base, not just acquiring new logos, drove the second act.

GTM: docs, sandbox keys, and the API as the go-to-market motion

The problem. A developer-first company cannot rely on the enterprise sales playbook of steak dinners and RFPs to reach the individual engineer wiring up a checkout flow. That buyer is skeptical of salespeople, evaluates by trying the product, and rewards clarity over pitch decks.

The approach. Stripe made the product itself the go-to-market motion: obsessively good documentation, instant self-serve API keys, a working sandbox, and a clean developer experience became the funnel. The engineer could evaluate, integrate, and go live before anyone from Stripe ever called, and word spread engineer-to-engineer.

How it solved it. The bottom-up motion let Stripe scale from a Y Combinator startup in 2010 to serving millions of businesses, from early-stage startups to Amazon and Maersk, without a traditional enterprise sales gate at the front door. That reputation for developer experience, not a sales quota, is what made "just use Stripe" the default answer among engineers.

Moats: switching cost as the compounding endgame

The problem. Payment processing is, on the surface, a fungible utility where a competitor can always undercut on basis points. Stripe needed the low-friction wedge to harden into something a customer would not casually rip out for a cheaper rate.

The approach. By pulling billing logic, fraud rules, payout flows, issued cards, and tax handling into one account, Stripe made itself the system of record for a business's money movement. Removing it is no longer swapping a gateway: it is a re-platforming project touching every product that depends on Stripe's APIs.

How it solved it. That embedded depth is the moat behind Stripe's durability: valued at a $95 billion peak in 2021, it dipped to roughly $70 billion in mid-2024, then recovered to $91.5 billion in a February 2025 tender as revenue and volume kept compounding on a sticky, multi-product base. A low-friction wedge, deliberately deepened, became a switching cost competitors cannot dislodge on price alone.