Failed-payment recovery for Stripe subscriptions

Failed payments are leaking MRR between Stripe's retries. We chase the ones retries can't reach.

Recoverly is failed payment recovery software for Stripe subscription businesses. Stripe's retries work on a card that is still valid; when the issuer returns a hard decline, the retries stay scheduled but the payment only executes once a new card is attached — so the only cure left is reaching your customer.

Stripe already retries. Here's the gap.

Stripe Billing's revenue recovery will retry a failed payment up to 8 times in 2 weeks by default, and that part works. Its own documentation is just as clear about where it stops: if the issuer returns a hard decline code, Stripe “can't retry invoice payment without a new payment method”. The retries stay on the schedule and the attempt counter keeps climbing, but nothing executes until a new card is attached. Stripe can't call your customer and ask for one. Somebody has to, and that is the part we do.

What we can't recover. Hard declines, stolen or cancelled cards, and some regional mandates need a new payment method — a new card, or a fresh mandate in the customer's own banking app — and India-issued cards aren't retried at all. If your customer won't do that, the invoice stays lost, and we won't pretend otherwise. The audit tells you which of your declines a new card would fix, and which nothing would.

Stripe Smart Retries: what they retry, and the declines they can't fix →

Free Failed-Payment Leak Audit

Tell us where to look and we'll tell you what's still recoverable.

No card details, nothing to install. We keep what you send us so we can reply to it. What we store, and how to get it deleted.

We'll ask for a read-only Stripe key once you're ready. See the exact steps first — what the key can read, what it can never do, and how to revoke it.

  • Read-only Stripe access — we never see card data, and nothing runs on your servers
  • A retry schedule and an email sequence — run by us, by hand, during pilots
  • No setup fee, no retainer — we're paid from what we recover

We're looking for our first design partners right now. That means a small number of accounts, direct access to the people building it, and terms agreed in writing with you first.

What the free Failed-Payment Leak Audit gives you back

  • One page, one figure: the money at risk, worked out from your own Stripe invoice data — not an industry average and not a guess at your size.
  • Which of your declines a new card would actually fix, and which ones a new card wouldn't.
  • What a pilot would cost you, in writing, before you decide anything.

Tell us where to look and we'll come back to you by email. Request the audit. Before you hand over a key, the exact steps to create and revoke it are published — including what we can read, what the key can never do, and the one permission a pilot needs that the audit key does not.

You don't have to take our word for what comes back. See a real run of the audit on a test account → That is the tool's own output over made-up invoices — a synthetic account, not a client, and no real company's figures anywhere on it.

How it works

Three steps, and only the first one needs your team. This is where involuntary churn comes from — customers who meant to keep paying and lost the subscription to an expired or reissued card.

  1. 1

    Connect your Stripe account (read-only)

    You issue a Stripe restricted key with Read access to invoices and charges — and nothing else. Not your customers, subscribers, products or balance. For the free audit the key can only read: it cannot create charges, move money, issue refunds or change anything in your account, and card numbers are never visible through the API in the first place. If you go on to a pilot, the retries themselves need one more permission on that key — attempting payment on a failed invoice — and we ask for that separately, in writing, before we switch retries on. Starting the pilot also needs a webhook endpoint added in your Stripe dashboard: a two-minute setting that tells us the moment a payment fails. Without it we would only see failures when we went looking.

    The exact steps, the two permissions we ask for, and how to revoke →

  2. 2

    We chase the invoices Stripe has given up on

    When an invoice payment fails we run our own retry schedule and write to the customer ourselves — a short message about the failed payment, carrying a link to Stripe's own hosted page for that invoice, where they can pay with a new card. Where Stripe gives us no such link, the message says so rather than carrying a dead one. No one on your team has to notice the failure or remember to follow up. During pilots a person runs the schedule and sends each message by hand from our own inbox, using exactly the text our tool renders — so the sending address is ours, not your brand: sending as you needs a verified sending domain we don't have yet.

  3. 3

    You pay a share of what we recover

    You are invoiced on revenue we actually recover. No setup fee, no retainer, and if nothing is recovered there is nothing to pay.

Works with, and doesn't work with

Works with

  • Stripe accounts, with subscriptions billed through Stripe Billing
  • One account per engagement, for now
  • Reporting and results by email, in plain numbers

Doesn't work with

  • Chargebee, Recurly, Braintree or any other billing system
  • Multi-account or team roll-ups — one login at a time
  • A live dashboard. There isn't one yet, and we won't pretend otherwise

Who this isn't for: our own rule of thumb says subscription businesses under roughly $20k MRR. Below that the recoverable amount is usually too small to be worth anyone's time, and we would rather say so up front than take the engagement.

What it costs

Performance pricing. We take a share of the revenue we recover, and the rate is agreed with each design partner before we start — our target for the first 12 months is 20% of recovered revenue.

How a recovery gets counted: an invoice only counts if our own series actually ran on it — a retry attempt or a message that really happened — and we bill on the amount Stripe records as paid, the same invoice IDs, amounts and dates your dashboard shows. Where Stripe records nothing as paid, we treat the invoice as not recovered. You see exactly the numbers we see, so if your Stripe says an invoice wasn't recovered, we don't bill it. If a recovery is later refunded or reversed, tell us and we take it off the total.

How we attribute recovered revenue — the rule in full, and the invoice list you check it against →

Setup fee
None.
Monthly retainer
None. There is nothing to pay in a month where we recover nothing.
Our fee
A share of recovered revenue, invoiced after the money is back in your account. The percentage is written into your engagement terms — target 20% for the first 12 months — and you approve it before we touch your account.
Where we are today
We're looking for our first design partners now. There is no published case-study page, because there are no past results to publish yet — the audit and the pilot are how a claim like that would ever get earned.
Scope for a first design partner
Stripe only, one account, reporting by email. No self-serve dashboard, no other processors and no team accounts yet.

Questions, answered honestly

Will the reminders annoy my customers — can a customer opt out?

Yes, in one click, and it is real. Every message carries a one-click way to stop the reminders: that message is the last one, anything still queued for that invoice is cancelled, and we record that we should leave that customer alone, so a later failure on a different invoice does not start the messages again. If a customer tells us another way — replying to a message, or telling you — we suppress them by hand. We don't re-attach a card someone deliberately let expire, and if a customer says they don't want the subscription we stop rather than push them into paying for something they are leaving.

Is connecting our Stripe account safe?

We ask for a Stripe restricted key with Read access to invoices and charges, and nothing else — we never need to see your customers, subscribers, products or balance. For the free audit that key can only read: it cannot create charges, refund money or change anything in your account, and card numbers are never exposed by Stripe's API to anyone, including us. Retrying a failed invoice is the one action that needs more than reading, so if we go on to a pilot we ask for that permission separately and in writing before we turn retries on. You can revoke the key at any time, which ends our access immediately.

How is this different from Stripe's own dunning and smart retries?

Stripe already retries some failed payments and can send its own recovery emails, and we don't replace that. Recoverly runs alongside it: our own retry attempts over a longer window, our own written sequence about the failed payment, and a link to Stripe's own hosted page for that invoice rather than a Stripe-branded notice. During pilots a person sends each message by hand from our own inbox, using exactly the text our tool renders — sending from your own brand is built but switched off, because it needs a verified sending domain we don't have yet. We also pick up invoices Stripe has stopped retrying. If your retry settings are already doing everything we would do, a leak audit will show that, and we'll tell you so.

What does it cost?

Performance pricing only. No setup fee and no monthly retainer: we're paid a share of the revenue we recover, and the exact percentage is agreed in writing with each design partner before we start on their account. Our target for a 12-month engagement is 20% of recovered revenue — you'll see the agreed number for your account before anything goes live.

What if you recover nothing?

Then you pay nothing. Our fee is a share of recovered revenue, so a month with no recoveries is a month with no invoice. The trade is your time: connecting the key and agreeing the email wording once at the start.

How long before we see results?

The first recoveries come from invoices you have already lost — failed payments still inside their retry window. Beyond that, recovery depends on how many payments fail, why they fail and whether those customers still want the product, so we won't quote you a percentage or a payback period we haven't produced. We run as a design partner engagement: we agree up front what we're measuring, report what actually recovered, and you can stop if the numbers aren't there.