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
Summary
| Severity | Check | What we found | Est. at risk |
|---|---|---|---|
| HIGH | Involuntary churn (cancelled for failed payment) | 14 subscriptions ($256.49/mo) were cancelled because payment failed, 70% of all cancellations in the window. | $3,078 |
| HIGH | Payouts, holds and account requirements | Verification requirements due by 2026-10-10: individual.verification.document; plus 2 more. | $2,260 |
| HIGH | Failed invoice payments and retries | 11 invoice(s) with $1,406 outstanding are failed or overdue, and automatic retries appear to be off. | $1,976 |
| HIGH | Dispute rate vs card-network thresholds | Dispute activity is 0.68% over 90 days. At least one recent month crossed a threshold that card networks or Stripe act on. | $1,132 |
| HIGH | Webhook deliveries that haven't landed | 23 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 |
| HIGH | Early fraud warnings you can still refund | 4 payments have an actionable early fraud warning and are not refunded or disputed yet. | $387.00 |
| HIGH | Access 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 |
| HIGH | Card-testing signals | Found 1 burst(s) of failed charges (220 failures) consistent with card testing; 1 customer(s) cycling through cards. | $112.00 |
| HIGH | Disputes waiting for your response | 4 open disputes have no evidence submitted. If the deadline passes, you lose them automatically. | $76.00 |
| HIGH | Webhook endpoint setup | 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. | – |
| MEDIUM | Refund rate | Refunds are 9.98% of gross volume over 90 days. | $15,928 |
| MEDIUM | Customers without an email address | 47 subscribed customers ($854.96/mo) can't receive receipts, failed-payment or card-expiring emails. | $854.96 |
| MEDIUM | Past-due and unpaid subscriptions | 9 subscriptions ($171.00/mo, 3.1% of MRR) are behind on payment. | $513.00 |
| MEDIUM | Cards expiring in the next 60 days | 12 subscriptions ($228.00/mo) are on cards that expire within 60 days. | $228.00 |
| MEDIUM | Radar rules and lists | No evidence of custom Radar rules. You're relying on Stripe's default rules only, while this report found fraud or dispute signals. | – |
| LOW | Statement descriptor and support details | Public 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.
- 20 cancellations in the last 180 days; 14 with cancellation_details.reason = payment_failed.
- Lost MRR from these: $256.49/mo.
- These customers didn't choose to leave. Email them a reactivation link.
- Turn on Smart Retries and failed-payment emails, and consider a longer retry window before cancelling.
- Enable card-expiring reminders so cards get updated before the renewal fails.
- 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 / customer | Stripe status | Last successful payment | Entitlement to check in your app |
|---|---|---|---|
sub_GolAGMm4KL6r6U001504cus_QVRBLyz05etI2I001501 | canceled | 2026-09-21, $19.00 | Off, unless the customer is on a new paid subscription |
sub_CQiLoAZPdtlnON001509cus_7m5nbLSz3FK6GD001506 | canceled | 2026-09-20, $49.00 | Off, unless the customer is on a new paid subscription |
sub_i16KZBHxUd1bQ1001514cus_yKBvDN4pDEAT0q001511 | canceled | 2026-09-08, $19.00 | Off, unless the customer is on a new paid subscription |
sub_rKU0UP4aNGH05m001519cus_oRGBhYQpGScrkF001516 | canceled | 2026-09-03, $49.00 | Off, unless the customer is on a new paid subscription |
sub_1bQ3pt5l2F5UmM001524cus_5mT2zmNDt1djFg001521 | canceled | 2026-09-05, $19.00 | Off, unless the customer is on a new paid subscription |
sub_aqdLmWJAsSxvPu001529cus_qOTm55f6VYQX6X001526 | canceled | 2026-09-10, $19.00 | Off, unless the customer is on a new paid subscription |
sub_0Mk5oQo1uKpoky001534cus_8wK8lsdbBSvy0B001531 | canceled | 2026-08-16, $190.00 | Off, unless the customer is on a new paid subscription |
sub_Yhgl9PKDO3nsbu001539cus_QaO3i5qEtxYm8B001536 | canceled | 2026-07-07, $99.00 | Off, unless the customer is on a new paid subscription |
sub_fcAuJISnmb0hMY001544cus_zKShNS3UIKe9kE001541 | canceled | 2026-09-02, $19.00 | Off, unless the customer is on a new paid subscription |
sub_UHfz2a6fDol3Vm001549cus_ZfMNr45WHXPMVN001546 | canceled | 2026-09-04, $19.00 | Off, unless the customer is on a new paid subscription |
Stripe docs: Automate payment retries (Smart Retries) · Automate customer emails · Revenue recovery
HIGH Payouts, holds and account requirements PAYOUTS
Verification requirements due by 2026-10-10: individual.verification.document; plus 2 more.
- Payout schedule: daily, delay 14 days.
- Balance: $2,412 available, $10,854 pending.
- 26 payouts in the window.
- Verification requirements due by 2026-10-10: individual.verification.document
- Payout delay is 14 days, longer than usual. Stripe sometimes extends it when it sees risk. Ask Stripe support if you didn't choose it.
- 1 payout(s) failed or were canceled ($2,260): po_girAhHK0BfDqFw005174 account_closed
- Clear any requirements in Settings > Business > Account status before the deadline.
- For failed payouts, check the bank account details in Settings > Payouts.
- If payouts are delayed and you didn't change the schedule, contact Stripe support and ask whether a reserve or review applies.
- Reserves aren't fully visible to a restricted key; check Balances in the Dashboard.
- 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
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.
- 11 open auto-charge invoices with a failed payment: $1,406 outstanding.
- 0 have a retry scheduled; 11 have no next_payment_attempt (retries finished or off).
- attempt_count distribution: 1×11
- 11 of 11 failed after a single attempt and were never retried. That pattern usually means automatic retries are off.
- 3 invoices marked uncollectible in the window: $570.00 written off.
- 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.
- Turn on failed-payment emails with a link to update the card (Billing > Revenue recovery > Emails: https://dashboard.stripe.com/revenue_recovery/emails).
- Decide what happens after the last retry (cancel, mark unpaid, or leave past_due) on purpose, not by default.
- Retry settings aren't readable through the API; confirm them in the Dashboard.
- 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
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.
- Last 90 days: 9 disputes on 1330 captured payments (0.68%).
- Monthly (captured / disputes / dispute activity / Visa VAMP events & ratio / Mastercard chargebacks & rate vs prior month):
- 2026-05: 451 / 1 / 0.22% / 1 (0.41%) / 0 (0.00%)
- 2026-06: 443 / 1 / 0.23% / 1 (0.46%) / 0 (0.00%)
- 2026-07: 442 / 2 / 0.45% / 2 (0.88%) / 0 (0.00%)
- 2026-08: 473 / 1 / 0.21% / 1 (0.38%) / 0 (0.00%)
- 2026-09: 447 / 7 / 1.57% / 11 (5.00%) / 0 (0.00%)
- 2026-10 (month to date): 9 / 0 / 0.00% / 0 (0.00%) / 0 (0.00%)
- Rising: last full month 1.57% vs 0.30% average of the prior three.
- Top reasons: fraudulent (5), product_not_received (2), subscription_canceled (2)
- 2026-09: dispute activity 1.57% ≥ Stripe's 0.75% line.
- Network 'excessive' programs also need minimum counts (Visa 1,500 events; Mastercard 100 chargebacks), so small accounts rarely enter them formally. Stripe can still act on high rates or spikes.
- Check your standing on the VAMP dashboard (Radar > Card network monitoring): https://dashboard.stripe.com/radar/cbmp/vamp
- Make the charge recognisable: a clear statement descriptor and a support URL/email on your public details.
- Refund actionable early fraud warnings before they become disputes (see the EFW finding).
- Turn on Stripe's dispute prevention (Visa Order Insights / RDR, Mastercard Ethoca alerts) if your volume justifies the per-alert fee.
- For 'fraudulent' disputes, add Radar rules (block CVC failures, 3DS for high-risk payments).
- For 'product_not_received' / 'subscription_canceled', send renewal reminders and make cancelling easy.
- 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
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.
- Oldest undelivered event: 2026-09-07 12:00 UTC.
- By type: checkout.session.completed (8), invoice.paid (8), customer.updated (7)
- Stripe retries live-mode deliveries for up to three days, then stops.
- Open Developers > Webhooks > your endpoint > Event deliveries and read the error.
- Fix the handler (return 2xx quickly, do work async), then resend or process the missed events.
- Reconcile: check that every paid Checkout Session or invoice in this list got fulfilled.
- 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
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.
- 4 actionable warnings, $327.00 in payments.
- Visa counts these warnings toward the VAMP ratio whether or not a dispute follows.
- issfr_06NaU3OUEZ3cM8004865 on ch_xmALVdXq1bLs5C003916: made_with_stolen_card, 2026-09-03
- issfr_JDgbG4U1uFF7p4004866 on ch_q5SUZOurS4tZd5003921: made_with_stolen_card, 2026-09-03
- issfr_WM9OMC8MyYio3s004867 on ch_5gnVSxqFDqXOpa003941: made_with_stolen_card, 2026-09-04
- issfr_2gaKlzQk8JQ1ol004868 on ch_IOyLyXV1AbCJXs003936: made_with_stolen_card, 2026-09-05
- Review each payment. If it looks fraudulent, refund it now (Payments > select payment > Refund).
- Consider a Radar rule or list entry for the card fingerprint or email involved.
- 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
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.
- 1 enabled webhook endpoint(s). Events covered: checkout.session.completed, customer.subscription.deleted, invoice.paid.
- 9 subscriptions behind on payment (past_due: 6, unpaid: 3), $171.00/mo; 3 of them with retries finished or marked unpaid ($57.00/mo).
- 3 subscriptions are stuck (unpaid, or past_due with no retry scheduled). No customer.subscription.deleted is coming for them, so access granted at checkout stays on.
- sub_rhhhz4iILo3ojQ000234: unpaid, $19.00/mo
- sub_7DOcZ44cc3PNr6000239: unpaid, $19.00/mo
- sub_xD5JtNEE0tbpvo000244: unpaid, $19.00/mo
- sub_JdED5jSFpFkIM3000179: paused, $19.00/mo
- sub_sw0FzvGr3GwnPF000184: pause_collection, pause_collection=mark_uncollectible, $15.83/mo
- sub_n7qLWaYyDIfIZw000204: past_due, $19.00/mo
- sub_g8CXL0M9iq1cvm000209: past_due, $19.00/mo
- sub_EdgjuWa8mRVtLL000214: past_due, $19.00/mo
- sub_J4jC3jrAApjbrK000219: past_due, $19.00/mo
- sub_c6AnrKli1lHXoT000224: past_due, $19.00/mo
- sub_7C9HehwTp0136u000229: past_due, $19.00/mo
- sub_rhhhz4iILo3ojQ000234: unpaid, $19.00/mo
- sub_7DOcZ44cc3PNr6000239: unpaid, $19.00/mo
- No enabled endpoint listens for customer.subscription.updated or invoice.payment_failed, but they do listen for checkout.session.completed, invoice.paid and customer.subscription.deleted. If access is granted on payment and revoked on deletion, a subscription that goes past_due or unpaid never loses access. Stripe sends .deleted only when the subscription is cancelled, and after the last failed retry your retry settings may mark it unpaid or leave it past_due instead.
- 11 subscription(s) are not active/trialing (and not in past_due grace) (past_due: 6, pause_collection: 1, paused: 1, unpaid: 3, $205.83/mo). If your app still grants them access, that is a leak. Drive entitlements from status: active or trialing = access; past_due = grace while retries run; paused, pause_collection, unpaid, incomplete, canceled = revoke.
- We can't read your webhook handler. This is inferred from which events your endpoints receive and what your subscriptions and cancellations look like.
- 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.
- 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).
- Reconcile today: for each subscription listed here, check whether your app still grants access.
- 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).
- 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.
- For past_due, keep access only while a retry is still scheduled (next_payment_attempt); revoke when retries are finished or status becomes unpaid.
- 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 / customer | Stripe status | Last successful payment | Entitlement to check in your app |
|---|---|---|---|
sub_rhhhz4iILo3ojQ000234cus_CGbHZIibp9foNl000231 | unpaid | 2026-08-26, $19.00 | Off (unpaid: Stripe stopped retrying) |
sub_7DOcZ44cc3PNr6000239cus_1MHcz8dXxvzp1v000236 | unpaid | 2026-09-26, $19.00 | Off (unpaid: Stripe stopped retrying) |
sub_xD5JtNEE0tbpvo000244cus_Bp8cshtwPkhdM9000241 | unpaid | 2026-09-06, $49.00 | Off (unpaid: Stripe stopped retrying) |
sub_JdED5jSFpFkIM3000179cus_qMgLj2olXCwYjn000176 | paused | 2026-09-28, $19.00 | Off (paused), unless it's a hold you chose and can name |
sub_sw0FzvGr3GwnPF000184cus_BA9RelOxOPbbNc000181 | active, pause_collection: mark_uncollectible | 2026-09-20, $190.00 | Off (paused), unless it's a hold you chose and can name |
sub_n7qLWaYyDIfIZw000204cus_oZCsSauqrBkL60000201 | past_due | 2026-09-25, $19.00 | Off, unless a retry is still scheduled (no open invoice with a next retry was found) |
sub_g8CXL0M9iq1cvm000209cus_LmmnmflZSsxKKw000206 | past_due | 2026-09-04, $99.00 | Off, unless a retry is still scheduled (no open invoice with a next retry was found) |
sub_EdgjuWa8mRVtLL000214cus_65e3MOz7hT9fqu000211 | past_due | 2026-08-03, $19.00 | Off, unless a retry is still scheduled (no open invoice with a next retry was found) |
sub_J4jC3jrAApjbrK000219cus_CpZj6R5aDT6mZc000216 | past_due | 2026-09-01, $49.00 | Off, unless a retry is still scheduled (no open invoice with a next retry was found) |
sub_c6AnrKli1lHXoT000224cus_GdO5YQ7nJE1shq000221 | past_due | 2026-09-03, $19.00 | Off, unless a retry is still scheduled (no open invoice with a next retry was found) |
Stripe docs: Using webhooks with subscriptions · Subscription statuses · Automate payment retries (Smart Retries) · Pause a subscription · Pause payment collection
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.
- 2026-09-14 03:00 UTC for 2h: 220 failed vs 8 succeeded, 120 distinct cards, 100% of attempts ≤ $5.00; top decline reasons: generic_decline (110), do_not_honor (55), incorrect_cvc (55)
- 1 customers/emails tried 5+ different cards that failed (max 6). Customer IDs: cus_F3n6w4QhfCKK4l004839
- Overall: 314 failed of 2977 charge attempts (10.55%) in the window.
- IP addresses aren't available through the API; check Radar's payment details for IP and device data.
- Refund the small successful charges from the burst windows before they turn into disputes.
- Use Checkout or the Payment Element (Stripe's built-in card-testing defences apply there).
- Add a CAPTCHA and rate limiting to any endpoint that creates PaymentIntents or SetupIntents.
- Add Radar rules, for example block if :card_count_for_customer_daily: > 3, or require 3DS on small amounts.
- Make sure your secret key hasn't leaked; roll it if in doubt.
- 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
HIGH Disputes waiting for your response DISPUTES_UNANSWERED
4 open disputes have no evidence submitted. If the deadline passes, you lose them automatically.
- 4 disputes need a response, totalling $76.00.
- dp_F75jCRgnJemIAK004859: $19.00, reason fraudulent, evidence due 2026-10-03
- dp_jdFwmqm3uoZUtb004860: $19.00, reason product_not_received, evidence due 2026-10-04
- dp_SVQb5IxlnMphmP004861: $19.00, reason subscription_canceled, evidence due 2026-10-05
- dp_feAWEsnpso2n7Y004862: $19.00, reason product_not_received, evidence due 2026-10-06
- Open each dispute in the Dashboard (Payments > Disputes) and submit evidence before the due date.
- Include proof of delivery or usage, your refund policy, and customer communication.
- If the claim is valid, accept it to close it quickly.
- 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
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- 2 endpoints (1 enabled).
- we_ujeF93V9NHLPgG005124: enabled, https://app.northwind-notes.example/api/stripe, 3 event types
- we_a68j9zBlMVFFkJ005125: disabled, http://old.northwind-notes.example/hooks/stripe, 1 event types
- we_a68j9zBlMVFFkJ005125 (http://old.northwind-notes.example/hooks/stripe) is DISABLED. Stripe stops sending to it, so nothing it handled is happening.
- we_a68j9zBlMVFFkJ005125 uses plain http:// (http://old.northwind-notes.example/hooks/stripe).
- No enabled endpoint listens for: charge.dispute.created, invoice.payment_failed, customer.subscription.updated.
- Re-enable or delete disabled endpoints (Developers > Webhooks). Fix the handler first, or it will be disabled again.
- Use HTTPS endpoints only.
- Subscribe to invoice.payment_failed, invoice.paid, customer.subscription.updated/deleted and charge.dispute.created.
- Verify signatures on every event.
- 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
MEDIUM Refund rate REFUND_RATE
Refunds are 9.98% of gross volume over 90 days.
- Last 90 days: $7,365 refunded on $73,765 gross (9.98%), 124 refunds.
- Reasons: requested_by_customer (56), duplicate (36), none given (32)
- Stripe does not return the original processing fee when you refund.
- Read the refund reasons and the products involved; fix the top cause (expectations, onboarding, billing surprise).
- Send renewal reminders before annual charges.
- Keep refunding instead of letting disputes happen; just make refunds rarer.
- 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
MEDIUM Customers without an email address MISSING_EMAILS
47 subscribed customers ($854.96/mo) can't receive receipts, failed-payment or card-expiring emails.
- 47 of 296 active subscriptions belong to customers with no email.
- 0 payments in the last 90 days have no customer, receipt email or billing email, so no receipt can be sent.
- Whether Stripe emails receipts automatically is a Dashboard setting (https://dashboard.stripe.com/settings/emails) that a key can't read.
- Collect email at checkout (Checkout does this by default) and backfill it on existing customers.
- Turn on successful-payment and refund receipts in Settings > Customer emails (https://dashboard.stripe.com/settings/emails).
- Unrecognised charges become disputes; a receipt is a cheap way to be recognised.
- 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
MEDIUM Past-due and unpaid subscriptions PAST_DUE_SUBS
9 subscriptions ($171.00/mo, 3.1% of MRR) are behind on payment.
- past_due: 6, unpaid: 3
- Total MRR $5,450.
- Email these customers a link to update their payment method (the Customer portal works).
- Make sure retries and failed-payment emails are on (see the failed-invoice finding).
- For 'unpaid' subscriptions, decide whether to cancel or keep providing service.
- 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 / customer | Stripe status | Last successful payment | Entitlement to check in your app |
|---|---|---|---|
sub_n7qLWaYyDIfIZw000204cus_oZCsSauqrBkL60000201 | past_due | 2026-09-25, $19.00 | Off, unless a retry is still scheduled (no open invoice with a next retry was found) |
sub_g8CXL0M9iq1cvm000209cus_LmmnmflZSsxKKw000206 | past_due | 2026-09-04, $99.00 | Off, unless a retry is still scheduled (no open invoice with a next retry was found) |
sub_EdgjuWa8mRVtLL000214cus_65e3MOz7hT9fqu000211 | past_due | 2026-08-03, $19.00 | Off, unless a retry is still scheduled (no open invoice with a next retry was found) |
sub_J4jC3jrAApjbrK000219cus_CpZj6R5aDT6mZc000216 | past_due | 2026-09-01, $49.00 | Off, unless a retry is still scheduled (no open invoice with a next retry was found) |
sub_c6AnrKli1lHXoT000224cus_GdO5YQ7nJE1shq000221 | past_due | 2026-09-03, $19.00 | Off, unless a retry is still scheduled (no open invoice with a next retry was found) |
sub_7C9HehwTp0136u000229cus_iNQTOZmLtmaeSU000226 | past_due | 2026-09-26, $19.00 | Off, unless a retry is still scheduled (no open invoice with a next retry was found) |
sub_rhhhz4iILo3ojQ000234cus_CGbHZIibp9foNl000231 | unpaid | 2026-08-26, $19.00 | Off (unpaid: Stripe stopped retrying) |
sub_7DOcZ44cc3PNr6000239cus_1MHcz8dXxvzp1v000236 | unpaid | 2026-09-26, $19.00 | Off (unpaid: Stripe stopped retrying) |
sub_xD5JtNEE0tbpvo000244cus_Bp8cshtwPkhdM9000241 | unpaid | 2026-09-06, $49.00 | Off (unpaid: Stripe stopped retrying) |
Stripe docs: Subscription statuses · Automate customer emails
MEDIUM Cards expiring in the next 60 days EXPIRING_CARDS
12 subscriptions ($228.00/mo) are on cards that expire within 60 days.
- 12 of 296 active subscriptions pay with a card that expires before 2026-11-30.
- 3 of these cards have already expired.
- sub_XQ8agOMTNwncxv000104: mastercard expiring 09/2026, $19.00/mo
- sub_Uzn8aB5kBh0fzK000109: mastercard expiring 09/2026, $19.00/mo
- sub_N2m1ElKncz8Hky000114: visa expiring 09/2026, $19.00/mo
- sub_ZCGGQccOif7UuX000119: mastercard expiring 10/2026, $19.00/mo
- sub_zkO7rRu5ykYYqh000124: mastercard expiring 10/2026, $19.00/mo
- sub_Gx5diFoNPcbdaK000129: visa expiring 10/2026, $19.00/mo
- sub_kd6XgaNJQ8mjAm000134: amex expiring 10/2026, $19.00/mo
- sub_95nf4Gakq5p1Vm000139: mastercard expiring 10/2026, $19.00/mo
- sub_eVce2LWxm090I5000144: mastercard expiring 10/2026, $19.00/mo
- sub_XgwETdIKnT30fK000149: visa expiring 10/2026, $19.00/mo
- 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.
- Link customers to the Customer portal to update their card.
- Listen for payment_method.automatically_updated to see which cards the networks refreshed.
- 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
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- 2977 of 2977 card charges carry a Radar risk score.
- 0 charges were allowed, blocked or reviewed by a custom rule (outcome.reason = 'rule').
- Value lists with entries: 0 of 1.
- Stripe has no API for listing Radar rules, so this is inferred from charge outcomes.
- Review https://dashboard.stripe.com/radar/rules and add rules that match your fraud pattern.
- Common starters: block if :cvc_check: = 'fail'; review if :risk_score: > 65; request 3DS if :risk_level: = 'elevated'.
- Use block lists for card fingerprints and emails from confirmed fraud.
- 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- Statement descriptor is 'NWN'. Customers who don't recognise a charge dispute it.
- No public support email or phone. Customers who can't reach you ask their bank instead.
- Set a recognisable statement descriptor and support details in Settings > Business > Public details.
- 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
| Program | Measures | Ratio | Minimum | Consequence |
|---|---|---|---|---|
| Stripe guidance | Dispute activity | 0.75% | No minimum | Stripe says activity above 0.75% is excessive and may reach out sooner on spikes. |
| Visa VAMP: non-compliant | (Disputes + fraud warnings) / captured payments, monthly | 0.5% | 5 events | Visa may assess fees. |
| Visa VAMP: excessive | Same | 1.5% (2.2% CEMEA) | 1,500 events (150 + USD 75k in CEMEA) | Visa assesses fees. |
| Mastercard ECM | Chargebacks this month / captured payments last month | 1.5% | 100 chargebacks | Fines from month 2 (USD 1,000 and rising). |
| Mastercard HECM | Same | 3.0% | 300 chargebacks | Higher fines. |
Coverage
Things a restricted key can't read (check by hand):
- Radar rules: There is no API to list Radar rules. We infer custom rules from charge outcomes (outcome.rule) and check value lists. Review https://dashboard.stripe.com/radar/rules.
- Smart Retries / retry schedule: Billing retry settings are Dashboard-only. We infer whether retries are running from invoice attempt_count and next_payment_attempt. Check https://dashboard.stripe.com/revenue_recovery/retries.
- Customer email settings (receipts, failed-payment emails): Dashboard-only. Check https://dashboard.stripe.com/settings/emails (receipts) and https://dashboard.stripe.com/revenue_recovery/emails (dunning).
- Webhook delivery attempt logs: Per-attempt logs are Dashboard-only. We use the Events API's pending_webhooks counter (last 30 days) instead.
- IP addresses of payment attempts: Not exposed on Charge objects. Card-testing detection uses timing, amounts, card fingerprints and decline codes instead.
- Reserves: Rolling or fixed reserves aren't fully visible to a restricted key. We flag the signals we can see (payout schedule delay, pending balance, verification requirements).
Stripe Leak Check by Zephos. Stripe is a trademark of Stripe, Inc.; this tool is not affiliated with or endorsed by Stripe.