Smart retry schedules
Retry after payday for insufficient funds. Skip retry for expired cards. Timing adapts per decline code.
Payment Recovery
Recover failed payments with a real playbook
A renewal fails. Gruv retries at the right time, emails the subscriber with a one-click card-update link, and tracks whether the charge recovers or becomes churn.
Retry policiesGrace periodsRecovery visibility
Dunning · M1 cohort
Recovered 62.4%
Lost 7.1%
Day 1
Retry 1
card declined
Day 3
Card update sent
email opened
Day 5
Retry 2
insufficient funds
Day 7
Updater hit
new card · +$49
Day 8
Recovered
active · billed
At risk
$128,400
Recovered
$80,196
Remaining window
14 days
How it works
Where failed-payment recovery falls apart
Retrying at the wrong time wastes attempts
An "insufficient funds" decline on the 28th clears on the 1st after payday. A "card expired" decline never clears, no matter how many retries. Same retry schedule for both wastes attempts.
Subscribers never get a useful notification
The email says "your payment failed." No card-update link. No explanation. The subscriber ignores it and churns three weeks later.
Nobody knows who is in grace and who is about to churn
Support checks one system. Billing checks another. Is this subscriber in retry, in grace, or already cancelled? Three people, three answers.
You cannot measure what you cannot see
Which retry cadence recovers the most revenue? Which failure reason has the lowest recovery rate? Without analytics, you are guessing.
Dunning around retry, action, and visibility
Failed charges trigger the right retry at the right time, notify the subscriber with a card-update link, and track recovery vs. churn for your growth team.
Retry schedules per failure reason
Insufficient funds retries after payday. Expired cards skip retry and send an update prompt. You configure the timing per decline code.
Grace periods with escalation
The subscriber keeps access for 7 days while retries run. After grace expires, the subscription moves to the state you configured: pause, downgrade, or cancel.
Actionable subscriber notifications
Each email explains what failed and includes a one-click card-update link. No vague "payment failed" messages.
Capabilities
What recovery teams need
Grace periods
7-day or 14-day grace with continued access. Escalation to pause or cancel after expiry.
Subscriber notifications
Clear emails with one-click card-update links. Sent at the right cadence, not a single generic blast.
Recovery analytics
Recovery rate by failure reason, method, plan, and cohort. See exactly where involuntary churn originates.
Lifecycle sync
Billing, support, and your CRM show the same recovery status throughout dunning.
How it works
From failed charge to recovered or churned
More in Subscriptions
Related capabilities on the same workflow
Recurring Billing
Gruv automates recurring billing with predictable invoice timing, saved payment methods, and real-time charge status for
Pricing Models
Gruv lets your pricing team launch flat, tiered, volume, and usage-based plans from the dashboard, no engineering deploy
Lifecycle Management
Gruv tracks every subscription from trial to cancellation with clear state transitions, pause controls, and a timestampe
Frequently Asked Questions
How many retry attempts should we configure?+
It depends on the decline code. Insufficient funds may recover after 2-3 retries. Expired cards need a subscriber update, not more retries. Gruv lets you set the max per decline type.
What happens after all retries fail?+
Your policy decides. Move to grace, pause the subscription, offer a lighter plan, or cancel. You configure the escalation path per plan and segment.
Can subscribers update their card during dunning?+
Yes. Every notification includes a one-click link to a hosted card-update page. Gruv re-attempts the charge the moment the subscriber updates.
How do we know if our dunning is working?+
Track recovery rate by decline reason, payment method, retry attempt number, and subscriber segment. See whether each retry actually recovers revenue or just delays churn.
What does Gruv AI do across these features?+
Gruv AI automates payout routing, compliance gates, exception triage, and the Ask Gruv AI workspace. Every feature shares the same AI layer, so rules, holds, and reconciliation stay consistent.
Can I start with one feature and add more later?+
Yes. Gruv is modular. Start with one workflow and expand to additional modules as your needs grow.
How do I connect Gruv to our existing systems?+
Connect through APIs and webhooks, or start with file imports and exports for a fast evaluation. Email ingestion works for lightweight backfills.
What determines coverage, methods, and timelines?+
Coverage, methods, and timelines vary by market and are subject to compliance and policy checks. Confirm your target corridors and payout methods during evaluation.
Is this tax or legal advice?+
No. Tax and compliance features vary by jurisdiction and customer configuration. This content is for informational purposes and is not tax or legal advice.
Recover more revenue.
A renewal fails. Gruv retries at the right time, emails the subscriber with a one-click card-update link, and tracks whether the charge recovers or becomes churn.
Many teams start with a narrow launch in weeks.