Stripe · Metrics · Mid · 45 to 60 minutes
Should Stripe localize subscription prices?
Stripe provides online payments, billing, and financial infrastructure for businesses. Answer this product management case and get it graded line by line against a weighted rubric.
- Metric design
- Experimentation
- Tradeoff analysis
- Payments intuition
- Decision making
The situation
Stripe's Checkout and Billing teams are considering adding automatic local currency pricing for subscription signups and renewals. Today many subscription businesses sell globally in one default currency, which can create mental math for buyers, expose merchants to cross border payment issues, and lead to effective charges that feel unpredictable when exchange rates move. Subscriptions make this harder than one time purchases because customers care about what they will be charged every billing cycle, and finance teams care about FX handling, reporting, and failed renewals. The head of Optimized Checkout asks you to define how Stripe should evaluate whether this capability is creating enough value to justify a broader rollout. Assume Stripe can instrument checkout sessions, payment authorization outcomes, subscription starts, and renewal activity for the first three months after signup across a large global traffic base. Your job is not to design the pricing system itself. Your job is to propose the metrics, experiment, and launch criteria Stripe should use to decide whether localized subscription pricing is worth scaling.
What to produce
Write a 1 to 2 page metrics and experiment memo.
Your answer must
- State the product decision to be made and define success at both the checkout session level and the subscription level.
- Provide a metric tree with one primary metric, 3 to 5 supporting metrics, and 2 guardrails that cover signup and the first three months after signup.
- Describe an experiment or quasi experiment design, including control strategy, unit of randomization, measurement window, and how you would interpret results across markets.
- Explain how you would isolate effects on conversion, payment authorization, and downstream renewal behavior instead of treating all revenue change as one blended outcome.
- Recommend segmentation and clear rollout thresholds, including what findings would support broad launch, limited launch, or more iteration.
Constraints
- Renewal amounts should feel stable to subscribers even when exchange rates move.
- Stripe cannot depend on merchants manually maintaining localized price lists market by market.
- The initial decision must be made using data from signup through the first three months, not full multi year lifetime.
- The approach must work across many countries where cross border authorization rates differ.
Format
Use five sections: decision, metric tree, experiment design, segments and guardrails, launch recommendation.
How Stripe actually played it
Stripe analyzed 1.5 million subscription checkout sessions to see how localized pricing affects subscriptions, noting that 80 percent of subscription transactions in 2025 were still priced in the default currency. It reports gains at signup and a 5.4 percent increase in lifetime value per session. A useful look at measuring pricing changes beyond first conversion.
- Track downstream value (LTV) for pricing changes, not only signup.
- Localized prices remove friction and FX risk for buyers.
- Large session counts allow cleaner pricing conclusions.
Built from Testing the impact of Adaptive Pricing across 1.5M subscription checkout sessions by Stripe.
Related case studies
- Deprecating a legacy Stripe payments APIStripe · Execution · Senior
- Where should Stripe place its next growth bet?Stripe · Strategy · Mid
- How should Stripe launch its payments API?Stripe · Go-to-market · Senior
- Should Stripe show BNPL at checkout?Stripe · Metrics · Mid
- How should Stripe measure payment method impact?Stripe · Metrics · Senior
- How should Stripe support AI pricing models?Stripe · Strategy · Mid