Dunning Management
Failed-payment recovery with campaigns, retry attempts, configurations, and payment-update tokens.
Dunning starts when a subscription charge fails. GetPaidHQ opens a campaign for the failed payment, records retry attempts, and can issue payment-update tokens so the customer can fix their payment method.
What it is
Dunning is the recovery process for a failed recurring charge. It keeps the subscription problem visible, retries payment, records what happened, and gives the customer a way to update payment details.
Core objects
- Campaign: recovery state for one failed subscription charge.
- Configuration: retry policy and escalation rules.
- Attempt: one automatic or manual retry.
- Communication: customer message history for the campaign.
- Payment-update token: limited link token used by a customer-facing update flow.
Configuration
Create and update retry policy records
Payment Updates
Verify, activate, and create payment-update tokens
Analytics
Read campaign, attempt, communication, and customer history data
Recovery Logic
How retry campaigns progress
Where it fits
Dunning starts after subscription billing fails. It sits after payment processing and before account suspension or cancellation. It should be connected to customer communication, support workflows, and payment-method update screens.
API details are in Dunning API.