How can we help?

Go to Settings → Integrations in your dashboard and paste a restricted Stripe API key (we show you exactly which permissions to enable — read access to invoices and subscriptions, nothing more). Then add the webhook endpoint URL we give you in your Stripe dashboard under Developers → Webhooks. The whole thing takes about five minutes, and Recoverly starts watching for failed payments immediately. No code changes to your product, nothing to install.

When a subscription payment fails, the customer automatically enters your recovery sequence: a friendly reminder on day 1, a firmer nudge on day 4, and a final notice on day 7. Every email links to your branded card-update page and is sent from your own sender address, so it reads like it's from you — not a third party. You can edit the subject and body of each email, use variables like {{first_name}} and {{amount}}, and toggle any email on or off. As soon as the payment succeeds, the customer leaves the sequence automatically.

It's a hosted, mobile-friendly page carrying your logo and brand color. When a customer clicks the link in a recovery email, they land here, enter their new card details, and Stripe updates the payment method on their subscription directly — your subscription resumes without you lifting a finger. We never see or store full card numbers; that all happens inside Stripe's secure fields. You get a notification every time a card is updated.

We use Stripe's official API and follow their integration security guidelines: API keys are stored encrypted, we request the minimum permissions needed, and card data never touches our servers — it's handled entirely by Stripe. That said, we're a new product, and we'd rather be straight about that than wave certifications we don't have yet. If you're evaluating us for a larger volume business, email us and we'll walk through our security practices in detail.

$29/month, flat. One plan, everything included: unlimited recovery sequences, the branded card-update page, the recovered-revenue dashboard, and email support. No per-recovery cut, no tiers, no "contact sales." We deliberately priced it at a tenth of the enterprise tools because we're built for independent subscription businesses, not Series C finance teams.

We bill the $29/month subscription through PayPal — hit "Start recovering revenue" on the pricing page and you'll check out securely. No charge until you subscribe, obviously.

Yes. One click in Billing, effective immediately, no retention calls and no dark patterns. Your recovery sequences stop the moment you cancel — any customer mid-sequence simply won't receive further emails.

Your workspace data — customers, sequence history, recovered-revenue records — is kept for 90 days in case you come back, then permanently deleted. You can export everything (CSV) any time before canceling from Settings → Data. We don't sell data, we don't keep it longer than stated, and we don't make you email us to delete it.

Work through this list in order: (1) confirm the sequence is toggled on in Email sequences; (2) check your sender email is verified — unverified senders get silently dropped, and your domain needs SPF/DKIM records (we show the exact DNS entries in Settings → Sending); (3) open the send log for the customer — bounces and spam complaints are listed per email; (4) make sure the customer hasn't unsubscribed from a previous email. If the log shows sends but nothing arrives, it's almost always the DNS records.

The usual culprits: a typo'd or over-restricted API key, or the webhook endpoint not responding. Re-paste the key (make sure it's a restricted key with the permissions we list, not your publishable key), then in your Stripe dashboard check Developers → Webhooks that our endpoint URL is present and returning 200s — Stripe shows recent delivery attempts right there. If you see red X marks, delete the endpoint and re-add it from our setup page.

A payment counts as "recovered" when a previously failed invoice gets paid within 30 days of entering a sequence — that's the definition behind every number on the dashboard. The two common mismatches: (1) test mode vs live mode — make sure you're looking at the right one in the workspace switcher; test payments never count; (2) failed-date timezones — Stripe timestamps are UTC, so a failure at 11pm ET shows as the next day. If it still looks off, send us a screenshot via the form below and we'll dig in.

Use the contact form below — it reaches a human (currently: the founder), and we reply within one business day, usually faster. Live chat is coming soon; when it launches it'll appear on every page of the app.