Key takeaways
- Distinguishes involuntary churn from voluntary cancellations for accurate revenue reporting.
- Automated retries with backoff intervals maximize recovery without annoying users.
- Clear user communication during dunning improves update rates and reduces support tickets.
- Failed payment recovery protects recurring revenue streams for SVOD and PPV models.
How Dunning works
When a payment fails, the billing system triggers a dunning sequence. This is not a single retry. It is a scheduled series of attempts over days or weeks. The system logs the failure reason, such as expired card or insufficient funds. It then retries the charge at specific intervals. Common patterns include retries on day 1, day 3, and day 7. Between attempts, the platform sends notifications to the user. These messages explain the failure and provide a direct link to update payment methods. If all retries fail, the system may suspend access or cancel the subscription. The exact behavior depends on your business rules. Some operators keep content accessible during the grace period. Others lock the account immediately. The goal is to recover the payment while maintaining user trust. You configure the retry schedule and message templates in your billing settings. The system handles the technical execution and status tracking automatically.
Why Dunning matters for a streaming business
Involuntary churn is a silent revenue leak. Many subscribers do not intend to cancel. They simply have a bank issue or an expired card. Without dunning, these users leave your platform permanently. You lose the recurring revenue and the marketing cost to acquire them. Dunning recovers a significant portion of these lost accounts. It also improves your data quality. You can separate true cancellations from payment failures. This distinction matters for churn rate analysis. If you see a spike in cancellations, dunning data tells you if it is a payment processor issue or a content problem. It also reduces support load. Users who receive clear instructions to update their card are less likely to call support. They fix the issue themselves. This keeps your support team focused on complex problems. For operators, dunning is a retention tool, not just a billing feature. It protects your MRR and LTV metrics.
Common mistakes with Dunning
Operators often misconfigure dunning sequences. Here are frequent errors:
- Too few retries: One or two attempts miss many recoverable payments. Users need time to resolve bank issues.
- Vague messaging: Saying "payment failed" without explaining why or how to fix it leads to confusion. Provide clear next steps.
- Immediate suspension: Locking content before the first retry frustrates users. They may have forgotten their card expired. Give them a grace period.
- Ignoring failure reasons: All failed payments are not the same. Expired cards need updates. Insufficient funds need time. Tailor your approach.
- No analytics: If you do not track dunning success rates, you cannot optimize your sequence. Monitor recovery percentages regularly.
How Flicknexs handles Dunning
Flicknexs integrates with more than 90 payment gateways to handle billing transactions. The platform supports subscription management, including SVOD and AVOD models. When a payment fails, the event is reported through the payment gateway and webhooks, and it appears in the analytics dashboard. You can manage user billing details through the video CMS and analytics dashboards. The operator runs recovery through the gateway or their own tooling. This helps you reduce involuntary churn and maintain stable recurring revenue. For details on setting up your billing and payment workflows, visit the Create your own OTT platform page.
Done reading about Dunning?
Flicknexs ships it as part of a white-label streaming platform: web, mobile and TV apps, billing, ads, DRM and playout, on your own domain.