From a failed charge to a paid invoice
- 01
Create the key
Our button opens Stripe's “Create restricted key” form with six permissions ticked: invoices (write, to retry), and read-only charges, customers, subscriptions, events, payment intents.
- 02
Scan 90 days
Open invoices charged automatically with at least one failed attempt, the decline code of each, and subscriptions Stripe cancelled for non-payment. Nothing is written, nobody is emailed.
- 03
Choose
Recovery sweep ($49 once) chases what is stuck today for 30 days. Pro chases today's backlog and every future failure. Pay with an email, no account.
- 04
The sequence runs
Day 0, 1, 3, 5: an email written for the decline reason, under your brand and reply-to. Retries only where the bank can say yes. Day 7: stop.
- 05
It stops by itself
Every few minutes we read your Stripe events. The moment an invoice is paid (by us, by Stripe's retries, or by the customer), the sequence ends.
The schedule, exactly
Read from the file the worker runs. Two actions on the same invoice are never less than 20 hours apart.
| Step | After failure | Soft decline / funds | New card / 3-D Secure / expired |
|---|---|---|---|
| Day 0 | 0 h | Email only | |
| Day 1 | 24 h | Retry (not for funds) + email | Email only |
| Day 3 | 72 h | Retry + email | Email only |
| Day 5 | 120 h | Retry + email | Email only |
| Day 7 | 168 h | Stop | Stop |