Stripe Checkout Metrics: Payment Conversion Funnel, Merchant Adoption and Guardrails

You are a product manager at Stripe, responsible for Checkout: the prebuilt payment page that merchants send their customers to when it is time to pay. Explain how you would measure whether Checkout is successful. ```hint Two customers, one page Checkout serves the shoppers who pay on it and the businesses that choose to use it. Define success for both, then follow a single payment from the moment the page loads to the money reaching the merchant. ``` ### Clarifying Questions - Should success be judged for shoppers paying on the page, for merchants adopting it, for Stripe's revenue, or for all three? - Is this an ongoing health measure for the product, or a measurement plan for a specific change such as a new payment method? - Are the embedded version and the Stripe-hosted page both in scope, and should results be compared with merchants who build their own payment forms? ### What a Strong Answer Covers - Checkout's purpose for shoppers, merchants and Stripe, turned into one goal. - A precisely defined north-star metric, with a decomposition showing which parts the product team can move. - A funnel from page load to successful payment, with metrics at each step and segmentation by payment method, device, country and merchant. - Merchant adoption and retention, plus guardrails such as fraud, disputes, false declines and page speed. ### Follow-up Questions - Checkout's completion rate falls for a week while merchant traffic is steady. How would you find the cause? - Stripe adds a new wallet to Checkout. How would you tell whether it created extra completed payments or only moved shoppers away from cards? - How would you stop a change in the mix of merchants from looking like a change in product quality?