The hero addresses "every business model" — startups, enterprises, platforms, SaaS, marketplaces, in-person retail — and the body follows suit with dedicated sections for each segment, none of which resolve into a primary path. A founder evaluating Stripe for the first time, a platform engineer embedding payments into a vertical SaaS product, and a Fortune 100 CFO exploring infrastructure migration all land on the same page and receive the same undifferentiated invitation to "Start now." Stripe has the brand weight to survive this; a competitor reading this page does not. The structural fix is not to cut segments but to add a routing layer — a brief segment selector above the fold (startup / platform / enterprise) that sends each buyer to a tailored path, rather than asking every buyer to self-identify through six scrolling sections.

The first proof surface the visitor encounters is "50% of Fortune 100 companies have used Stripe" — a claim so broad it reads as marketing language rather than evidence. The named, specific proof (Hertz unifying commerce across 11,000 locations, URBN consolidating $5 billion in revenue, Hargreaves Lansdown reducing failed payments by £540 million) appears only after the visitor has already scrolled past the hero, the subheadline, and the product grid. The testimonials with named roles — Laura Collinson at Jobber, Seth McMillan at Substack, Dax Dasilva at Lightspeed — are buried further still. Move one named case study with a specific outcome number directly under the hero; the aggregate claim ("50% of Fortune 100") can stay, but it needs a named anchor beside it or it reads as a placeholder.

API-first infrastructure, enterprise uptime, startup-friendly onboarding, agentic commerce, stablecoin support, embedded platform monetization, and no-code tools for non-developers all appear as headline-level claims within the same scroll. Each of these is a defensible position against a specific competitor — API-first against PayPal, embedded platform tools against Adyen, startup onboarding against Checkout.com — but the page never commits to one. The result is that a buyer who came to evaluate Stripe against a specific alternative leaves without a clear reason to choose Stripe over that alternative. Pick the one axis Stripe wins most decisively for the primary ICP (platform engineers building embedded payments) and make every section on the page defend that axis; move the secondary claims to segment-specific pages where they can be argued fully.

"Monetise through agentic commerce" and "Access borderless money movement with stablecoins and crypto" appear in the same product grid as Payments and Billing — products with $1.9 trillion in volume and 200 million subscriptions behind them. The agentic and stablecoin sections have no customer names, no volume numbers, no case studies. A buyer evaluating these capabilities reads a feature description next to a scale claim that doesn't apply to it, which either inflates the expectation or deflates the credibility of the scale claims nearby. Either add a named early adopter and a specific outcome to each emerging product section, or move them to a separate "what's next" surface and stop asking them to carry the same weight as proven infrastructure.