Analytics
On first connect, Recurflux pulls 90 days of failed charges from your processor and shows you exactly how much revenue you have already lost and what your current recovery rate is. The number makes every setup step that follows obvious.
90 days
Of failed charge history pulled on first connect
Read-only
Sync — nothing in your processor is modified
Under 60s
For most accounts to see their full history
Quick answer
Historical sync pulls 90 days of failed charge data from your processor on first connect. Recurflux shows recovered revenue, lost revenue, baseline recovery rate, and failure code distribution before any configuration is complete. The sync is read-only, takes under 60 seconds for most accounts, and informs retry logic from day one.
The problem
Most payment processors show you individual failed charges but not your aggregate recovery rate or total revenue lost over time. Without that number, the cost of inaction is invisible.
Without historical sync
With Recurflux historical sync
How it works
01
You connect Stripe, Paddle, Razorpay, Cashfree, or RevenueCat in settings. The connection takes under 60 seconds — OAuth or API key, depending on the processor.
02
Recurflux immediately begins pulling the last 90 days of failed charge data from your processor's API. No manual trigger, no configuration required.
03
The recovery dashboard shows: total revenue lost in the last 90 days, your current recovery rate, most common failure codes, and the MRR at risk from currently active failures.
04
Your failure pattern — which codes, at what frequency, at what amounts — is used to set initial retry rule suggestions for your account. You can accept defaults or adjust.
What you see
01
Total revenue from failed charges in the last 90 days that was never recovered. This is the number that makes the cost of inaction concrete.
02
The percentage of failed charges that were eventually recovered — before Recurflux. Your starting point. Everything from here is measured against this.
03
The 90-day history broken down by decline code: insufficient funds, expired card, do_not_honor, and the rest. See which codes are driving the most lost revenue.
Recover charges from the last 90 days. Connect and start working your backlog immediately.
See how this works →FAQ
Failed charges from the last 90 days: customer name, amount, failure code, date, and whether the charge was eventually recovered or lost. Recurflux uses this to calculate your baseline recovery rate and total revenue lost before any optimisations.
Most accounts sync in under 60 seconds. Accounts with a very large volume of historical failures may take a few minutes. The dashboard shows a loading state and updates as data comes in.
No. The sync is read-only. It pulls historical data from your processor's API and populates the Recurflux dashboard — no charges are triggered, no subscriptions are modified.
Yes. Your historical failure pattern — which codes appear most often, at what amounts, on which billing dates — informs how Recurflux structures retry logic for your account from day one.
Stripe, Paddle, Razorpay, and Cashfree. RevenueCat also supports a historical sync, showing failed billing attempts and grace period events from the last 90 days.
Related features
Analytics
The dashboard the historical sync populates — your baseline and every metric that follows.
Recovery
Historical failure patterns inform how retry rules are configured for your account.
Recovery
Historical sync shows how many past failures were expired card — card monitoring prevents them going forward.
Works with your processor
Live in under 5 minutes