Revenue from Radar is flat despite user growth. Diagnose the root causes

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 Radar helps businesses detect and manage payment fraud while balancing approval rates and customer conversion. You are investigating a situation where Radar’s revenue has remained flat even though the number of users or merchants using Radar has grown, particularly among SaaS companies that rely on recurring payments, subscriptions, trials, and global card acceptance.

Frame this as a root-cause analysis problem. Your task is to clarify what “user growth” and “revenue” mean in this context, validate whether the anomaly is real, and identify where the disconnect may be happening across acquisition, activation, usage, pricing, billing, fraud volume, merchant mix, and retention. Assume the business cares about both direct Radar monetization and the broader Stripe payments ecosystem impact.

You should approach the problem as if you are a PM working with data science, finance, engineering, sales, support, and risk teams. The goal is not to jump to a fix, but to build a structured investigation that can isolate likely causes, distinguish data issues from business issues, and determine what evidence would confirm or reject each hypothesis.

The diagnosis should consider:

- The exact metric definitions for Radar revenue, active Radar users, merchants, accounts, transactions screened, and paid feature usage.

- Whether the flat revenue trend holds across cohorts, regions, merchant size, SaaS subsegments, pricing plans, payment volume tiers, and acquisition channels.

- Instrumentation and billing checks, including event tracking, entitlement logic, invoice generation, discounts, free trials, bundled pricing, and reporting delays.

- Usage-pattern changes, such as lower fraud exposure, fewer chargeable transactions, reduced rule usage, more merchants on free or bundled tiers, or shifts toward lower-volume customers.

- Funnel points from signup to activation to sustained paid usage, including whether new users are integrating Radar but not reaching meaningful monetized usage.

- External or ecosystem factors, such as changes in fraud rates, card network behavior, regulations, competitive pricing pressure, or merchant optimization for authorization rates.

- Evidence needed from dashboards, logs, finance data, customer interviews, support tickets, and sales feedback before concluding root cause.

- Immediate mitigation, communication needs, and prevention mechanisms once the root cause is identified.

Your goal is to present a clear RCA plan that narrows the problem from a broad revenue symptom into testable hypotheses, prioritized analyses, and decision-ready findings for Stripe’s Radar business.