Stripe’s PayPal Bet Would Trade Focus for Scale

A Stripe–PayPal combination is financially conceivable only if Stripe can preserve PayPal’s distribution and cash generation while radically rebuilding its cost base and infrastructure. That is the appeal in Jason Calacanis’s version of the idea—and the condition that makes Alex Wilhelm doubt Stripe should pursue it at all.

The Wall Street Journal reported that Stripe had considered a bid for PayPal, describing the work as a preliminary evaluation rather than an advancing transaction. The reported facts are thin, but the premise is unusually large: a private payments company with an indicated valuation of roughly $70 billion evaluating a public rival with an enterprise value of about $85 billion.

Wilhelm treats the possibility less as evidence of an imminent deal than as a marker of a changing hierarchy in payments. PayPal was acquired by eBay for roughly $1.5 billion in 2002, returned to public markets in 2015, climbed dramatically during the pandemic, and then declined. Stripe, meanwhile, has become the ascendant company in the comparison. The two are now close enough in implied value for a merger discussion to be imaginable, even though PayPal remains larger by payment volume, employee count, and operating cash flow.

The revenue row is particularly easy to overread. PayPal’s $29.8 billion figure is net revenue; Stripe’s roughly $30 billion is estimated gross revenue. Wilhelm notes that Stripe’s financial numbers are murky, and the superficially similar figures are not equivalent revenue measures.

Calacanis calls the valuation proximity a “Pac-Man scenario”: a smaller private company combines with a larger public one, while the smaller company’s leaders run the resulting business. Stripe could use the transaction as an unconventional route into public markets, rather than completing an independent IPO.

The central economic attraction is PayPal’s cash flow. The displayed comparison assigns PayPal $4.8 billion in 2023 operating cash flow, compared with more than $1 billion for Stripe. Calacanis pairs that cash generation with Stripe’s faster growth and technical reputation. If the combined business could eliminate large parts of PayPal’s operating expense, he argues, it could become a much more valuable public company.

Calacanis starts with PayPal’s roughly 27,200 employees and speculates that a merger could eliminate overlapping systems, support, sales, and administrative functions. He briefly assumes an average burdened cost of $150,000 per employee, then uses a lower $100,000-per-employee calculation to arrive at $2.7 billion of potential payroll savings. His most aggressive version imagines roughly $2.5 trillion in combined payment volume operating on one technical foundation, with about 1,000 people running the back end.

Wilhelm agrees that PayPal’s cash flow makes it the kind of mature public technology company that private equity could examine. He expects financial buyers with substantial dry powder to seek out stale or operationally underperforming public companies, naming PayPal and Twilio as examples. But that is a case for an owner willing to “shake out” a mature company. It is not necessarily a case for the faster-growing competitor to buy it.

The real question is whether PayPal’s volume, consumer reach, and cash flow can be separated from the older systems and larger organization that currently produce them.

Wilhelm’s case for why Stripe might want PayPal begins with distribution. Stripe has the stronger brand among engineers choosing payments tools, he says, while PayPal remains a default checkout button in many places because it had decades more time to establish itself. PayPal would bring consumer reach through Venmo, basic PayPal transfers, consumer attention and float, as well as a large installed enterprise payments base.

That is the asset Calacanis wants Stripe to obtain: payment relationships that PayPal has built over time, combined with Stripe’s developer-oriented technology. In the favorable version of the transaction, Stripe would become the infrastructure behind a much larger installed base of merchants and consumers.

But Alex Wilhelm argues that the company cannot simply acquire the valuable exterior while leaving behind the operating burden. In his description, PayPal runs on old technology. Combining it with Stripe would be like taking “a backpack full of rocks” off one company and putting it on Secretariat—the faster company would inherit the weight of the one it is outcompeting.

Jason Calacanis does not dispute the premise that PayPal is older, larger, and technologically cumbersome. His answer is to avoid a conventional integration. Stripe would not need to transform tens of thousands of PayPal employees into Stripe employees, he argues. Instead, a small group of engineers from each company could map PayPal’s API endpoints, create compatible endpoints that route activity into Stripe’s infrastructure, and gradually retire PayPal servers.

In that model, legacy PayPal applications could remain customer-facing while the underlying transaction processing progressively moves into Stripe’s systems. The front ends and the customer relationships would stay in place; the routing layer would change underneath them. Calacanis imagines Stripe taking 50 engineers, pairing them with 50 people at the top of PayPal’s technical organization, and constructing a compatibility layer that directs existing PayPal instances to Stripe’s infrastructure.

The claimed savings therefore require more than corporate consolidation. They depend on a staged migration that preserves the payment flows giving PayPal its value while moving the underlying work to a different technical stack. The scale is substantial: the chart shown during the discussion lists $1.53 trillion in 2023 payment volume for PayPal and $1 trillion for Stripe.

Calacanis regards that migration as a potentially elegant engineering problem for people who enjoy “untying the knot.” He also acknowledges Wilhelm’s central objection. Even if it is technically possible to move the volume, Stripe would be putting the burden of a massive legacy business onto the company that has succeeded by staying fast, focused, and product-led.

The discussion produces two different financing theories, and they lead to different ownership structures.

Jason Calacanis first explores whether PayPal’s own cash flow could support a highly leveraged acquisition. In that version, Stripe, a private-equity partner such as Silver Lake or Apollo, and perhaps another investor would contribute equity while debt finances much of the purchase. Calacanis throws out possible equity contributions of $5 billion or $10 billion and considers borrowing $40 billion or $50 billion, before recognizing the difficulty of applying conventional leveraged-buyout logic at PayPal’s scale.

Alex Wilhelm puts the size in context. PayPal’s roughly $85 billion enterprise value would likely be a floor rather than a final purchase price, because shareholders would ordinarily require a premium. A take-private deal could therefore approach $100 billion or $105 billion. Twitter’s $44 billion sale, Wilhelm notes, was roughly half that size and “broke the internet for like a year.”

PayPal’s $4.8 billion in operating cash flow makes debt part of a conceivable financing discussion, but it does not make an $85 billion-plus take-private straightforward. The burden is especially large because the acquisition case also assumes a difficult technical integration and cost-reduction program. The buyer would be counting on a business’s future cash generation while simultaneously undertaking the work that is supposed to improve it.

Calacanis then shifts toward a different structure: a share swap. If Stripe and PayPal are close enough in value, Stripe could exchange equity with PayPal holders and form a larger public company rather than deliver the full purchase price in cash. He describes, illustratively, a merged entity worth roughly the sum of the two indicated values—about $155 billion—before any acquisition premium or claimed synergies.

That structure changes the immediate financing burden. It does not make PayPal free. As Wilhelm points out, in a simplified equal-value merger Stripe would have to give PayPal shareholders a substantial stake in the combined company—roughly half. Stripe holders would receive a public-market vehicle and ownership in a larger payments platform, but they would own only part of it and would inherit the integration required to justify the combination.

Calacanis’s preferred outcome is a public company with a consolidated technical stack, far fewer PayPal employees, and sharply higher cash generation. He imagines PayPal’s cash flow rising toward $7.5 billion if half its workforce could be cut, and Stripe adding another $1 billion or $2 billion as it grows. That could create what he calls a roughly $10 billion cash-flow company.

The share-swap logic makes the merger easier to picture than a full cash acquisition. It does not solve the basic bargain: Stripe shareholders would trade some ownership in a focused, rapidly growing company for ownership in a much larger platform whose value depends on restructuring an older rival.

Wilhelm’s objection is ultimately strategic rather than merely financial or technical. Stripe, in his account, is already winning by executing its existing plan: building good code, selling a broader suite of enterprise products, and maintaining a developer-friendly model that can win customers from the bottom up. He says Stripe is beating competitors such as Adyen because it has more to sell to enterprise customers.

A PayPal deal would redirect that company toward a multiyear integration, a legacy technology estate, and an organization nearly four times Stripe’s displayed headcount. The problem is not simply that integration would be difficult. Wilhelm argues that focus is itself a central part of Stripe’s present value.

Wilhelm’s alternative is more conventional: Stripe could go public independently, potentially gain value in public markets, and continue taking market share from PayPal over time. If Stripe’s product breadth, infrastructure, and execution are already enough to win customers, it can capture distribution without taking responsibility for PayPal’s systems and workforce.

Jason Calacanis ultimately accepts the force of that objection even as he remains drawn to the scale of the hypothetical. He sees an alluring combination: PayPal’s distribution and cash flow, Stripe’s infrastructure, major cost reductions, and a rapid route to becoming a large public company. Yet he returns to the same image Wilhelm uses against the deal: why put all that weight on the company already moving faster?

Wilhelm invokes AOL–Time Warner as a warning about how a celebrated merger can become a durable symbol of strategic error; Calacanis calls it the worst deal in history. Wilhelm also recalls Yahoo and AOL discussing a defensive combination during Microsoft’s pursuit of Yahoo in 2008. Neither analogy is a direct model for payments. Both point to the risk that complicated mergers develop their own internal logic even when the stronger company is not the one in need of rescue.

Stripe is not presented as a distressed business seeking transformation. It is the faster-moving competitor. That makes the financial cleverness of the merger less decisive than the operating cost: Stripe could keep compounding its focused model, or it could become the consolidator responsible for rebuilding the legacy platform it has been beating.