Failed payments, recovered politely.
Involuntary churn is quiet money: cards expire, banks hiccup, and customers who never meant to leave just stop paying. yRecurring opens a recovery run the moment a charge fails and works it, intelligently and politely, until the money is back or you decide otherwise.
- Day 0 Charge fails
Card declined on the renewal invoice. Nothing is emailed yet.
- Day 1 Smart retry
A retry at the hour most likely to clear, based on the failure code.
- Day 3 Personal email
An AI drafted note in your voice, with a one click payment link.
- Day 7 Grace period
The customer keeps access, sees a gentle banner, updates the card.
- Day 9 Recovered: $249.00
Paid in full. The whole thread is on the customer's timeline.
Retries that understand the failure.
- A temporary decline is retried on your schedule: you set how many attempts and how long to wait before each
- A dead card is never hammered: the run parks, the customer gets a one click link to update it, and collection resumes when they do
- A bank asking for confirmation (3DS/SCA) gets the customer a link to approve the payment, no blind retries
- Smart timing adapts to the failure type: a processing hiccup re-verifies within hours, insufficient funds waits for the start of the month, and every shifted retry records why
Polite to the person on the other end.
- Every dunning email explains the failure in plain language, never a raw bank code, and sends between 8:00 and 20:00 in your timezone
- AI drafts recovery emails in your voice; you read, edit, and press Send, and nothing reaches the customer before you do
- The customer keeps access during grace, sees a gentle banner in their portal, and fixes their card from one link
- Expiring cards get a friendly heads up before the renewal ever fails, once per card
You decide how it ends.
When the schedule runs out, nothing is destroyed by itself. Your setting decides: alert only, so the invoice stays open and owed; pause the subscription; write the invoice off; or cancel. Every attempt, retry, and recovery lands on the invoice and in the dunning console, which counts what was recovered, what is still at risk, and your recovery rate. A payment that arrives by any route closes the run as recovered.
Questions, answered.
What happens when a customer's payment fails?
yRecurring opens a recovery run against the invoice and starts collecting. Temporary declines are retried on your schedule, dead cards are not retried at all (the run waits for a new card instead), and a bank asking for confirmation gets the customer a one-tap link. The run tracks everything from the first failure to recovery.
Do you keep retrying an expired or stolen card?
No. A hard decline parks the run as awaiting card, because retrying a dead card burns attempts and annoys the customer. The customer gets a link to update their payment details, and collection resumes when they do. If you prefer, you can choose to retry hard declines on the schedule anyway.
What does my customer see during recovery?
The same truth, in friendlier words: the invoice's hosted page explains what happened and what happens next, the customer portal shows a banner while recovery is in progress, and every dunning email explains the failure in plain language, never a raw bank code. Emails send between 8:00 and 20:00 in your timezone.
What happens when the retries run out?
Your choice, set once in dunning settings: alert only (the default, the invoice stays open and owed), pause the subscription, write the invoice off, or cancel. Exhaustion never destroys anything by itself, and an invoice paid through any other route closes the run as recovered.
Can I change the retry timing?
Yes. You set how many retries and how long to wait before each one. On Grow and above, smart timing adapts to the failure type: a processing hiccup is re-verified within hours, and an insufficient-funds decline lines up with the start of the month. Every shifted retry records why it moved.
Recover the quiet money.
Turn it on once; it runs per invoice and reports what it brought back.