Industry Applications

Use the same dunning primitives in every industry: retry schedules, communications, escalation rules, and payment-update tokens. Adjust the policy to match the customer relationship and the cost of failed recovery.

SaaS subscriptions

• Use a longer progressive retry schedule for high-value accounts.
• Start customer communication before suspension.
• Set suspend_after_attempt before cancel_after_attempt.

Usage-based billing

• Keep the subscription active while usage invoices are in recovery if your product can tolerate delayed payment.
• Use campaign history to decide when support should intervene.

Consumer subscriptions

• Keep token expiry short.
• Use fewer retry attempts for low invoice amounts.
• Make cancellation timing explicit in the final notice template.

Enterprise billing

• Use customer- or segment-scoped configurations for named accounts.
• Route campaign history into your support workflow.
• Prefer manual review before cancellation.