Example report. Demonstration data only. Not a real Stripe account.
Commercial health report
Example workspace
- Environment
- Live
- Stripe account
- acct_e…demo
- Generated
- 2026-08-15T14:02:00.000Z
- Scan window
- 2026-07-16 → 2026-08-15 14:02 UTC
- Coverage
- Complete for requested scope
Commercial Health Score
61/ 100 · Needs attention
This is not an AI score and not a Stripe score. It deducts from 100 using versioned rules on open incidents, money presence, identity, and freshness. Formula version 1.
- −12 critical incident1 critical open incident × 12, cap 36
- −12 high incident2 high open incident(s) × 6, cap 24
- −15 confirmed lossconfirmed loss present in at least one currency
Financial impact
Amounts are shown per currency. Ropely never adds currencies together.
Confirmed loss
- USD1840.00
- EUR420.00
Currently at risk
- USD960.00
Customer exposure
- GBP150.00
Affected customers
23
Top findings
Renewal failure spike
Failed subscription renewals clustered above the recent baseline in the requested window. This is an observation from invoice payment outcomes, not a claim that access was revoked.
- Affected customers
- 11
- Why flagged
- The renewal-failure detector compared recent failed invoices with the prior baseline and the rate crossed the configured delta.
- Next check
- Inspect the failed invoices in Stripe and confirm whether cards expired or payments were retried.
- money lost actual · USD · 1840.00
Possible duplicate subscription
Two active subscriptions share overlapping commercial identity evidence. This is an inference until an operator confirms they belong to one customer.
- Affected customers
- 2
- Why flagged
- Identity projection attached two subscriptions to parties with the same normalized email and no merge decision.
- Next check
- Compare the two subscriptions in Ropely customers, then confirm or reject the identity suggestion.
- customer exposure · GBP · 150.00
Unresolved customer identity
Several Stripe customers in the window have no merchant app-user claim. Ropely cannot see application entitlements from Stripe alone.
- Affected customers
- 8
- Why flagged
- Identity work produced unresolved references because no app-user mapping was supplied.
- Next check
- Add merchant app-user claims later if you need to know who can still access the product.
Stale webhook warning
The latest processed Stripe webhook is older than the freshness window. A one-time scan is not real-time monitoring.
- Affected customers
- 0
- Why flagged
- Webhook silence exceeded the health freshness threshold relative to API observations.
- Next check
- Confirm the Stripe webhook endpoint is still sending events to Ropely.
- revenue at risk · USD · 960.00
- revenue at risk · EUR · 420.00
Data coverage
This report covers the requested bounded window only. It does not claim a full account-wide assessment.
- Customers
- 184
- Subscriptions
- 211
- Invoices
- 392
- Payments
- 401
- Refunds
- 12
- Pages fetched
- 26
- Webhook last seen
- 2026-08-13T09:22:00.000Z
- Truncated resources
- None
Limitations
- This scan covers a bounded window, not the complete commercial history.
- Application access and granted allowance are not visible from a commercial source alone. Add access events or paste an allowance snapshot.
- Merchant application identities are not mapped in this window.
- stale webhook
- Ropely stores the commercial records required to generate and monitor this report according to your workspace retention settings.
Recommended next actions
- Scan your Stripe account with a read-only restricted key.
- Keep monitoring after the first report so new failures are detected.
- Send alerts to Slack or email.
- Add granted allowance with access events or an allowance snapshot. Ropely cannot see granted units from a commercial source alone.