How Stripe sold seven lines of code and became the internet's toll booth

• Card networks and banks — the rails beneath the rails
• Platform customers (Shopify, Amazon, Salla-likes) embedding Stripe
• Local payment methods worldwide (wallets, bank debits, BNPL)
• Regulators and licensing regimes in dozens of countries
• The developer ecosystem building libraries and integrations

Why it mattersStripe's biggest 'customers' are also distribution partners: when a platform like Shopify embeds Stripe under its own payments product, Stripe earns on millions of merchants it never acquired. Being the infrastructure inside other people's products is the highest-leverage partnership shape in software — invisible, sticky, and volume-linked.

• Abstracting global payment complexity behind one API
• Writing documentation as a first-class product
• Fighting fraud at network scale (Radar)
• Bank and regulator integrations, country by country
• Expanding the suite: Billing, Connect, Issuing, Treasury, Atlas

Why it mattersNote what's ranked second: documentation. Stripe treated docs as product, not afterthought — famously the best in the industry — because its buyer reads before he buys. Every activity list should over-invest in whatever your actual decision-maker touches first; for developer tools, that's the docs, not the sales deck.

• The API and its accumulated abstraction depth
• Fraud data across $1.4T of annual volume
• Licenses and bank relationships in dozens of countries
• The developer brand — 'just use Stripe' as reflex

Why it mattersRadar's fraud models see patterns across the whole network — a card testing attack on one merchant instantly protects a million others. That's a resource only scale can build and only the leader really has. Regulatory licenses are the second moat: years of paperwork per country that a challenger must serially repeat. Data network effects plus regulatory grind — the deepest infra moat combination there is.

• Developers: accept payments in an afternoon, not a quarter
• Businesses: one integration = every payment method, every country
• Platforms: Connect turns marketplaces into payment facilitators
• Everyone: fraud, compliance, and bank plumbing handled invisibly

Why it mattersThe original pitch — seven lines of code — compressed months of bank negotiations and PCI compliance into an afternoon. Stripe sells time and abstraction, not transactions. When your product removes an entire category of dread, price is barely negotiated; nobody haggles hard with the thing that saved their quarter.

• Self-serve: sign up, get API keys, charge a card in minutes
• Docs, changelogs, and status pages as the relationship surface
• Usage-based billing — the relationship deepens with volume
• Enterprise teams for the largest accounts (added late, deliberately)

Why it mattersStripe grew for years with essentially no sales force: the developer integrates, the product proves itself on real revenue, and switching costs assemble themselves — payment flows are the last thing anyone rips out. Self-serve plus usage pricing means the customer's growth is the account expansion. Sales came later, to harvest what the product had already won.

• Documentation and SEO — developers arrive mid-search
• Default status in accelerators, tutorials, and boilerplates
• Platform embeds carrying Stripe to millions of merchants
• Word of mouth in engineering teams

Why it mattersStripe's channel is the moment a developer googles 'how to accept payments' — and finds docs so good they double as the tutorial. Content that answers the buying-trigger question IS the sales funnel for technical products. (Your teardown pages are the same play: be the best answer at the moment of intent.)