Estimate the number of daily transactions or interactions generated by Connect

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.

You are being asked to estimate the daily volume of transactions or product interactions generated by Stripe Connect, Stripe’s infrastructure for marketplaces and platforms that route payments between buyers, sellers, service providers, creators, and other connected accounts.

Assume the interviewer wants to see how you structure an ambiguous sizing problem in a payments context. “Transactions or interactions” may include marketplace payments, transfers, payouts, refunds, onboarding events, account updates, disputes, or other Connect-related payment lifecycle events, depending on how you define scope. Your first task is to clarify the unit being estimated and then build a defensible bottom-up or top-down estimate.

The estimate should reflect the realities of marketplace businesses: many platforms have uneven transaction frequency, seasonal spikes, varying seller activity, multiple geographies, different payment methods, and payment flows that can generate more than one backend interaction per end-user purchase.

The experience should consider:

- The exact unit of estimation: completed payment transactions, API interactions, account events, money movement events, or total Connect-related platform interactions.

- The relevant population: number of Stripe Connect platforms, active connected accounts, end customers, or marketplace buyers/sellers.

- Marketplace categories to include, such as gig work, e-commerce marketplaces, creator platforms, SaaS platforms, ticketing, delivery, or services marketplaces.

- Adoption and activity assumptions, including active platform share, average transactions per platform, seller activity rates, and daily versus monthly frequency.

- Payment lifecycle multipliers, such as authorizations, captures, transfers, payouts, refunds, disputes, identity checks, and account onboarding interactions.

- Geographic and business-size variation, including enterprise platforms versus long-tail platforms and mature markets versus emerging markets.

- Sensitivity of the estimate to a few key assumptions, especially platform count, average daily transaction volume, and interactions per transaction.

- Sanity checks against broader payments volume, marketplace GMV, and reasonable infrastructure-scale expectations for a company like Stripe.

Your goal is not to know Stripe’s internal numbers, but to produce a clear, logical, and testable estimate with explicit assumptions, reasonable ranges, and a brief explanation of which inputs would most affect the final answer.