Stripe's Infrastructure Moat

The Thesis

Stripe is not primarily a payments company. It's an infrastructure company that happens to route money. The distinction matters enormously for how you think about its defensibility, its moat, and its long-run trajectory.

The payments layer is commoditized and price-sensitive. The infrastructure layer — the developer tooling, the compliance stack, the fraud systems, the financial primitive APIs — is where compounding occurs.

Business Model

Stripe charges a percentage of transaction volume (2.9% + 30¢ for standard processing). But that's the beginning, not the end. The real model is layering higher-margin products onto that volume relationship:

• Radar (fraud detection): priced per transaction
• Billing (subscription management): priced per active subscription
• Connect (marketplace payments): priced on volume
• Treasury (financial accounts): interest income + fees
• Atlas (incorporation): one-time fee

Each additional product increases switching costs. A company using Stripe for payments, Billing, and Radar has deeply integrated Stripe into its financial operations. That's not a vendor relationship — it's infrastructure dependency.

Unit Economics

The core payment product is low-margin but high-volume. Stripe's reported gross margin trajectory suggests the business mix is shifting toward software products, which carry 70–80%+ gross margins.

Key metrics to watch:

• Revenue per active user (increasing as product attach rates grow)
• Take rate on total payment volume (relatively stable; not the growth driver)
• Software revenue as % of total (the real indicator of mix improvement)

Competitive Position

Three structural advantages compound over time.

1. Developer distribution. Stripe's initial moat was superior developer experience. This created a flywheel: developers chose Stripe for new projects, those projects scaled, large companies ended up on Stripe because developers brought it in. Now Stripe has enterprise relationships it didn't have to sell enterprise-first to acquire.

2. Fraud data. Radar processes transactions across millions of merchants. The fraud pattern data that accumulates from this volume is an asymmetric advantage — a new entrant cannot replicate years of cross-merchant signal.

3. Compliance infrastructure. Global payments requires navigating hundreds of regulatory regimes. Stripe has built this once and amortizes it across its merchant base. The cost to build from scratch is prohibitive; the cost to maintain at Stripe is spread across volume.

Risks

• Margin compression from enterprise competition. Large merchants have pricing leverage. JPMC, Adyen, and Braintree all compete for volume contracts.
• Regulatory exposure. Any major compliance failure in any single jurisdiction is a reputational event.
• Concentration risk. A non-trivial amount of GMV runs through a small number of large platform companies.
• Disintermediation from networks. Card networks could theoretically unbundle Stripe's value if they moved down-stack. Unlikely but not impossible.

Verdict

Stripe's public market story, when it comes, will be told as a payments company. The right frame is an infrastructure business with embedded distribution in a large and growing market. The switching costs are real, the data advantages compound, and the product expansion path is credible.

The valuation question is distinct from the business quality question — and the business quality is high.