Sample report. Northwind Notes is a fictional company and every number below comes from Stripe Leak Check's synthetic demo fixture (stripe-leak-check demo leaky). No real Stripe data. Back to Stripe Leak Check

Stripe Leak Check: Northwind Notes

Generated 2026-10-01 12:00 UTC · 180-day window · mode DEMO (leaky synthetic fixture, not real data) · USD · v0.2.2
10 high-severity leak(s) worth fixing this week.
Disclaimer. Not financial, legal or tax advice. Dollar amounts are estimates built from your own Stripe data plus the assumptions stated next to each one; they overlap and are not a forecast. Card-network thresholds were checked against Stripe's public docs on 2026-10-02 and can change. Confirm anything important with Stripe or your advisor.
0CRITICAL
10HIGH
5MEDIUM
1LOW
0PASS
$27,260est. at risk*

* Sum of per-finding estimates. They overlap and mix one-off and annualised figures; read each basis below.

Summary

SeverityCheckWhat we foundEst. at risk
HIGHInvoluntary churn (cancelled for failed payment)14 subscriptions ($256.49/mo) were cancelled because payment failed, 70% of all cancellations in the window.$3,078
HIGHPayouts, holds and account requirementsVerification requirements due by 2026-10-10: individual.verification.document; plus 2 more.$2,260
HIGHFailed invoice payments and retries11 invoice(s) with $1,406 outstanding are failed or overdue, and automatic retries appear to be off.$1,976
HIGHDispute rate vs card-network thresholdsDispute activity is 0.68% over 90 days. At least one recent month crossed a threshold that card networks or Stripe act on.$1,132
HIGHWebhook deliveries that haven't landed23 events from the last 30 days still haven't been delivered to at least one endpoint, including 16 payment events worth $544.00.$544.00
HIGHEarly fraud warnings you can still refund4 payments have an actionable early fraud warning and are not refunded or disputed yet.$387.00
HIGHAccess vs subscription status (never revoked, cut too early, or not entitled)Failed payments probably never cost a customer access: no endpoint listens for customer.subscription.updated or invoice.payment_failed, and 3 subscriptions ($57.00/mo) are stuck in unpaid/past_due; plus 1 more.$171.00
HIGHCard-testing signalsFound 1 burst(s) of failed charges (220 failures) consistent with card testing; 1 customer(s) cycling through cards.$112.00
HIGHDisputes waiting for your response4 open disputes have no evidence submitted. If the deadline passes, you lose them automatically.$76.00
HIGHWebhook endpoint setupwe_a68j9zBlMVFFkJ005125 (http://old.northwind-notes.example/hooks/stripe) is DISABLED. Stripe stops sending to it, so nothing it handled is happening; plus 2 more.–
MEDIUMRefund rateRefunds are 9.98% of gross volume over 90 days.$15,928
MEDIUMCustomers without an email address47 subscribed customers ($854.96/mo) can't receive receipts, failed-payment or card-expiring emails.$854.96
MEDIUMPast-due and unpaid subscriptions9 subscriptions ($171.00/mo, 3.1% of MRR) are behind on payment.$513.00
MEDIUMCards expiring in the next 60 days12 subscriptions ($228.00/mo) are on cards that expire within 60 days.$228.00
MEDIUMRadar rules and listsNo evidence of custom Radar rules. You're relying on Stripe's default rules only, while this report found fraud or dispute signals.–
LOWStatement descriptor and support detailsPublic details that help customers recognise your charges are incomplete.–

Findings

HIGH Involuntary churn (cancelled for failed payment) INVOLUNTARY_CHURN

14 subscriptions ($256.49/mo) were cancelled because payment failed, 70% of all cancellations in the window.

Estimated at risk: $3,078. Estimate: lost MRR × 12, assuming these customers would otherwise have stayed a year. Treat it as an upper bound.
Evidence How to fix
  1. These customers didn't choose to leave. Email them a reactivation link.
  2. Turn on Smart Retries and failed-payment emails, and consider a longer retry window before cancelling.
  3. Enable card-expiring reminders so cards get updated before the renewal fails.
Reconcile checklist
  • Look up: Each subscription in the table below (cancelled with reason payment_failed), and whether your app removed access when it was cancelled.
  • Fix: Send a reactivation link to the customers you want back, and turn on retries plus failed-payment and expiring-card emails so fewer reach cancellation.
  • Confirm: Each row's app access should be off, or on a new paid subscription. Re-run in 30 days and compare the number of payment_failed cancellations.
Subscription / customerStripe statusLast successful paymentEntitlement to check in your app
sub_GolAGMm4KL6r6U001504
cus_QVRBLyz05etI2I001501
canceled2026-09-21, $19.00Off, unless the customer is on a new paid subscription
sub_CQiLoAZPdtlnON001509
cus_7m5nbLSz3FK6GD001506
canceled2026-09-20, $49.00Off, unless the customer is on a new paid subscription
sub_i16KZBHxUd1bQ1001514
cus_yKBvDN4pDEAT0q001511
canceled2026-09-08, $19.00Off, unless the customer is on a new paid subscription
sub_rKU0UP4aNGH05m001519
cus_oRGBhYQpGScrkF001516
canceled2026-09-03, $49.00Off, unless the customer is on a new paid subscription
sub_1bQ3pt5l2F5UmM001524
cus_5mT2zmNDt1djFg001521
canceled2026-09-05, $19.00Off, unless the customer is on a new paid subscription
sub_aqdLmWJAsSxvPu001529
cus_qOTm55f6VYQX6X001526
canceled2026-09-10, $19.00Off, unless the customer is on a new paid subscription
sub_0Mk5oQo1uKpoky001534
cus_8wK8lsdbBSvy0B001531
canceled2026-08-16, $190.00Off, unless the customer is on a new paid subscription
sub_Yhgl9PKDO3nsbu001539
cus_QaO3i5qEtxYm8B001536
canceled2026-07-07, $99.00Off, unless the customer is on a new paid subscription
sub_fcAuJISnmb0hMY001544
cus_zKShNS3UIKe9kE001541
canceled2026-09-02, $19.00Off, unless the customer is on a new paid subscription
sub_UHfz2a6fDol3Vm001549
cus_ZfMNr45WHXPMVN001546
canceled2026-09-04, $19.00Off, unless the customer is on a new paid subscription

Stripe side only. The scan can't read your app's entitlements, so the last column is what to look up there; a row is a confirmed leak only if your app disagrees with it.

Stripe docs: Automate payment retries (Smart Retries) · Automate customer emails · Revenue recovery

Object IDs to look at: sub_GolAGMm4KL6r6U001504, sub_CQiLoAZPdtlnON001509, sub_i16KZBHxUd1bQ1001514, sub_rKU0UP4aNGH05m001519, sub_1bQ3pt5l2F5UmM001524, sub_aqdLmWJAsSxvPu001529, sub_0Mk5oQo1uKpoky001534, sub_Yhgl9PKDO3nsbu001539, sub_fcAuJISnmb0hMY001544, sub_UHfz2a6fDol3Vm001549

HIGH Payouts, holds and account requirements PAYOUTS

Verification requirements due by 2026-10-10: individual.verification.document; plus 2 more.

Estimated at risk: $2,260. Money delayed rather than lost: failed/canceled payouts plus pending balance if it looks held.
Evidence How to fix
  1. Clear any requirements in Settings > Business > Account status before the deadline.
  2. For failed payouts, check the bank account details in Settings > Payouts.
  3. If payouts are delayed and you didn't change the schedule, contact Stripe support and ask whether a reserve or review applies.
  4. Reserves aren't fully visible to a restricted key; check Balances in the Dashboard.
Reconcile checklist
  • Look up: Settings > Business > Account status (requirements and deadlines), Settings > Payouts (bank account), the payout IDs below, and Balances for reserves, which a restricted key can't fully read.
  • Fix: Clear requirements before the deadline, fix the bank details, and ask Stripe support about any payout delay you didn't choose.
  • Confirm: Re-run the scan: this check passes when payouts and charges are enabled, nothing is due, and no payout in the window failed or was cancelled.

Stripe docs: Payouts

Object IDs to look at: po_girAhHK0BfDqFw005174

HIGH Failed invoice payments and retries FAILED_INVOICES

11 invoice(s) with $1,406 outstanding are failed or overdue, and automatic retries appear to be off.

Estimated at risk: $1,976. Amounts outstanding on open failed/overdue invoices plus those written off as uncollectible in the window. Not all of it is recoverable.
Evidence How to fix
  1. Turn on Smart Retries: Billing > Revenue recovery > Retries (https://dashboard.stripe.com/revenue_recovery/retries). Stripe's recommended default is 8 tries within 2 weeks.
  2. Turn on failed-payment emails with a link to update the card (Billing > Revenue recovery > Emails: https://dashboard.stripe.com/revenue_recovery/emails).
  3. Decide what happens after the last retry (cancel, mark unpaid, or leave past_due) on purpose, not by default.
  4. Retry settings aren't readable through the API; confirm them in the Dashboard.
Reconcile checklist
  • Look up: Each invoice ID below: attempt_count, next_payment_attempt and amount_remaining in Stripe, and in your database whether that customer still has access while it's unpaid.
  • Fix: Turn on Smart Retries and failed-payment emails (Dashboard-only settings), and chase emailed invoices past their due date.
  • Confirm: Re-run the scan: paid invoices leave the open list, and the ones still failing should show a next_payment_attempt. Confirm the retry schedule by hand in Billing > Revenue recovery > Retries; the key can't read it.

Stripe docs: Automate payment retries (Smart Retries) · Automate customer emails · Revenue recovery

Object IDs to look at: in_Uy6WZDYop0A4TI005110, in_gQcnHe5Rp4wQzA005111, in_ziZiDzBZXNCzqX005112, in_ffmoBuDsssnLwt005113, in_CAzYOjPVtblAjm005114, in_JSRKib2LCoOlBJ005115, in_OxI6Pv9JOQ2GrJ005116, in_XBc65yWTAeCqAK005117, in_iKOHpgWyH5lgnj005118, in_RvBDiuvu6aWdfX005119

HIGH Dispute rate vs card-network thresholds DISPUTE_RATE

Dispute activity is 0.68% over 90 days. At least one recent month crossed a threshold that card networks or Stripe act on.

Estimated at risk: $1,132. Estimate: last 90 days' disputed amounts not won ($144.00) plus $15.00 fee per dispute, annualised at the current pace.
Evidence How to fix
  1. Check your standing on the VAMP dashboard (Radar > Card network monitoring): https://dashboard.stripe.com/radar/cbmp/vamp
  2. Make the charge recognisable: a clear statement descriptor and a support URL/email on your public details.
  3. Refund actionable early fraud warnings before they become disputes (see the EFW finding).
  4. Turn on Stripe's dispute prevention (Visa Order Insights / RDR, Mastercard Ethoca alerts) if your volume justifies the per-alert fee.
  5. For 'fraudulent' disputes, add Radar rules (block CVC failures, 3DS for high-risk payments).
  6. For 'product_not_received' / 'subscription_canceled', send renewal reminders and make cancelling easy.
Reconcile checklist
  • Look up: The disputes listed below in Payments > Disputes, and for each one the order behind its charge in your database: what was sold and whether it was delivered or used.
  • Fix: Refund fraud before it becomes a dispute (see the early-fraud-warning finding) and make the charge recognisable on a card statement (see the descriptor finding).
  • Confirm: Re-run the scan after the month closes: that month's disputes per charge for each card brand should sit under the lines in the thresholds table. Stripe's VAMP view in the Dashboard is the authoritative ratio.

Stripe docs: Dispute and fraud monitoring programs · Measuring disputes · Preventing disputes and fraud

Object IDs to look at: dp_ZRTet5Fr6o1KuO004856, dp_vc62sKrxAbIvZ2004857, dp_0AQhjxZzQaIitF004858, dp_F75jCRgnJemIAK004859, dp_jdFwmqm3uoZUtb004860, dp_SVQb5IxlnMphmP004861, dp_feAWEsnpso2n7Y004862, dp_zP7WGWmV4xsKoS004863, dp_6EHFOorbJRv1Dr004864

HIGH Webhook deliveries that haven't landed WEBHOOK_DELIVERY

23 events from the last 30 days still haven't been delivered to at least one endpoint, including 16 payment events worth $544.00.

Estimated at risk: $544.00. Payment amounts on events your app may never have processed (orders not fulfilled, upgrades not granted, cancellations not applied). Some may have been handled another way.
Evidence How to fix
  1. Open Developers > Webhooks > your endpoint > Event deliveries and read the error.
  2. Fix the handler (return 2xx quickly, do work async), then resend or process the missed events.
  3. Reconcile: check that every paid Checkout Session or invoice in this list got fulfilled.
Reconcile checklist
  • Look up: Each event ID below, the object it carries (Checkout Session, invoice, payment), and whether your database has the matching order, upgrade or cancellation.
  • Fix: Fix the handler, resend or process the missed events, and fulfil anything missing by hand.
  • Confirm: Re-run the scan: those events stop showing as undelivered, and every paid object in this list has a matching fulfilment row in your database.

Stripe docs: Process undelivered webhook events · Webhooks

Object IDs to look at: evt_BbBlVKCRzMX9E5005126, evt_Sj3F9jjt9lMrTM005127, evt_kkMWxcbOdvYEBI005128, evt_XgoSp6lDlyc2wv005129, evt_rchN0HtjSsDVEM005130, evt_NGMfuFNqd1yxYX005131, evt_DUkr2FFHLeFviy005132, evt_e65bVqZWL56LPy005133, evt_Um124XGzZr3h5Y005134, evt_N9xHJH7c0YjT4O005135

HIGH Early fraud warnings you can still refund EFW_UNREFUNDED

4 payments have an actionable early fraud warning and are not refunded or disputed yet.

Estimated at risk: $387.00. Estimate: if each becomes a dispute you lose the payment plus the dispute fee. Refunding now loses the payment but avoids the fee and the dispute count.
Evidence How to fix
  1. Review each payment. If it looks fraudulent, refund it now (Payments > select payment > Refund).
  2. Consider a Radar rule or list entry for the card fingerprint or email involved.
Reconcile checklist
  • Look up: Each warning ID below and the charge it names, then in your database whether that order was delivered or used, and by which account.
  • Fix: Refund the payments you can't stand behind (Payments > the payment > Refund) and add the card fingerprint or email to a Radar block list.
  • Confirm: Re-run the scan: a refunded or disputed payment drops off this finding, so what's left should be only the warnings you decided to keep.

Stripe docs: Early fraud warnings · Radar lists

Object IDs to look at: issfr_06NaU3OUEZ3cM8004865, issfr_JDgbG4U1uFF7p4004866, issfr_WM9OMC8MyYio3s004867, issfr_2gaKlzQk8JQ1ol004868

HIGH Access vs subscription status (never revoked, cut too early, or not entitled) ACCESS_LIFECYCLE

Failed payments probably never cost a customer access: no endpoint listens for customer.subscription.updated or invoice.payment_failed, and 3 subscriptions ($57.00/mo) are stuck in unpaid/past_due; plus 1 more.

Estimated at risk: $171.00. Per month: MRR of the 9 past_due/unpaid subscriptions ($171.00), service you may be providing without payment. It overlaps with the past-due finding. Also includes non-entitled statuses beyond past_due/unpaid when present.
Evidence How to fix
  1. Subscribe to customer.subscription.updated and drive access from subscription.status: active or trialing = access; past_due = keep access while retries run and show an 'update your card' banner; paused, unpaid, canceled, incomplete or incomplete_expired = revoke.
  2. Or set Billing > Revenue recovery > Retries > 'If all retries for a payment fail' to cancel the subscription, so customer.subscription.deleted does arrive (https://dashboard.stripe.com/revenue_recovery/retries).
  3. Reconcile today: for each subscription listed here, check whether your app still grants access.
  4. Reconcile your entitlement table against every subscription that is not active or trialing (paused, pause_collection, unpaid, past_due with retries finished, incomplete, and any new status Stripe adds later).
  5. Treat status=paused and pause_collection as revoke (or a deliberate free-access hold you can name). Listen for customer.subscription.paused / .updated, not only .deleted.
  6. For past_due, keep access only while a retry is still scheduled (next_payment_attempt); revoke when retries are finished or status becomes unpaid.
Reconcile checklist
  • Look up: Each subscription in the table below, then the entitlement your app keeps for that customer (plan flag, role or access-until date). The scan can't see that table; this is the join it can't do.
  • Fix: Where the two disagree, correct the app side first (turn access off, or back on for a customer cut early), then change the webhook handler as listed under How to fix so it doesn't drift again.
  • Confirm: Every row should match its "Entitlement to check" column. Then prove the handler in test mode: renew a subscription on card 4000 0000 0000 0341 (it attaches, then fails) and watch your app's flag follow the status through past_due to unpaid or canceled.
Subscription / customerStripe statusLast successful paymentEntitlement to check in your app
sub_rhhhz4iILo3ojQ000234
cus_CGbHZIibp9foNl000231
unpaid2026-08-26, $19.00Off (unpaid: Stripe stopped retrying)
sub_7DOcZ44cc3PNr6000239
cus_1MHcz8dXxvzp1v000236
unpaid2026-09-26, $19.00Off (unpaid: Stripe stopped retrying)
sub_xD5JtNEE0tbpvo000244
cus_Bp8cshtwPkhdM9000241
unpaid2026-09-06, $49.00Off (unpaid: Stripe stopped retrying)
sub_JdED5jSFpFkIM3000179
cus_qMgLj2olXCwYjn000176
paused2026-09-28, $19.00Off (paused), unless it's a hold you chose and can name
sub_sw0FzvGr3GwnPF000184
cus_BA9RelOxOPbbNc000181
active, pause_collection: mark_uncollectible2026-09-20, $190.00Off (paused), unless it's a hold you chose and can name
sub_n7qLWaYyDIfIZw000204
cus_oZCsSauqrBkL60000201
past_due2026-09-25, $19.00Off, unless a retry is still scheduled (no open invoice with a next retry was found)
sub_g8CXL0M9iq1cvm000209
cus_LmmnmflZSsxKKw000206
past_due2026-09-04, $99.00Off, unless a retry is still scheduled (no open invoice with a next retry was found)
sub_EdgjuWa8mRVtLL000214
cus_65e3MOz7hT9fqu000211
past_due2026-08-03, $19.00Off, unless a retry is still scheduled (no open invoice with a next retry was found)
sub_J4jC3jrAApjbrK000219
cus_CpZj6R5aDT6mZc000216
past_due2026-09-01, $49.00Off, unless a retry is still scheduled (no open invoice with a next retry was found)
sub_c6AnrKli1lHXoT000224
cus_GdO5YQ7nJE1shq000221
past_due2026-09-03, $19.00Off, unless a retry is still scheduled (no open invoice with a next retry was found)

Stripe side only. The scan can't read your app's entitlements, so the last column is what to look up there; a row is a confirmed leak only if your app disagrees with it.

Stripe docs: Using webhooks with subscriptions · Subscription statuses · Automate payment retries (Smart Retries) · Pause a subscription · Pause payment collection

Object IDs to look at: sub_rhhhz4iILo3ojQ000234, sub_7DOcZ44cc3PNr6000239, sub_xD5JtNEE0tbpvo000244, sub_JdED5jSFpFkIM3000179, sub_sw0FzvGr3GwnPF000184, sub_n7qLWaYyDIfIZw000204, sub_g8CXL0M9iq1cvm000209, sub_EdgjuWa8mRVtLL000214, sub_J4jC3jrAApjbrK000219, sub_c6AnrKli1lHXoT000224

HIGH Card-testing signals CARD_TESTING

Found 1 burst(s) of failed charges (220 failures) consistent with card testing; 1 customer(s) cycling through cards.

Estimated at risk: $112.00. Estimate: 7 small charges that succeeded during bursts (likely stolen cards that will be disputed) plus a dispute fee each. Not counted: higher decline rates for your real customers, which card testing can cause.
Evidence How to fix
  1. Refund the small successful charges from the burst windows before they turn into disputes.
  2. Use Checkout or the Payment Element (Stripe's built-in card-testing defences apply there).
  3. Add a CAPTCHA and rate limiting to any endpoint that creates PaymentIntents or SetupIntents.
  4. Add Radar rules, for example block if :card_count_for_customer_daily: > 3, or require 3DS on small amounts.
  5. Make sure your secret key hasn't leaked; roll it if in doubt.
Reconcile checklist
  • Look up: The burst windows and charge IDs in the evidence, then in your logs which sessions or accounts created payments in those hours, and which small charges succeeded during them.
  • Fix: Refund the small successful charges from the bursts, then add rate limiting, a CAPTCHA and Radar rules as listed under How to fix.
  • Confirm: Re-run the scan a week later: no new hour should reach 15+ failed charges at 5× your usual hourly failures, and no customer or email should show 5+ different failed cards.

Stripe docs: Card testing · Radar rules

Object IDs to look at: ch_9dMvVoFfFh643P004819, ch_hYzWZJ19V3fyPa004797, ch_i2sg3XqwltbpOR004633

HIGH Disputes waiting for your response DISPUTES_UNANSWERED

4 open disputes have no evidence submitted. If the deadline passes, you lose them automatically.

Estimated at risk: $76.00. The disputed amounts, which you lose by default if you don't respond (the dispute fee is charged either way).
Evidence How to fix
  1. Open each dispute in the Dashboard (Payments > Disputes) and submit evidence before the due date.
  2. Include proof of delivery or usage, your refund policy, and customer communication.
  3. If the claim is valid, accept it to close it quickly.
Reconcile checklist
  • Look up: Each dispute ID below and its evidence due date (in the evidence list), then the order in your database: what was bought, delivery or login/usage records, and any messages with the customer.
  • Fix: Submit that evidence in Payments > Disputes before the due date, or accept the dispute if the claim is valid.
  • Confirm: Re-run the scan: a dispute with evidence submitted is no longer needs_response, so it drops off this finding.

Stripe docs: Responding to disputes

Object IDs to look at: dp_F75jCRgnJemIAK004859, dp_jdFwmqm3uoZUtb004860, dp_SVQb5IxlnMphmP004861, dp_feAWEsnpso2n7Y004862

HIGH Webhook endpoint setup WEBHOOK_CONFIG

we_a68j9zBlMVFFkJ005125 (http://old.northwind-notes.example/hooks/stripe) is DISABLED. Stripe stops sending to it, so nothing it handled is happening; plus 2 more.

Evidence How to fix
  1. Re-enable or delete disabled endpoints (Developers > Webhooks). Fix the handler first, or it will be disabled again.
  2. Use HTTPS endpoints only.
  3. Subscribe to invoice.payment_failed, invoice.paid, customer.subscription.updated/deleted and charge.dispute.created.
  4. Verify signatures on every event.
Reconcile checklist
  • Look up: Developers > Webhooks: each endpoint's status, URL scheme and event list, and in your code which handler serves that URL.
  • Fix: Fix the handler, then re-enable or delete disabled endpoints, switch to https://, and add the missing events.
  • Confirm: Re-run the scan: this check passes when every endpoint is enabled, on HTTPS and covers the events listed. Send a test event from the Dashboard and check your handler logged it.

Stripe docs: Webhooks · Using webhooks with subscriptions

Object IDs to look at: we_a68j9zBlMVFFkJ005125

MEDIUM Refund rate REFUND_RATE

Refunds are 9.98% of gross volume over 90 days.

Estimated at risk: $15,928. Estimate: refunds above 5% of gross ($3,677) plus unreturned processing fees on all refunds (assumed 2.9% + 30¢, US standard pricing; about $250.78), annualised. Some refunds are healthy; they're cheaper than disputes.
Evidence How to fix
  1. Read the refund reasons and the products involved; fix the top cause (expectations, onboarding, billing surprise).
  2. Send renewal reminders before annual charges.
  3. Keep refunding instead of letting disputes happen; just make refunds rarer.
Reconcile checklist
  • Look up: The refund IDs below, their reasons, and in your database which product or plan each refund was for.
  • Fix: Fix the top cause (expectations, onboarding, a renewal surprise) and send reminders before annual renewals.
  • Confirm: Re-run the scan next month: refunds over the trailing 90 days should be under 5% of gross, the line this check uses.

Stripe docs: Refunds

Object IDs to look at: re_ubAY8z3710CE5a004982, re_4UhHWH7pPWJmFs004985, re_Z5j2rEPFbJGg1I004987, re_OVQ3sJMV0928Qg004989, re_u5iOTVuOhJKKi0004990, re_hiqoRpQyxCT1dp004991, re_AIb2T2ADIM4TIu004992, re_jtfqe8AC7Xo0zz004993, re_pEeDhjv7HgO5RK004994, re_36rblq35tTn4G3004995

MEDIUM Customers without an email address MISSING_EMAILS

47 subscribed customers ($854.96/mo) can't receive receipts, failed-payment or card-expiring emails.

Estimated at risk: $854.96. MRR on subscriptions where dunning emails can't reach anyone. It's at risk only if their payment fails.
Evidence How to fix
  1. Collect email at checkout (Checkout does this by default) and backfill it on existing customers.
  2. Turn on successful-payment and refund receipts in Settings > Customer emails (https://dashboard.stripe.com/settings/emails).
  3. Unrecognised charges become disputes; a receipt is a cheap way to be recognised.
Reconcile checklist
  • Look up: Each subscription below and its customer in your own database; you may have the email even though Stripe doesn't.
  • Fix: Backfill the email on the Stripe customer (Customers > the customer > Edit) and collect email at checkout from now on.
  • Confirm: Re-run the scan: a subscription drops off once its customer has an email.

Stripe docs: Receipts and paid invoices · Automate customer emails

Object IDs to look at: sub_xNKu8iS2G8NPRV000014, sub_1SkHbn88HxjSI6000019, sub_GMGmSrCGIZEG8p000034, sub_xvCkgafrfwA94h000089, sub_Gx5diFoNPcbdaK000129, sub_ZZdPaRXLujTpwr000264, sub_YunX6wV6fASVzV000284, sub_z9MNfZZdURvMQt000304, sub_celN0PRMz1E9kS000319, sub_ewn294oUerTlaq000354

MEDIUM Past-due and unpaid subscriptions PAST_DUE_SUBS

9 subscriptions ($171.00/mo, 3.1% of MRR) are behind on payment.

Estimated at risk: $513.00. Estimate: three months of their MRR, a rough value of keeping them versus losing them.
Evidence How to fix
  1. Email these customers a link to update their payment method (the Customer portal works).
  2. Make sure retries and failed-payment emails are on (see the failed-invoice finding).
  3. For 'unpaid' subscriptions, decide whether to cancel or keep providing service.
Reconcile checklist
  • Look up: Each subscription in the table below: Stripe status and last successful payment, then the access flag your app keeps for that customer.
  • Fix: Send each customer a card-update link (the Customer portal works). For unpaid ones, decide whether to cancel or keep serving, and set the app's access flag to match.
  • Confirm: Re-run the scan: subscriptions that paid return to active and drop off. For the rest, your app's flag should match the "Entitlement to check" column.
Subscription / customerStripe statusLast successful paymentEntitlement to check in your app
sub_n7qLWaYyDIfIZw000204
cus_oZCsSauqrBkL60000201
past_due2026-09-25, $19.00Off, unless a retry is still scheduled (no open invoice with a next retry was found)
sub_g8CXL0M9iq1cvm000209
cus_LmmnmflZSsxKKw000206
past_due2026-09-04, $99.00Off, unless a retry is still scheduled (no open invoice with a next retry was found)
sub_EdgjuWa8mRVtLL000214
cus_65e3MOz7hT9fqu000211
past_due2026-08-03, $19.00Off, unless a retry is still scheduled (no open invoice with a next retry was found)
sub_J4jC3jrAApjbrK000219
cus_CpZj6R5aDT6mZc000216
past_due2026-09-01, $49.00Off, unless a retry is still scheduled (no open invoice with a next retry was found)
sub_c6AnrKli1lHXoT000224
cus_GdO5YQ7nJE1shq000221
past_due2026-09-03, $19.00Off, unless a retry is still scheduled (no open invoice with a next retry was found)
sub_7C9HehwTp0136u000229
cus_iNQTOZmLtmaeSU000226
past_due2026-09-26, $19.00Off, unless a retry is still scheduled (no open invoice with a next retry was found)
sub_rhhhz4iILo3ojQ000234
cus_CGbHZIibp9foNl000231
unpaid2026-08-26, $19.00Off (unpaid: Stripe stopped retrying)
sub_7DOcZ44cc3PNr6000239
cus_1MHcz8dXxvzp1v000236
unpaid2026-09-26, $19.00Off (unpaid: Stripe stopped retrying)
sub_xD5JtNEE0tbpvo000244
cus_Bp8cshtwPkhdM9000241
unpaid2026-09-06, $49.00Off (unpaid: Stripe stopped retrying)

Stripe side only. The scan can't read your app's entitlements, so the last column is what to look up there; a row is a confirmed leak only if your app disagrees with it.

Stripe docs: Subscription statuses · Automate customer emails

Object IDs to look at: sub_n7qLWaYyDIfIZw000204, sub_g8CXL0M9iq1cvm000209, sub_EdgjuWa8mRVtLL000214, sub_J4jC3jrAApjbrK000219, sub_c6AnrKli1lHXoT000224, sub_7C9HehwTp0136u000229, sub_rhhhz4iILo3ojQ000234, sub_7DOcZ44cc3PNr6000239, sub_xD5JtNEE0tbpvo000244

MEDIUM Cards expiring in the next 60 days EXPIRING_CARDS

12 subscriptions ($228.00/mo) are on cards that expire within 60 days.

Estimated at risk: $228.00. Upper bound: one month of MRR on these subscriptions. Stripe's automatic card updates refresh many US cards on their own, so the real loss is usually lower.
Evidence How to fix
  1. Turn on expiring-card emails in Billing > Revenue recovery > Emails (https://dashboard.stripe.com/revenue_recovery/emails). It's Dashboard-only, so we can't read it.
  2. Link customers to the Customer portal to update their card.
  3. Listen for payment_method.automatically_updated to see which cards the networks refreshed.
Reconcile checklist
  • Look up: Each subscription below and its card's expiry in the evidence, and whether that customer has an email to receive a reminder (see the missing-email finding).
  • Fix: Turn on expiring-card emails (Dashboard-only) and send the Customer portal link to update the card.
  • Confirm: Re-run the scan: a subscription drops off once the card on file expires beyond the 60-day horizon. Cards the networks refreshed arrive as payment_method.automatically_updated events.

Stripe docs: Automatic card updates · Automate customer emails

Object IDs to look at: sub_XQ8agOMTNwncxv000104, sub_Uzn8aB5kBh0fzK000109, sub_N2m1ElKncz8Hky000114, sub_ZCGGQccOif7UuX000119, sub_zkO7rRu5ykYYqh000124, sub_Gx5diFoNPcbdaK000129, sub_kd6XgaNJQ8mjAm000134, sub_95nf4Gakq5p1Vm000139, sub_eVce2LWxm090I5000144, sub_XgwETdIKnT30fK000149

MEDIUM Radar rules and lists RADAR_RULES

No evidence of custom Radar rules. You're relying on Stripe's default rules only, while this report found fraud or dispute signals.

Evidence How to fix
  1. Review https://dashboard.stripe.com/radar/rules and add rules that match your fraud pattern.
  2. Common starters: block if :cvc_check: = 'fail'; review if :risk_score: > 65; request 3DS if :risk_level: = 'elevated'.
  3. Use block lists for card fingerprints and emails from confirmed fraud.
Reconcile checklist
  • Look up: Radar > Rules in the Dashboard (there is no API for rules), next to the dispute and card-testing findings in this report.
  • Fix: Add at least one custom rule that matches that pattern, and block-list card fingerprints and emails from confirmed fraud.
  • Confirm: Re-run the scan once the rule has seen traffic: this check passes when charges show outcome.reason = rule.

Stripe docs: Radar rules · Radar lists

LOW Statement descriptor and support details DESCRIPTOR

Public details that help customers recognise your charges are incomplete.

Evidence How to fix
  1. Set a recognisable statement descriptor and support details in Settings > Business > Public details.
Reconcile checklist
  • Look up: Settings > Business > Public details: statement descriptor, support email or phone, business or support URL.
  • Fix: Set a descriptor a customer would recognise on a card statement (5+ characters), a support contact and a URL.
  • Confirm: Re-run the scan: this check passes when all three are set.

Stripe docs: Statement descriptors

Thresholds we compare against

ProgramMeasuresRatioMinimumConsequence
Stripe guidanceDispute activity0.75%No minimumStripe says activity above 0.75% is excessive and may reach out sooner on spikes.
Visa VAMP: non-compliant(Disputes + fraud warnings) / captured payments, monthly0.5%5 eventsVisa may assess fees.
Visa VAMP: excessiveSame1.5% (2.2% CEMEA)1,500 events (150 + USD 75k in CEMEA)Visa assesses fees.
Mastercard ECMChargebacks this month / captured payments last month1.5%100 chargebacksFines from month 2 (USD 1,000 and rising).
Mastercard HECMSame3.0%300 chargebacksHigher fines.

Sources: Stripe: Dispute and fraud monitoring programs · Stripe: Measuring disputes (checked 2026-10-02). The 0.9% Visa figure often quoted is from Visa's Dispute Monitoring Program (VDMP), retired in March 2025 and replaced by VAMP, which also counts fraud warnings. Some 2025 bulletins said VAMP's excessive ratio would fall to 0.9% in 2026; Stripe's current docs show 1.5%. Either way, Stripe's own 0.75% line comes first.

Coverage

Things a restricted key can't read (check by hand):

API requests made: 13, all GET: /v1/account ×1, /v1/balance ×1, /v1/charges ×1, /v1/disputes ×1, /v1/radar/early_fraud_warnings ×1, /v1/radar/value_lists ×1, /v1/refunds ×1, /v1/payouts ×1, /v1/subscriptions ×1, /v1/invoices ×2, /v1/webhook_endpoints ×1, /v1/events ×1

Your key was held in memory for this run only: not written to disk, not logged, and sent only to api.stripe.com. This report contains Stripe object IDs and aggregates, not card numbers or customer emails.

Stripe Leak Check by Zephos. Stripe is a trademark of Stripe, Inc.; this tool is not affiliated with or endorsed by Stripe.