Stripe — What I Think
The most underrated sentence in fintech: accepting money on the internet was a developer problem, not a banking problem.
Before Stripe, taking a card online meant a merchant account, a gateway, a processor, a week of paperwork, and a contract with a bank that assumed you were a fraud risk by default. Stripe looked at that mess and saw the thing everyone in payments had stopped seeing because they were too close to it. The actual work, the thing a person sat down to do, was integrate a payment. Seven lines of code. They built for the person at the keyboard, not the person in the procurement meeting. That one decision is the entire company.
The contrarian bit is that in software, the buyer is the builder. Win the engineer, win the company, because the engineer ships the thing and the thing becomes load-bearing and now you’re infrastructure. Stripe optimized docs the way Visa optimized dispute resolution: as the actual product. I’ve integrated a lot of payment systems. The difference between good docs and bad docs is the difference between a Tuesday and a quarter. Stripe priced that difference correctly when nobody else thought it had a price.
Where I think they’re right and underappreciated: Stripe treats money movement as a programmable surface, not a service you call. Billing, Connect, Issuing, Treasury, Atlas. Each one is “what if this annoying financial primitive were just an API.” That’s the correct mental model for the next twenty years. The economy is being rewritten as software, and software wants money to behave like every other dependency. Importable. Composable. Testable.
Where I’d push: Stripe is, underneath, a beautiful abstraction over the same card and bank rails everyone else uses. The genius is the abstraction. But an abstraction over old plumbing inherits the plumbing’s limits, settlement time, interchange, geographic fragmentation, the bank’s risk appetite. Their stablecoin and on-chain moves are the tell that they know this. The interesting question is whether the company that abstracted away the banks can eventually abstract away the need for them. If anyone ships that, it’s the team that already taught money to behave like code. Or something like that.
Favorite & worst CEO
This is a founder-CEO company, so:
On its leadership. Patrick and John Collison built Stripe on a thesis most payments people couldn’t even parse, that the bottleneck on internet commerce was developer experience, and that taste, in APIs, in docs, in writing, is a moat. They run the company like editors, not operators, and it shows in how coherent the product surface is. The risk in founder-led idealism is over-engineering elegance the market never asked for, and Stripe occasionally drifts there. But of everyone in this series, their mental model of what payments is becoming most resembles mine. Money as a programmable primitive, the developer as the real customer.
Part of “What I Think About the Top 50 Fintech Companies of All Time.” I’m Prajjwal Chittori. prajjwalchittori.com.