Executive readout. Of $31,000 in observed first-attempt failures, $17,000 later recovered. The remaining $14,000 requires a customer payment update or should exit the standard retry path. No currently unpaid failure has a future Stripe retry scheduled.
$31,000 First-attempt failed12.9% of billed volume
$17,000 Recovered54.8% of observed failures
$14,000 Current exposure5.8% of billed volume
Current exposure by recommended action
Customer action required$11,500 current
Do not retry$2,500 current
Priority decisions
Priority labels below reflect observed failure value as a share of recurring billed volume: Low under 5%, Medium 5–10%, High above 10%. Operational urgency can still be immediate for hard declines.
Category
Observed failure
Later recovered
Current exposure
Customers
Recommended next action
Customer action required
$28,500
$17,000
$11,500
145
Validate failed-payment/3DS emails, a secure payment-update path, and subscription-level default-payment-method handling.
Do not retry
$2,500
$0
$2,500
15
Stop the ordinary retry posture; use a neutral new-payment-method flow and validate collection after update.
Cross-cutting configuration check: monitor invoice.payment_failed and invoice.updated, retain the scheduled-next-attempt state, and confirm what happens to subscription status and customer entitlement after the dunning window ends.
Prioritized recommendations
High
Customer action required: $11,500 currently needs a decision.
Evidence: Observed failure value: $28,500 (11.9% of recurring billed volume). $11,500 remains unresolved; $17,000 later recovered after an observed failure.
Action: Validate failed-payment/3DS emails, a secure payment-update path, and subscription-level default-payment-method handling.
Priority reflects observed failure volume as a share of recurring billed volume; it does not reduce the urgency of a hard decline or customer-action path.Low
Do not retry: $2,500 currently needs a decision.
Evidence: Observed failure value: $2,500 (1.0% of recurring billed volume). $2,500 has hard-decline or provider-advice evidence and remains unresolved.
Action: Stop the ordinary retry posture; use a neutral new-payment-method flow and validate collection after update.
Priority reflects observed failure volume as a share of recurring billed volume; it does not reduce the urgency of a hard decline or customer-action path.
Evidence confidence
160 of 160 observed failed invoices have a preserved first-failure snapshot. Browse the captured payment evidence by type below; the full machine-readable ledger remains available in evidence-ledger.json.
105 captured failures
Customer action / payment method
A payment method is missing or must be updated; background retries alone cannot complete that customer step.
Configuration checks: Validate failed-payment and authentication emails, a secure payment-update link or portal, automatic card updates where supported, and that the replacement payment method updates the subscription-level default where needed.
Show one auditable Stripe trace
Observed reason: Payment Method Required First failure: Aug 11, 2026 · 8:12 PM UTC Invoice:in_1U3M2UKAS1ZhxKDgoDSsRLlb Events:evt_1U3M2WKAS1ZhxKDgdNNVP67a, evt_1U3MVAKAS1ZhxKDgUerFdb3H, evt_1U3MVBKAS1ZhxKDgzagvopL1
40 captured failures
Temporary issuer decline
The issuer returned a temporary signal such as insufficient funds or try-again-later. In this fixture, no future Stripe retry is currently scheduled.
Configuration checks: Validate Smart Retries versus a custom retry schedule, the retry window and attempt limit, dunning messages, and that next payment attempts are observable in Stripe.
Show one auditable Stripe trace
Observed reason: Insufficient Funds First failure: Aug 11, 2026 · 8:18 PM UTC Invoice:in_1U3M7bKAS1ZhxKDgaKagAGpU Events:evt_1U3M7dKAS1ZhxKDgmJkpbI60
15 captured failures
Hard decline / do not retry
The issuer evidence indicates a lost card or do-not-try-again instruction.
Configuration checks: Stop the ordinary retry posture. Ask for a new payment method with neutral customer-facing language; do not expose a lost- or stolen-card reason.
Show one auditable Stripe trace
Observed reason: Lost Card First failure: Aug 11, 2026 · 8:21 PM UTC Invoice:in_1U3MB3KAS1ZhxKDgTYMgzjCg Events:evt_1U3MB5KAS1ZhxKDgBhMquel0
Continue the work
Turn this evidence into a measured payment-recovery plan, then validate the configuration and customer-journey changes that fit your billing operation.