Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update revenue-recovery.md #79

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update revenue-recovery.md #79

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion explore-hyperswitch/payment-flows-and-management/subscriptions/revenue-recovery.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ Revenue Recovery module of Hyperswitch is designed to act as a failsafe for recu

### **Why is Revenue Recovery Important?**

For subscription-based businesses, involuntary churn from failed recurring payments can significantly impact revenue. Payment failures may result from insufficient funds, fraud checks, or issuer restrictions. A simple dunning setup is not effective in retrieving these failed payments. Revenue recovery’s Intelligent retry engine analyzes 30+ transaction parameters to find best retry strategy to recover the given payment.
For subscription-based businesses, involuntary churn from failed recurring payments can significantly impact revenue. Payment failures may result from insufficient funds, fraud checks, or issuer restrictions. A simple dunning setup is not effective in retrieving these failed payments. Revenue recovery’s Intelligent retry engine analyzes 20+ transaction parameters to find best retry strategy to recover the given payment.

### Benefits for SaaS Businesses

Expand Down