Configuration
How dunning retry policies are structured.
Dunning configurations are named retry policies. The orchestrator selects a matching configuration for a failed subscription charge and snapshots it onto the campaign.
What a policy controls
- Which failed charges the policy applies to.
- Immediate retry behavior for transient gateway failures.
- Progressive retry behavior for card or funds failures.
- Escalation rules such as final notice, suspension, or cancellation.
- Communication channels and templates.
- Default payment-update token settings.
Immediate retries
Use immediate retries for failures that may clear quickly, such as timeouts, gateway errors, or processing errors. Keep these short and limited.
Progressive retries
Use progressive retries for customer-action failures, such as declined cards, expired cards, or insufficient funds. These retries should leave enough time for customer communication.
Escalation
Escalation rules decide what happens when recovery does not succeed. Typical actions are final notice, suspension, and cancellation.
Policy selection
Policies can target different scopes, such as organization, customer segment, subscription tier, customer, or experiment group.
Interval format
Retry intervals use duration strings such as 2m, 4h, or 3d.
API details are in Dunning API.