Terminal engagement dropped 20% in two weeks among enterprise merchants. Diagnose the issue

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 Terminal enables enterprise merchants to accept in-person payments through connected readers, POS integrations, and Stripe’s payments infrastructure. In this scenario, engagement among enterprise merchants has dropped 20% over the last two weeks, creating concern because this segment often represents high payment volume, complex integrations, and long-term platform relationships.

You are asked to diagnose the decline as a product RCA. Treat “engagement” as a product/business metric that must first be clarified: it could refer to active merchants, active locations, connected readers, successful in-person transactions, payment volume, SDK/API usage, dashboard activity, or another Terminal-specific usage signal. Your task is to structure how you would investigate whether the drop is real, where it is concentrated, what may have caused it, and what actions should follow.

Focus on the workflows of enterprise merchants using Terminal across physical retail locations, field operations, events, or omnichannel checkout environments. Consider the roles involved, such as merchant developers, store associates, payment operations teams, finance teams, and Stripe support/account teams.

The diagnosis should consider:

- How to validate the anomaly, including metric definition, denominator, baseline period, seasonality, and data quality checks.

- Segmentation by merchant size, geography, industry, integration type, SDK/API version, reader model, location, payment method, and onboarding cohort.

- Instrumentation checks across device connectivity, reader activation, transaction attempts, authorization success, error rates, webhook delivery, and dashboard/API events.

- Product and platform hypotheses, such as recent releases, firmware changes, outages, latency, degraded payment acceptance, compliance changes, or onboarding friction.

- Merchant-side hypotheses, including store closures, POS changes, staff behavior, inventory/traffic shifts, contract changes, or migration to another provider.

- External factors such as holidays, macro retail trends, network or acquirer issues, regional regulations, and competitive displacement.

- Evidence needed to prioritize hypotheses, including logs, support tickets, merchant feedback, account manager input, incident timelines, and cohort-level trend analysis.

- Mitigation and prevention paths, including communication, monitoring, alerting, rollback considerations, and longer-term instrumentation improvements.

The goal is to demonstrate a clear, structured RCA approach that separates measurement issues from true user behavior changes, narrows the problem to affected merchant cohorts and workflows, identifies the most likely causes using evidence, and defines practical next steps to protect payment reliability and enterprise merchant trust.