Create a metric dashboard for the executive team reviewing Issuing

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’s executive team is reviewing the health and trajectory of Stripe Issuing, with particular interest in how it serves subscription businesses that may use virtual or physical cards for vendor spend, payouts, employee purchasing, or operational workflows. You are asked to design a metric dashboard that would help leadership quickly understand whether Issuing is growing, reliable, valuable to customers, and aligned with Stripe’s broader payments and financial infrastructure strategy.

The dashboard should be executive-facing, so it needs to separate signal from noise and support decisions about investment, product quality, market focus, and risk. It should account for the fact that Issuing is both a financial product and a developer/platform product: customers care about card creation, authorization performance, spend controls, fraud prevention, reconciliation, compliance, and integration quality.

Your task is not to design the UI in detail, but to define what the dashboard should measure, how the metrics should be structured, and how leadership should interpret them. Be clear about metric definitions, denominators, segments, data sources, and guardrails so the dashboard is useful for decision-making rather than just reporting activity.

The experience should consider:

- The primary executive questions the dashboard must answer about Issuing performance, customer adoption, reliability, revenue, risk, and customer value.

- Clear definitions for core metrics, including what counts in the numerator and denominator and how time windows should be handled.

- Relevant customer cohorts, such as subscription businesses by size, geography, maturity, use case, integration type, or card program type.

- Instrumentation needed across card creation, authorization attempts, transaction outcomes, declines, disputes, fraud events, API usage, and customer support signals.

- Guardrail metrics for financial reliability, compliance, fraud loss, operational burden, user trust, and customer experience.

- How to distinguish between growth driven by new customers, existing customer expansion, higher spend per card, or changes in authorization behavior.

- How the dashboard should surface anomalies, trends, and decision thresholds for executive review.

The goal is to create a concise but decision-useful executive dashboard framework that helps Stripe leadership assess whether Issuing is scaling successfully for subscription businesses, where performance or risk issues may exist, and what areas may require deeper investigation or investment.