Estimate the annual addressable market for Radar among platform businesses

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.

Estimate the annual addressable market for Stripe Radar among platform businesses: companies that enable many underlying merchants, sellers, service providers, or creators to accept payments through a platform model. Radar is Stripe’s fraud prevention and risk management product, so the estimate should focus on the revenue opportunity from helping these platforms reduce fraudulent transactions while preserving legitimate conversion.

This is a guesstimate exercise, not a request for exact market data. You should define the market boundary, choose a clear unit of analysis, and build a structured estimate using reasonable assumptions about platform count, payment volume, fraud-risk exposure, pricing model, and likely adoption. The scope should be specific to platform businesses rather than all Stripe merchants or all online payments.

The estimate should consider:

- Which platform business types are in scope, such as marketplaces, SaaS platforms with payments, creator platforms, delivery platforms, booking platforms, or payment facilitators.

- The relevant unit of estimation, such as annual processed payment volume, number of platforms, number of connected merchants, transaction volume, or Radar revenue per dollar processed.

- How to segment platforms by size, geography, risk profile, vertical, and payment complexity.

- Assumptions about fraud exposure, chargeback risk, and why platforms may value dedicated fraud tooling.

- Expected adoption among eligible platforms, including Stripe-native platforms versus platforms using other payment providers.

- Potential pricing logic for Radar, such as per-transaction fees, basis points on processed volume, bundled pricing, or enterprise contracts.

- Sensitivity of the estimate to key assumptions like platform payment volume, attach rate, pricing, and fraud-risk intensity.

- Sanity checks against broader payments, fraud prevention, and platform-commerce market constraints.

The goal is to produce a clear, defensible annual market-size estimate with transparent assumptions, reasonable ranges, and an explanation of the biggest drivers of uncertainty.