Getting started
RecoverIQ connects to your Stripe account and starts recovering failed payments automatically. No code changes, no ETL, no cards stored on our side. Here's what the first day looks like.
Install RecoverIQ
You have two paths, depending on where you're starting from:
From the Stripe App Marketplace
Open the RecoverIQ listing in Stripe, click Install, and approve the requested permissions. Stripe hands us a scoped OAuth token, we create your account, and you land directly on your RecoverIQ dashboard. No separate signup.
From recoveriqapp.com
Click Start Free Trial, create an account with email + password, then install RecoverIQ from the Stripe Marketplace via the onboarding screen.
What permissions does RecoverIQ need?
The Stripe OAuth flow asks for a specific set of scopes. In plain English, RecoverIQ needs to:
- Read failed invoices and payment intents — so we know which payments need recovery.
- Read customer and subscription metadata — so we can email the right person with the right context.
- Retry a payment — so we can attempt the charge again at the optimal time.
- Receive webhook events — so we react in real time when a payment fails, recovers, or a card expires.
RecoverIQ does not receive or store full card numbers. Stripe holds that data; we only see the last four digits for display. We never move money or initiate charges outside of retrying the exact failed payment.
Your first 24 hours
Minute 0 — connection complete
As soon as Stripe OAuth finishes, your dashboard is live. Metric tiles are zeroed until data rolls in.
Minutes 0–10 — webhook stream begins
Stripe starts sending live events to RecoverIQ. Any payment that fails from this point on is picked up immediately, classified, scheduled for retry, and queued for a dunning email.
Hours 1–24 — historical backfill
RecoverIQ scans your recent failed payments and imports any that are still within their recovery window. You'll see active cases appear on the dashboard as the import runs.
Day 1 onward — recoveries start landing
Retries are scheduled per decline category (see retry strategies). Most soft declines recover within 24–72 hours. Card-problem declines depend on how quickly the customer updates their payment method.
Next steps
- Review your email templates — defaults are sensible but your voice is better than ours.
- Pick a retry strategy if the default (Balanced) doesn't fit.
- Enable pre-dunning if you want to catch cards before they expire.
- Bookmark your dashboard — that's where recovery activity lives.
Still have questions?
Get in touch with support — we reply within 4 hours.
Contact us →