Estimate the revenue opportunity if Stripe improves Issuing adoption by 10%

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 wants to understand the revenue opportunity from increasing adoption of Stripe Issuing by 10% among international sellers. Issuing enables businesses to create and manage payment cards for use cases such as employee spend, marketplace payouts, vendor payments, logistics, advertising spend, or creator/contractor disbursements. The estimate should focus on incremental revenue potential for Stripe, not just incremental cardholders or transaction volume.

Frame this as a guesstimate for a PM interview: define the relevant seller population, identify which portion is eligible and likely to use Issuing, estimate the incremental adoption implied by a 10% improvement, and translate usage into Stripe revenue. Consider that international sellers may operate across currencies, markets, compliance regimes, and payout workflows, and that adoption may vary significantly by business model, geography, and payment volume.

You should make explicit assumptions, choose reasonable units, and show how changes in key assumptions would affect the answer. The goal is not to find a precise public number, but to build a structured, defensible estimate that could help Stripe decide whether improving Issuing adoption is a meaningful business opportunity.

The experience should consider:

- Scope: whether “10% adoption improvement” means a relative lift in current Issuing adoption or a 10 percentage-point increase.

- Target population: international sellers using Stripe, segmented by size, geography, business model, and card-issuing relevance.

- Eligibility and adoption: which sellers have workflows where virtual or physical cards solve a real operational problem.

- Usage model: expected number of cards, spend per seller, transaction frequency, and cross-border or currency effects.

- Revenue model: interchange, platform fees, FX, card issuance fees, SaaS-like controls, or other monetization assumptions.

- Sensitivity: which assumptions most drive the estimate, such as seller count, average card spend, take rate, and adoption baseline.

- Sanity checks: compare the implied card volume and revenue to plausible seller GMV, payment volume, and competitive benchmarks.

- Constraints: compliance, fraud risk, treasury requirements, issuer partnerships, and geographic availability.

Your goal is to produce a clear revenue opportunity estimate with transparent assumptions, a logical calculation path, and a short discussion of confidence level, upside/downside scenarios, and what data Stripe should validate before making a product or investment decision.