Revenue from Checkout is flat despite user growth. Diagnose the root causes

Problem Statement Description

Product context: Stripe is financial infrastructure for internet businesses; its products include payments, Checkout, Billing, Connect, Radar, Issuing, Terminal, and tax tools.

Stripe Checkout is seeing growth in the number of users or merchants using the product, but total revenue from Checkout has remained flat. You are asked to diagnose what could be driving this mismatch and how you would structure the investigation.

Assume Checkout is used by SaaS companies to accept payments for subscriptions, upgrades, renewals, and one-time purchases across different geographies, payment methods, and customer segments. Revenue may be influenced by checkout conversion, transaction volume, average order value, pricing, payment success, refunds, fraud controls, churn, merchant mix, and competitive or market dynamics.

Your task is not to jump to a fix, but to frame the anomaly clearly, identify the most important cuts of data, validate whether the issue is real, and develop a prioritized set of hypotheses that could explain why user growth is not translating into revenue growth.

The experience should consider:

- How “user growth” and “Checkout revenue” should be defined, including numerator, denominator, time window, and whether the trend is gross or net revenue.

- Segmentation by merchant type, SaaS company size, geography, currency, payment method, acquisition channel, integration type, and new versus existing merchants.

- Funnel diagnostics across Checkout sessions, payment attempts, authorization rates, completed payments, subscription starts, renewals, refunds, disputes, and chargebacks.

- Instrumentation checks to rule out logging gaps, delayed revenue recognition, reporting changes, pricing changes, or attribution shifts between Stripe products.

- Hypotheses around merchant mix, lower transaction volume per merchant, lower average contract value, failed payments, increased discounts, churn, or migration to competing payment flows.

- External and platform factors such as macro pressure on SaaS spend, regulatory changes, card network behavior, fraud controls, payment method availability, or competitor activity.

- How to distinguish short-term noise from a sustained business issue using cohorts, historical baselines, seasonality, and comparable control segments.

- What evidence would determine the highest-priority root cause and what immediate mitigations or follow-up investigations would be appropriate.

The goal is to demonstrate a structured RCA approach suitable for a Stripe product environment: precise metric framing, rigorous segmentation, careful validation of data quality, clear hypothesis prioritization, and a path from diagnosis to action without prematurely prescribing a solution.