Collect the Stripe invoices your retries gave up on.
Recurback's AI recovery engine works the unpaid invoices Stripe stopped retrying, through every payment method your customers saved.
- Charges
- None — read only
- Your key
- Encrypted, revocable
- Paid to
- Your own Stripe
Statement of recoverable revenue
Sample account · invoices Stripe stopped retrying
Illustrative
- Statement
- No. 0417
- Period
- Last 90 days
- Page
- 1 of 1
- Written off
- $1,244.00
- Recovered
- $208.00
- Settling
- $240.00
| Invoice | What happened | Status | Amount | ||
|---|---|---|---|---|---|
| INV-2041Card declined → second card on file | Card declined → second card on file | Settled | +$129.00 | ||
| INV-2057Card expired → PayPal on file | Card expired → PayPal on file | Settled | +$79.00 | ||
| INV-2063Insufficient funds → SEPA debit | Insufficient funds → SEPA debit | Settling | $240.00 | ||
| Recovered this period | Recovered this period | $208.00 | |||
- recovered for subscription businesses
- $4.9M+
- unpaid invoices collected
- 60.3K+
- subscriptions back to active
- 52.5K+
Why that money is still sitting in your Stripe account
Day 0: A payment fails
A card expires or a balance runs short. The invoice is marked unpaid.
Days 1–21: Stripe retries the same card
A few attempts on the one method it was given, then it stops.
Day 22+: The invoice sits there
Still owed, often still collectable — and quietly written off. This is where Recurback starts.
Three steps to your first recovery
- 1
Connect your Stripe account
Paste a restricted API key you can revoke at any time. Nothing is migrated and your billing setup doesn't change.
- 2
Read your free statement
A scan reads every unpaid invoice and shows what's recoverable, what the banks already refused, and what's genuinely lost — without charging anyone.
- 3
Recover it when you're ready
Start a live run. It works the backlog under the limits you set and keeps going until every invoice is covered. You can stop it at any moment.
What a run does, line by line
Not a reminder sequence. Each unpaid invoice is handled on its own, and the next step comes from what the bank said about the last one.
- Every saved payment method, in order
- Stripe retries the card that failed. Recurback tries the customer's other saved methods — cards, Apple Pay and Google Pay, Link, PayPal, Revolut Pay, ACH, SEPA, Bacs and BECS debits, UPI and more — and stops at the first that clears.
- Reads why each payment failed
- An expired card, insufficient funds and a hard decline are different problems. The AI recovery engine reads what the bank said and handles each one differently.
- Brings subscriptions back, not just invoices
- When a past-due subscription's invoice clears, the subscription returns to active — reported as monthly revenue restored, not a one-off payment.
- Protects your customers
- Cooldowns between attempts, limits per invoice and per customer, and invoices left alone when the customer is paying elsewhere or has cancelled.
- Gentle on your systems
- Pace a live run to a set number of charges a minute, or pause chosen webhooks while it runs — switched back on automatically, with a list of what they missed.
- Numbers that are literally true
- A bank debit counts as recovered only once it settles. Scans never count toward your plan. What's still owed is never shown as earned.
For the people around the money
Finance wants the numbers, the team wants to know when a run lands, and some customers need a nudge no retry can give.
- Colleagues, read-only
- Invite people on your own company email domain to see runs and reports. They can't start runs, change settings, or see your key or billing.
- Run updates in Slack
- A message when a run starts and when it ends — totals only, never a customer's name or email.
- A nudge for customers no retry can reach
- No card on file, or an expired one: have Stripe email those customers their invoice with a link to pay. Off until you switch it on.
- Reports for finance
- Recovered money and subscriptions restored, month by month, plus every invoice from every run as a CSV.
Fee schedule
A flat monthly price, chosen by how much you recover in a calendar month — never a percentage, and no charge per seat. The first $500 a month is free.
| Plan | Recovered each month | Monthly fee | Choose |
|---|---|---|---|
| Free | Up to $500 | $0/mo | Start free |
| Starter | Up to $2,500 | $49/mo | Choose Starter |
| Growthrecommended | Up to $10,000 | $99/mo | Choose Growth |
| Scale | No limit | $199/mo | Choose Scale |
Scans are always free and never count toward a limit. Colleagues are free on every plan. Cancel whenever you like.
Important information about your account
- Nobody is charged by accident
- Every account starts with scans that charge no one. A live run is a separate switch, and the confirmation says plainly that real customers will be charged.
- Never charged twice
- Every attempt carries a unique key, so a resumed run can't take the same invoice twice — and one successful charge ends the attempts on that invoice.
- Your key, encrypted and revocable
- Held encrypted in a managed secrets store, never written to our database and never sent to a browser. Revoke it in Stripe and every run stops.
- Card data never touches us
- Payments stay inside Stripe. We never see, store or transmit a card number.
- The money never passes through us
- Every recovered payment settles in your own Stripe balance, on your own payout schedule.
- Your team sees, never touches
- View-only access is enforced by the API itself, not just hidden in the interface.
Questions
Doesn't Stripe already retry failed payments?
It does — a few times, on the one card that failed, and then it stops and the invoice sits open. Recurback starts where that ends and tries the customer's other saved payment methods instead of the same card again.
Can I see what would happen before anyone is charged?
Yes, and it's where everyone starts. A scan reads your whole backlog and reports what it would attempt and why each invoice went unpaid, without touching a single customer.
Will my customers be emailed?
Not by Recurback. If you switch it on, it can ask Stripe to send a customer their invoice when no retry can work — never more often than you allow. We also show you how to turn off Stripe's own failure emails before a live run.
Which payment methods can it use?
Any method your customer saved in Stripe that can be charged without them present: cards (including Apple Pay and Google Pay), Link, PayPal, Revolut Pay, Cash App Pay, Amazon Pay, Klarna, UPI AutoPay, and ACH, Canadian, SEPA, Bacs, Australian and New Zealand bank debits.
Can my team see the results?
Yes. Invite colleagues on your company email domain as read-only viewers. Running, settings, your key and billing stay with you.
How long does setup take?
A few minutes: paste a Stripe key, choose your limits, run a scan. No engineering work.
Does it work with my stack?
Recurback works with Stripe. Your plans, prices and invoices stay exactly where they are — nothing is migrated and nothing in your billing setup changes.
See what's still collectable in your own Stripe account.
- Time
- A few minutes
- Engineering
- None
- Billing
- Unchanged
Free on every plan