Stripe and Advent Just Bid for PayPal. When Your Payment Layer Gets Acquired, You're Along for the Ride.
Reuters broke it on July 15: Stripe and Advent Capital have jointly bid for PayPal, estimated valuation $40–50B, deal in negotiation. PayPal's board is reviewing it. If it closes (and venture-backed firms acquiring public payments companies is table-stakes now), Stripe just consolidated what used to be a competitive market into something closer to a monopoly. And if you're a solo operator running a Stripe checkout, you didn't get a vote.
What happens when your vendor absorbs its competitor
PayPal and Stripe aren't identical. Stripe is heavy on developer integration (API-first). PayPal is heavy on merchant direct-to-consumer (buttons, hosted checkout). Their customer segments mostly don't overlap. But they're both in payments.
If Stripe acquires PayPal, it inherits:
- ~30 million users on PayPal's merchant network
- PayPal's direct-to-customer brand and button integrations
- PayPal's enterprise relationships (you can't remove PayPal from a Fortune 500 checkout without board approval at a lot of companies)
- A decade of compliance and regulatory parity on both sides of the Atlantic
From a pure market concentration standpoint, this is huge. Stripe already has ~50% developer market share. PayPal has ~40% of small-merchant checkouts. Together, they're the only two payment processors most indie developers evaluate. The other ~10% is Square, Adyen, Wise, and a bunch of vertical specialists.
After the acquisition, Stripe isn't a choice. It's a default. That changes your negotiating position from "I can switch to PayPal if you raise rates" to "I can switch to... nobody."
What actually changes for you
Pricing. Stripe's current rate is 2.9% + $0.30 per transaction for most SMBs. PayPal's is similar (~2.9% + $0.30 on direct payments). Once PayPal is a Stripe subsidiary, there's no competitive pressure on that rate. Stripe could hold steady, or they could raise to 3.2% after a year and face no churn risk in the SMB segment. Enterprise customers have pricing power to push back. SMBs don't.
Integration surface. Stripe's API is the standard for developers. PayPal's button code is the standard for no-code/low-code. Combining them means you don't get to choose. You get one integrated API that serves both developer and merchant templates. That's maybe more convenient, or it might mean the developer API gets compromised to serve merchant needs. We won't know until it ships.
Merchant support. Stripe's merchant support is historically sparse (you get a dashboard and a knowledge base). PayPal's is heavier (phone support, dispute handling, relationship management). After acquisition, Stripe will probably rationalize that to one support model. If it's PayPal's model, you get better support. If it's Stripe's, PayPal merchants lose it.
Regulatory requirements. PayPal has different compliance obligations in different regions (Germany, UK, Australia all have specific regulations). Stripe has its own. Merging those two risk profiles requires either running two parallel compliance stacks or rationalizing down to the higher bar. The higher bar is more expensive.
Your exit. If you built a company on Stripe and now want to sell it, acquirers will ask: "how do you handle Stripe churn if they raise rates?" After the acquisition, the honest answer is "we can't." That's a technical risk factor that lowers your valuation.
The honest read: why this might be fine
Stripe + Advent paying $40–50B for PayPal isn't an irrational deal. PayPal generates ~$25B annual payment volume. At a 2% cut for the acquirer, that's $500M in annual gross revenue. A 2–3 year payback on $50B is realistic if they can consolidate costs and nudge rates up 20–30 basis points over time.
The competitive check is that this deal probably doesn't face massive regulatory scrutiny. Antitrust authorities in the US and EU have been more aggressive on tech M&A in the last three years, but payments concentration is historically less of a priority than, say, search or social. That said, $50B+ bids for publicly traded companies do draw comment. Expect congress to ask questions.
If you're paranoid, the counter-argument is real: one company owning two-thirds of indie checkout means one architectural decision, one rate decision, one outage risk. But Stripe's infrastructure is genuinely reliable. Being hosted by Stripe beats self-hosting Adyen or rolling your own processor. Consolidation isn't always bad.
What I'd actually do
First, diversify your checkout layer. If you're 100% Stripe, move 10–20% of volume to another processor (Adyen, Wise, even PayPal directly if you're still supporting it before the acquisition). It's not about switching immediately. It's about proving you can switch if you need to. That takes 3–4 months and requires testing.
Second, look at your contract. If you're on Stripe's standard terms, you're not locked in. If you're enterprise (which is rare for solo operators), you might have an MFN clause or a rate-lock. Check whether the acquisition changes anything.
Third, know your effective rate. Stripe 2.9% + $0.30 isn't the only cost. There's chargeback liability, interchange pass-through, and fraud prevention. Your effective rate is probably 3.2–3.5%. That's your baseline for comparison. When Stripe raises rates, know what the break-even point is for migrating.
Fourth, don't panic. The acquisition probably closes in 2027 or later. You have time to prepare your checkout layer for alternatives. Most of that time, the integration surface and pricing likely stays stable while the deal closes and integrates. Use that time to get comfortable with option B.
Author
Lukas
@lukcombinator