Working · 2026-11Vendor claimRetentionBilling

ML-timed payment retries

Use a model trained on payment-network signals to choose when and how to retry failed subscription charges, instead of a fixed schedule.

Also called: smart retries, network-informed retry logic

Claim and evidence

The claimrecover $9 in revenue for every $1 customers spend on Billing.

Stripe Billing · stripe.com · 2024-01-23

What the numbers show

$9 per $1

customers spend on Billing, recovered per Stripe (vendor claim)

stripe.com

Why it works

Diagram, not data
Charge failsRead declinecode andsignalsRetry at thelikeliestmomentHard decline:ask for a newcard
Charge failsRead decline code and signalsRetry at the likeliest momentHard decline: ask for a new card

Issuer approval odds vary by time, device signals and decline code. Choosing retry timing and sometimes switching payment method recovers charges a fixed schedule loses.

How to run it

  1. Enable smart or network-aware retries in your billing tool
  2. Set max retries and window (e.g. 8 retries in 2 weeks)
  3. Skip retries on hard declines and request a new card
  4. Add emails with a payment-update link
  5. Report recovery rate by cohort

Ways to run it

Design options to test, not promised results.

  1. Option ABilling-tool smart retries

    Turn on model-timed retries in your billing tool, as Stripe offers with Smart Retries.

  2. Option BRetry window and cap

    Set a maximum number of retries over a fixed window and stop early on hard declines.

  3. Option CRetries plus emails

    Pair retries with emails that link to a payment-update page, and report recovery by cohort.

Timeline

  1. 12024 first documented: Stripe blog (Kiran Chandran)
  2. 22024 Stripe Billing — Says Smart Retries use 500+ attributes; a quarter of lapsed subscriptions are purely payment failures.
  3. 32024 Deliveroo — Stripe says it recovered over £100M in one year using Smart Retries with other recovery tools.
  4. 42026 Enterprise retailer (Recurly case) — Existing system recovered about 53% of eligible failed transactions before optimized retry logic.
  5. 52026-11 status checked: Working

Dated examples

  1. 2026

    Enterprise retailer (Recurly case)

    Existing system recovered about 53% of eligible failed transactions before optimized retry logic.

    “Their current system was recovering approximately 53% of eligible failed transactions.”
    ✓ quote checked word-for-word on the page

    recurly.com · 2026-04-30

  2. 2024

    Stripe Billing

    Says Smart Retries use 500+ attributes; a quarter of lapsed subscriptions are purely payment failures.

    $9 recovered per $1 spent on Billing; recovered subscriptions last about seven more months.

    “recover $9 in revenue for every $1 customers spend on Billing.”
    ✓ quote checked word-for-word on the page

    stripe.com · 2024-01-23

  3. 2024

    Deliveroo

    Stripe says it recovered over £100M in one year using Smart Retries with other recovery tools.

    stripe.com · 2024-01-23

Does it still work?

Workingas of 2026-11

Stripe docs enable Smart Retries by default for new accounts with up to 8 retries in 2 weeks. source

Risks

  • Vendor figures only
  • No retry on hard declines

Sources

  1. stripe.com · Stripe Blog · Kiran Chandran · 2024-01-23
    “recover $9 in revenue for every $1 customers spend on Billing.”
    ✓ quote checked word-for-word on the page
  2. docs.stripe.com · Stripe Docs · undated
    “Using AI, Smart Retries chooses the best times to retry failed payment attempts to increase the chance of successfully paying an invoice.”
    ✓ quote checked word-for-word on the page
  3. recurly.com · Recurly Blog · Matthew Calhoun · 2026-04-30
    “Their current system was recovering approximately 53% of eligible failed transactions.”
    ✓ quote checked word-for-word on the page

Change log

  • 2026-11-20 — harvest v0.1 (retention)