Sample output — synthetic test data

A real run of the leak audit, on a test account with made-up invoices

This page reports no client. It is the audit tool's own output, run over a synthetic Stripe test account we built so there would be something to show: made-up invoices, made-up customer ids, a made-up account name. Every figure, table row and caveat below was printed by the tool — none of it was typed in by hand, so it cannot drift from what the audit really returns. If the tool changes, this page changes with it.

No figure on this page belongs to a real company. This is not a client, there is no client, and nothing here was recovered from anyone.

What follows is the page a prospect receives, unedited. Only the two amber labels — this one and the one above the headline figure — are ours; everything else is the tool's output. The Stripe key named at the top of it is a fixture string, not a live credential, and the audit was replayed against the same fake Stripe our test suite uses rather than any real account.

The headline figure this test run produces

5,370.00 USD at risk

across 10 invoices and 9 distinct customers — all of them synthetic, from a test account holding 14 made-up invoices. The figure is real tool output; the invoices behind it are not. Anchor date of the run: 2026-02-01T00:00:00.000Z.

Below: the audit page exactly as the tool printed it — synthetic data, not a client

Failed-payment audit — Fixture Subscription Co

Prepared by Recoverly. Read from your own Stripe account on 2026-02-01T00:00:00.000Z with a read-only key. Nothing in this page is an industry average or an estimate of your size: every figure below is a sum over the invoices in your own account, and the largest of them are listed individually further down so you can check them.

Key used: a restricted read-only key in test mode (test data only). The audit made 5 read request(s) for invoices and 1 for individual charges, every one of them pinned to Stripe API version 2024-06-20. Nothing was written to your account.

Still synthetic data: the figure below was produced against the same made-up test account. It is not a client's money, and no real company's invoices are behind it.

1. The number

5,370.00 USD at risk — 10 invoices, 9 distinct customers.

"At risk" means the amount still outstanding (Stripe's amount_remaining) on every invoice your account still lists as open, that Stripe has already attempted at least once, and that was created inside the lookback window. Only invoices created in the 90 days before the anchor date were requested. Left out of the headline in this currency: 1 open invoice(s) with 5,000.00 USD on them that nobody has attempted to collect yet, and 1 open invoice(s) with nothing still owing.

These invoices are a mix of ones Stripe will still try on its own and ones it has given up on. Its own retry state, for the invoices counted above:

Stripe's retry stateInvoicesAmount
Still has a retry scheduled21,230.00 USD
No retry left — Stripe has stopped84,140.00 USD

The same 5,370.00 USD, split by what would fix it:

What would fix itInvoicesAmountShare
A new card would fix this42,630.00 USD49%
Nothing we do recovers this2820.00 USD15%
We can't tell from the decline code41,920.00 USD36%

Estimate, not a promise. Worked out from the decline code Stripe recorded on each failed payment, using Stripe's own published meaning for that code. It does not know which customers still want the product, which ones have already left, or whether a customer will bother to update their card. Treat it as the ceiling on what a recovery series could reach, not as money in the bank.

Your invoices are in more than one currency, so they are not added together. Other currencies, largest first: 220.00 EUR across 1 invoice(s). Add the equivalent yourself at today's rate if you want one combined figure; we won't invent one.

2. Every decline code, counted — USD

Stripe decline codeInvoicesAmountWhat we class it asNote
expired_card21,350.00 USDA new card would fix thisthe card has expired; current card details are needed
card_not_supported1960.00 USDA new card would fix thisthis card type isn't accepted for this charge; a different card is needed
some_new_issuer_code1750.00 USDWe can't tell from the decline codenot a code we have a documented meaning for, so we don't guess
fraudulent1640.00 USDNothing we do recovers thisthe issuer flagged the payment as fraud; Stripe's guidance is not to retry
insufficient_funds1480.00 USDWe can't tell from the decline codea soft decline: the same card may work later, so a new card isn't clearly the fix
processing_error1440.00 USDWe can't tell from the decline codea network or processing fault; a later retry may succeed on its own
stolen_card1320.00 USDA new card would fix thisthe bank blocked a card reported stolen; a different card is needed
do_not_honor1250.00 USDWe can't tell from the decline codethe issuer's catch-all decline; the reason, and so the fix, isn't disclosed
revocation_of_all_authorizations1180.00 USDNothing we do recovers thisthe cardholder revoked all authorisations with their bank

Every code above is Stripe's own, read from your invoices or the failed charge behind them. What each code means comes from Stripe's decline-code documentation; the bucket it is put in is our reading of it, and a code we have no documented meaning for is counted as unknown rather than guessed at.

Total for USD: 5,370.00 USD across 10 invoice(s).

2. Every decline code, counted — EUR

Stripe decline codeInvoicesAmountWhat we class it asNote
pickup_card1220.00 EURA new card would fix thisthe bank asked for the card back; a different card is needed

Every code above is Stripe's own, read from your invoices or the failed charge behind them. What each code means comes from Stripe's decline-code documentation; the bucket it is put in is our reading of it, and a code we have no documented meaning for is counted as unknown rather than guessed at.

Total for EUR: 220.00 EUR across 1 invoice(s).

3. The largest invoices, so you can check this yourself

The 10 largest invoices in the figure above. Open any of these ids in your Stripe dashboard (Invoices → search the id) and the amount, attempt count and status should match exactly.

InvoiceCustomerAmountDays past dueAttemptsStripe retrying?Decline code
in_fixture_01cus_alpha1,200.00 USD333noexpired_card
in_fixture_04cus_gamma960.00 USD214nocard_not_supported
in_fixture_08cus_eta750.00 USD63yessome_new_issuer_code
in_fixture_05cus_delta640.00 USD141nofraudulent
in_fixture_02cus_alpha480.00 USD282yesinsufficient_funds
in_fixture_14cus_lambda440.00 USD11noprocessing_error
in_fixture_07cus_zeta320.00 USD82nostolen_card
in_fixture_03cus_beta250.00 USD245nodo_not_honor
in_fixture_06cus_epsilon180.00 USD96norevocation_of_all_authorizations
in_fixture_09[email protected]150.00 USD52noexpired_card

Where the code came from, for the rows above: invoice.last_finalization_error, charge.failure_code, invoice.payment_intent.last_payment_error. Those are the Stripe fields we read; the invoice id is the same one Stripe shows you.

Due dates and days past due use each invoice's due_date where Stripe set one, and its creation date where it did not. Anchor date for every "days" figure: 2026-02-01.

4. How to check the headline against your dashboard

  1. Stripe dashboard → Invoices → filter Status: Open. That is the exact set this audit was given (asked for 100 at a time, paged to the end — never just the first page).
  2. Cross-check the counts. The Open filter lists every open invoice; this audit counted 11 of them (10 in USD + 1 in EUR). Left out and stated in section 1: 1 open invoice(s) with a balance nothing has attempted to collect yet, and 1 with nothing still owing — all of them listed in the tallies above, so the filter will show more invoices than this page counts. Any open invoice created before 2025-11-03T00:00:00.000Z was never requested and is not in this page at all.
  3. Compare the Amount remaining column with the invoice table above. Our figure is the sum of that column, not of Amount due — an invoice with a partial payment shows only what is still owed.
  4. For any invoice in doubt, open it: the decline code we list is the one Stripe recorded on that invoice (or on the failed charge behind it), under the field named above.

If any of it does not match, tell us — the mismatch is worth more to us than the number, and we would rather correct this page than argue about it.

5. What this page does not claim

  • It only sees invoices your account still lists as open. A decline that never reached an invoice — a failed one-off PaymentIntent, a failed subscription creation, a payment abandoned at checkout — is invisible here, because there is no invoice to read.
  • It cannot know intent. An at-risk invoice belongs to a customer who may have already decided to leave; nothing in Stripe records that. So the at-risk figure is money that has not been collected, not money that will come back.
  • The three-way split is our reading of Stripe's decline codes, not a Stripe product. Stripe states what a code means; which bucket it belongs in is our judgement and is labelled an estimate.
  • Codes we have no documented meaning for are counted as unknown rather than guessed at, which pushes money out of the 'new card' figure, not into it.
  • Invoices marked uncollectible or void by your team are not counted at all: those are debts you have already written off.
  • Regional mandate problems (for example India-issued cards, or a customer whose bank mandate has lapsed) cannot be identified from a decline code alone, so some of the 'card update' money may in fact need a fresh mandate in the customer's banking app.
  • It reads card-level and mandate-level facts only. Card numbers are never returned by Stripe's API to anyone, including this audit.
  • Amounts are taken from Stripe exactly as stored (in the smallest currency unit) and never converted between currencies. If your invoices are in several currencies, the headline is the largest single currency and the others are listed separately.

Assumptions, in one line each

  • Anchor date: 2026-02-01T00:00:00.000Z. Every figure is as at 2026-02-01T00:00:00.000Z (the anchor date). Nothing after it is included.
  • Lookback: Only invoices created in the 90 days before the anchor date were requested.
  • At risk: the amount still outstanding (Stripe's amount_remaining) on every invoice your account still lists as open, that Stripe has already attempted at least once, and that was created inside the lookback window.
  • Amounts: Stripe's amount_remaining in the smallest unit of each invoice's own currency, never converted. Only invoices created after the lookback start and still marked open are considered.
  • Currency handling: each currency is summed separately; no exchange rate is invented.
  • Classification source: Stripe decline codes, 39 of them; a code outside that table is unknown and flagged.

This is an information page, not an offer or a quote. No fee is implied by it, and no customer of yours was contacted in producing it.

Generated for this page by scripts/audit.ts (runAudit + renderAuditMarkdown) reading scripts/audit-fixtures.ts through scripts/audit-fixture-api.ts, with the fixture account name Fixture Subscription Co and the harness anchor date 2026-02-01T00:00:00.000Z. The same code path and the same fixtures are what bun run audit and bun run audit:harness exercise.

Want this run on your own account?

The audit is free and it is the same page with your figures in it. It needs one thing from you: a Stripe restricted key set to Read on Invoices and Charges, and nothing else. The exact steps to create and revoke it are published, including what the key can never do. Then request the audit.