Prompt
How do I manage retries and dunning for failed payments?
Latest observation
To manage retries and dunning for failed payments effectively, you want a system that is policy-driven, customer-friendly, and data-aware.
1) Separate failure types
Not all failed payments should be handled the same way.
- Soft declines: temporary issues like insufficient funds, network errors, card issuer unavailable
- Retry these
- Hard declines: expired card, stolen card, invalid account, closed card
- Don’t keep retrying blindly; prompt for updated payment details
- Fraud / disputed / blocked:
- Stop retries and route to manual review or customer support
2) Use a retry schedule
For soft declines, use a staggered retry strategy rather than hammering the card.
A common pattern:
- Retry after 1 day
- Then 3 days
- Then 5–7 days
- Stop after 3–5 total attempts
Best practices:
- Retry at times when funds are more likely to be available
- Vary timing by reason code if your PSP provides them
- Avoid retrying too frequently, which can increase issuer rejection and customer frustration
3) Set dunning stages
Dunning is the customer communication process around failed payments.
Typical flow:
- Immediate notification after failure
- Reminder before account impact (“payment due, we’ll retry soon”)
- Warning before service restriction
- Final notice before suspension/cancellation
Include:
- Amount due
- Reason for failure, if appropriate
- Clear CTA to update payment method or pay now
- Next retry date
- Support/contact option
4) Automate payment method updates
Make it easy for customers to fix the issue:
- Update card on file
- Wallet / ACH / alternative payment methods
- Card updater service, if available
- Hosted self-serve billing portal
The faster customers can update details, the fewer retries you need.
5) Segment by customer value and risk
You may not want the same policy for everyone.
Examples:
- High-value / enterprise customers: more retries, longer grace period, human outreach
- Low-value / self-serve: fewer retries, more automated dunning
- High-risk or high-chargeback segments: tighter controls and faster suspension
6) Track important metrics
Monitor:
- Retry recovery rate
- Dunning email open/click-to-pay rate
- Time to recovery
- Recovery by decline reason
- Churn after failed payment
- Chargeback/dispute rate
- False-positive hard decline rate
This helps you tune retry timing and communication.
7) Respect compliance and customer experience
- Be transparent about billing terms
- Don’t over-communicate
- Follow local laws on recurring billing, notices, and grace periods
- Keep retry logic and communication preferences configurable
8) A practical default policy
If you need a starting point:
- Attempt 1: at invoice/renewal date
- Attempt 2: +1 day
- Attempt 3: +3 days
- Attempt 4: +5 days
- Dunning emails: day 0, day 2, day 5, final notice before access change
- Suspend service: after final retry window ends
- Cancel: after a defined grace period, depending on your business rules
9) If you use a payment provider
Many providers support:
- Automated retry scheduling
- Smart retry optimizations
- Decline code classification
- Billing portals
- Card updater tools
- Dunning webhooks / events
If you tell me which provider you use, I can suggest a concrete implementation pattern.
If you want, I can also help you design:
- a retry policy table
- a dunning email sequence
- or a database/state machine model for failed payments.