Stripe reports that its services power more than 5 million businesses, directly or through platforms. Stripe, 2025 annual letter
Protocol reading: interpretation, not a fact
Constraint (Q1)The integration that lives in customers' own code and operations — payment APIs, billing logic and account data.
Gate 1 · withdrawalRouting around Stripe means rewriting live payment code and migrating billing and customer data; the core is not cheaply obtainable elsewhere.
Gate 2 · captureStripe controls the integration layer and keeps its economics. The card rails beneath it belong to the networks and issuers — a real dependency, but one every rival pays on the same terms: a commodity input, not the decisive constraint.
Flashlight (Q4)DarkThe parties upstream — card networks and banks — are not positioned to ship Stripe's developer integration to Stripe's customers.
Decisive objectDeepen the embedded integration; watch the enterprise end, where large merchants can route volume across several processors.
What would overturn this reading
Reclassify if a network or acquiring bank ships an equivalent integration directly to Stripe's developers, or if multi-processor routing becomes normal lower in the market.
The founder's Monday
Find the highest-value segment where the switching constraint is weakest, and close that leak before chasing surface growth.
Want this reading, with its evidence gaps and the observations that would change it, for a company you are assessing? The Reading Report applies the same protocol to your answers and evidence. See a sample.