Implementation
How dunning fits into a billing implementation.
Implementation is about deciding how failed-payment recovery should behave in your product. The API details are separate.
1. Choose a recovery policy
Define how many retries should run, how quickly they should run, and when the customer should be suspended or cancelled. Keep the policy simple until you have real recovery data.
See Configuration.
2. Connect billing failures to recovery
When a recurring charge fails, GetPaidHQ opens or updates a campaign for that subscription. Treat the campaign as the recovery record your support and customer-facing UI can show.
3. Show recovery state
Expose clear states to operators: active recovery, paused recovery, recovered, cancelled, or exhausted. Do not make support staff infer state from payment failures alone.
4. Support manual intervention
Support needs a way to pause a campaign, resume it, cancel it, or trigger a manual retry after a customer says their payment method is fixed.
5. Add payment-update links
Use payment-update tokens for customer-facing recovery links. The token should let the customer update payment details without giving them access to an admin session.
API details are in Dunning API.