What metrics would you use to evaluate a new Radar feature for enterprise merchants

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 is launching a new Radar feature aimed at enterprise merchants that process high transaction volumes across multiple geographies, payment methods, and business lines. These merchants typically have dedicated fraud, risk, finance, and engineering teams, and they care about reducing fraudulent transactions without blocking legitimate customers or creating operational overhead.

In this metrics interview, you are asked to define how you would evaluate whether the new Radar feature is successful after launch. The feature should be considered in the context of Stripe’s role as a payments and financial infrastructure platform, where fraud prevention, payment authorization, merchant trust, customer conversion, compliance, and reliability are all tightly connected.

Your response should focus on building a measurement framework rather than proposing product changes. Consider how enterprise merchants adopt, configure, and rely on fraud tooling; how Stripe can attribute outcomes to the new feature; and how to balance fraud reduction with merchant revenue growth and customer experience.

The experience should consider:

- The primary success metric and why it reflects value for enterprise merchants and Stripe

- Clear metric definitions, including numerator, denominator, time window, and eligible transaction population

- Adoption and usage metrics for enterprise teams, such as activation, configuration, and ongoing engagement

- Fraud and risk outcome metrics, including how to distinguish prevented fraud from false positives

- Conversion and revenue guardrails to ensure legitimate payments are not being harmed

- Instrumentation requirements across payment attempts, risk decisions, rules, disputes, chargebacks, reviews, and merchant actions

- Cohort cuts by merchant size, industry, geography, payment method, integration type, and feature exposure

- Decision usefulness, including how the metrics would inform rollout, iteration, merchant communication, or rollback

The goal is to present a practical metrics framework that helps Stripe determine whether the new Radar feature creates measurable value for enterprise merchants while preserving payment reliability, customer conversion, and trust in Stripe’s fraud prevention platform.