How would you detect unhealthy growth in Treasury

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 Treasury enables startups and platforms to embed financial accounts, store funds, move money, and manage cash flows through Stripe’s infrastructure. In this metrics interview, you are asked to define how you would detect “unhealthy growth” in Treasury: growth that looks positive at the top line but may be driven by risky, low-quality, unsustainable, non-compliant, or operationally burdensome usage.

Assume Treasury is growing among startups with varying business models, funding stages, geographies, and financial maturity. Some customers may be legitimate high-potential businesses, while others may create elevated fraud, compliance, liquidity, support, or reliability risk. Your task is to frame what healthy versus unhealthy growth means for this product and how Stripe should measure it before it becomes a systemic issue.

You should focus on metric design and diagnostic structure rather than proposing a product roadmap. Consider how Stripe would distinguish durable merchant value and responsible financial activity from vanity growth, risky account behavior, poor retention, or growth that increases losses and operational load faster than revenue or strategic value.

The experience should consider:

- Clear definitions of growth units, such as active Treasury accounts, balances, transaction volume, money movement, revenue, retained customers, or platform-level adoption.

- Denominators and normalization, including per-account, per-cohort, per-dollar-volume, per-segment, and per-risk-tier views.

- Cohorts by startup stage, industry, geography, acquisition channel, platform partner, onboarding path, and time since activation.

- Instrumentation needed across onboarding, KYC/KYB, account funding, transfers, card or payment activity, disputes, freezes, support contacts, and account closures.

- Guardrail metrics for fraud losses, compliance review rates, failed transfers, negative balances, unusual velocity, support burden, regulatory escalations, and customer concentration.

- Signals that separate healthy engagement from risky or low-quality usage, including retention, balance stability, transaction legitimacy, repeat behavior, and downstream merchant success.

- Decision usefulness: what thresholds, alerts, dashboards, or reviews would help teams decide whether to investigate, slow growth, adjust controls, or continue scaling.

The goal is to show how you would build a rigorous metrics framework for detecting when Treasury’s growth is becoming unsafe or unsustainable, while preserving Stripe’s ability to support high-quality startups and long-term financial infrastructure growth.