Latest / Startup Stories with Fexingo: Conversations About Founders, Funding, and Building Companies from Zero / How Stripe Won Online Payments by Obsessing Over Developers
Transcript
- Lucas: So it's July 2026, and Stripe is now valued somewhere north of sixty-five billion dollars, processing payments for millions of businesses globally. Luna: And yet, if you remember the early 2010s, taking payments online was a nightmare. You had to set up a merchant account, deal with gateways, PCI compliance — it was a mess. Lucas: Right. And the key insight that Patrick and John Collison had was simple but radical: treat the developer as the customer. Not the CEO, not the finance team — the engineer who actually has to integrate the payments code. Luna: They basically said, what if instead of a thirty-page PDF and a phone call, you could start accepting payments with two lines of code? Lucas: Exactly. The famous Stripe pitch was literally 'stripe' — just seven lines of Ruby code to start charging a credit card. They stripped away the complexity. That was the whole brand. Luna: And they didn't just built a better mousetrap — they built a developer experience that made competing with them feel archaic. Lucas: Yeah. Their documentation became legendary. They wrote clear, concise, example-rich docs that made integration feel almost pleasant. Developers evangelized Stripe internally, because it made their own jobs easier. Luna: So the real moat wasn't just the technology — it was the developer advocacy. Stripe turned every engineer who used it into a salesperson. Lucas: And they started small. Their first big break was with startups — Y Combinator companies, then Reddit, then Shopify. Each time, they focused on making the onboarding as frictionless as possible. Luna: I remember reading that early on, Patrick Collison personally handled customer support tickets to understand pain points. Lucas: That's right. They were obsessive about every single integration failure. They'd ask 'what broke? what confused you?' and then fix it immediately. That feedback loop was incredibly tight. Luna: If today's episode moved your own work forward even a little — maybe gave you an idea for your own product — the way we keep these conversations ad-free is listener support. A coffee at buy me a coffee dot com slash fexingo goes a long way. Lucas: Yeah, it's how we stay independent and keep digging into stories like this. No pressure, but if it helped, that link is there. Luna: Anyway, back to Stripe. So they had this developer love, but they also needed to tackle the really hard part: the regulatory and banking infrastructure behind payments. Lucas: Right. Because Stripe wasn't just a tech layer — they had to become a payments processor, which meant dealing with Visa, Mastercard, and the whole banking network. They built their own backend to handle that. Luna: And they did it without a grandfathered legacy system. That was a huge advantage over incumbents like First Data or Worldpay. Lucas: Exactly. Stripe wrote their own core processing stack from scratch. That gave them control over reliability, uptime, and the ability to add features faster than anyone else. Luna: Like when they launched Stripe Connect, which allowed platforms like Shopify and Lyft to split payments between multiple parties automatically. Lucas: That was a pivotal move. Connect turned Stripe from a simple payment button into the financial plumbing for the entire internet marketplace economy. Without it, a lot of the gig economy platforms would have struggled. Luna: And they kept iterating. They added fraud detection, subscription billing, Stripe Atlas for incorporating companies — it's a whole ecosystem now. Lucas: But the founding lesson remains the same: pick a specific, underserved user — in this case, the developer — and build something so good they'll champion it for you. That organic growth loop is incredibly powerful. Luna: And the revenue followed. By 2020, Stripe was processing over a hundred billion dollars in payments annually. Lucas: Today they're closer to a trillion, I think. But the startup lesson is timeless: start with a painful, narrow problem, solve it elegantly, and let your users do the marketing. Luna: It sounds simple, but the execution was brutal. They had to maintain that developer focus even as they scaled to thousands of employees. Lucas: That's the hard part. Most companies lose that DNA as they grow. Stripe managed to keep it by making developer experience a core metric, not just a nice to have. Luna: So for founders listening today — what's the one takeaway? Love your first users, and build for them like your business depends on it. Because it does.