Dunning Management
Failed payment recovery and retry configuration for subscription billing
Dunning Management
GetPaidHQ provides dunning management capabilities to handle failed payment recovery through configurable campaigns and retry strategies.
Overview
Dunning management handles the process of recovering failed payments through:
- Automated retry attempts with configurable timing
- Customer communication campaigns
- Payment method update workflows
- Campaign analytics and reporting
How Dunning Works
When a payment fails, GetPaidHQ can automatically:
- Categorize the failure type (technical, decline, insufficient funds)
- Apply appropriate retry strategies based on failure reason
- Send customer communications with payment update links
- Track recovery attempts and outcomes
- Generate analytics on campaign performance
Core Components
Configuration
Set up dunning campaigns, retry schedules, and communication rules
Communication
Customer notification templates and messaging configuration
Payment Updates
Secure payment method update workflows for customers
Analytics
Campaign performance tracking and recovery metrics
Dunning Campaigns
Campaigns define the recovery strategy for failed payments:
Campaign Configuration
- Timing: Specify retry intervals (immediate, hours, days)
- Attempts: Configure maximum retry attempts
- Communications: Set up customer notification schedules
- Conditions: Define when campaigns should trigger
Campaign Lifecycle
- Trigger: Payment failure occurs
- Categorization: Failure type is determined
- Strategy Application: Appropriate campaign is selected
- Execution: Retry attempts and communications are sent
- Resolution: Payment succeeds or campaign completes
Campaign Types
- Immediate Retry: For technical failures and temporary issues
- Progressive Engagement: Graduated customer outreach over time
- Grace Period: Allow account access during recovery period
- Final Notice: Last attempt before subscription cancellation
Payment Recovery Methods
Automatic Retries
Technical failures are retried automatically:
- API timeouts: Immediate retry
- Network errors: Exponential backoff
- Gateway issues: Delayed retry with alternative routing
Customer-Initiated Updates
For declined payments, customers can:
- Update payment methods via secure links
- Add backup payment methods
- Resolve account issues directly
Manual Recovery
Support teams can:
- Trigger manual retry attempts
- Override campaign settings
- Apply custom recovery strategies
Implementation
Campaign Setup
Configure dunning campaigns and retry strategies
Integration Guide
API integration patterns and webhook handling
Recovery Strategies
Best practices for different failure scenarios
API Integration
Dunning operations are managed through dedicated API endpoints:
/api/dunning/campaigns
- Campaign management/api/dunning/configurations
- Settings and rules/api/payment-tokens/verify
- Payment update verification/api/customers/{id}/dunning-history
- Customer recovery history
Monitoring and Analytics
Track dunning performance with built-in analytics:
- Recovery rates by failure type
- Campaign effectiveness metrics
- Customer communication engagement
- Revenue recovery attribution