The Rise of a New Challenger
To understand the story, you have to go back to the late 2000s and early 2010s. PayPal, born from the dot-com boom and battle-hardened by its early years, was the undisputed champion of digital payments. If you wanted to send money or accept payments online without a traditional merchant account, PayPal was the default. It was a consumer-facing brand, a trusted button on millions of websites. But a new wave of internet business was emerging. This new web was driven by apps, platforms, and marketplaces that needed payments to be a seamless, integrated part of their code—not just a button that sent customers to another website. Into this gap stepped Stripe, founded in 2010 by Irish brothers Patrick and John Collison. It wasn't for everyone; it was for developers.
Its tagline, "payments for developers," was a direct shot across PayPal's bow, signaling a completely different approach.
A Fundamental Clash of Philosophies
Here lies the “hidden reason,” and it’s more of a cultural chasm than a secret memo. PayPal was built as a product for end-users. It's a destination, a digital wallet with a login and a balance. Its ecosystem is largely self-contained. For years, its goal was to get more users and more merchants to use the PayPal button. Stripe was built on a radically different philosophy. It wasn't a product for people; it was a tool for builders. Stripe’s customers weren’t everyday shoppers but the engineers at companies like Lyft, Kickstarter, and Shopify. It offered a powerful, flexible set of APIs (Application Programming Interfaces) that allowed developers to build custom payment flows directly into their own products. You've likely used Stripe hundreds of times without ever seeing its name. This philosophy made Stripe invisible infrastructure, while PayPal remained a visible brand. An acquisition would have been like trying to merge a car company with an engine component factory—they both deal with transport, but their DNA is fundamentally different.
The Problem of Price and Pride
Of course, there were practical barriers. By the time Stripe became a clear and present threat to PayPal's dominance in the new app economy, it was already a Silicon Valley darling with a sky-high valuation. Acquiring it would have required a monumental, eye-watering check. For a large, publicly-traded company like PayPal, justifying such an expense for a company with a completely different business model would have been a tough sell to shareholders. Furthermore, Stripe was—and is—a founder-led company with a clear, ambitious vision. The Collison brothers weren’t looking for a quick exit; they were aiming to “increase the GDP of the internet.” Founders with that level of ambition and control rarely sell to an incumbent, especially when doing so would mean subsuming their developer-first culture into a larger, more consumer-focused bureaucracy. The pride of building an industry-defining company often outweighs the allure of a buyout.
The Innovator's Dilemma in Action
Ultimately, PayPal’s situation is a textbook example of the “Innovator’s Dilemma.” The theory, coined by Clayton Christensen, describes how successful, well-managed companies can fail by doing everything right. PayPal was busy optimizing its massive, profitable business. It improved its consumer app, expanded internationally, and made smart acquisitions that fit its model, like Braintree and Venmo. Buying Venmo, a peer-to-peer payment app, made perfect sense for a consumer-facing company. But truly embracing the Stripe model would have meant disrupting its own core business. It would have required a massive internal shift to prioritize developers over consumers and infrastructure over a branded product. For a market leader, that kind of self-disruption is incredibly difficult. It was easier and safer for PayPal to continue building on its existing strengths than to absorb a competitor whose very success was a critique of PayPal's own foundational strategy.
