Questions, answered.

We connect via Stripe’s standard OAuth flow — Stripe shows you the exact permissions on the consent screen before you approve. We read your customers, subscriptions, and cancellation events so we can detect churn and compute MRR. We use writeaccess for one purpose only: renewing a subscription when a customer accepts a winback offer — we never create new subscriptions out of nowhere, never refund, never change prices. You can disconnect us any time from Stripe Dashboard → Apps.

No. We never create charges, never issue refunds, never change prices or plan configurations. The only write action we take is renewing a cancelled subscription when a customer clicks your winback offer — and that only restores what they previously had.

We stop receiving cancellation events immediately and stop sending emails. Nothing on your Stripe side changes — your subscriptions, customers, and prices are untouched.

On servers in the US (AWS us-east-2), under EU Standard Contractual Clauses. The full list of subprocessors is at /subprocessors.

One exit email at cancellation to capture the reason for leaving. Then, if you later ship a product improvement that matches that reason within the follow-up window, the subscriber gets one follow-up email naming what they asked for and what you delivered. That’s it — no drip sequences, no AI replies.

One exit email at cancellation, plus at most one follow-up per shipped match — never a drip sequence. Payment-recovery emails (up to three, timed to lead Stripe’s automatic retries) stop the moment Stripe collects. Every email carries a visible unsubscribe link plus the List-Unsubscribe header for one-click unsubscribe in Gmail and Outlook.

Your name on the From line, from our verified sending domain. Replies go to your normal inbox — WinbackFlow doesn’t intercept the conversation or auto-respond. From there it’s a direct conversation between you and the subscriber.

Yes. From Reasons (top-nav) you can select a single Stripe promotion code at a time to offer with winback emails (or skip — many merchants find a personal-sounding email outperforms a discount). Switching the active code is one click.

Before showing the code to a subscriber, WinbackFlow verifies four gates against Stripe in real time:

• The promotion code is active in Stripe.
• It hasn’t passed its redemption deadline.
• It hasn’t hit its max-redemptions cap.
• It applies to the price the subscriber was on.

If any gate fails, the email goes out without the offer rather than leading the customer to a broken checkout.

One thing you have to set up on the Stripe side: make sure your cancelled customers are eligibleto redeem the code. We verify the four gates above, but we can’t override Stripe’s customer-eligibility rules at checkout:

• Don’t tick “First-time transaction only”on the coupon — your cancelled customers have already paid you before.
• If you’ve restricted the code to a specific customer list, make sure the cancelled cohort is in it.
• Currency, region, and product/price restrictions still apply at Stripe checkout.

Skip these and the customer clicks through to a Stripe checkout that says “This code is not valid” — not WinbackFlow’s rejection, Stripe’s. Worth a 30-second sanity check when you create the code.

Unsubscribes are honoured immediately — we flag the subscriber and never email them again. For full deletion under GDPR Article 17, email privacy@winbackflow.co and we’ll delete them from our database within 30 days. Details in our Privacy Policy.

One flat monthly fee priced by your own MRR. No per-recovery charges, no performance fees, no usage caps.

• Starter — MRR up to $50k — $99 / month
• Growth — MRR $50k – $250k — $299 / month
• Scale — MRR $250k – $1M — $699 / month
• Enterprise — MRR $1M+ — custom, sales-handled

See full pricing →

No card at signup. WinbackFlow runs free until we deliver your first payment recovery or cancellation winback. Only then do we prompt you in-app to confirm your tier and subscribe. If we deliver nothing, you pay nothing.

Yes, but never automatically. We re-compute your MRR weekly. If it grows into a higher tier and stays there for 14 days, you’ll see an upgrade prompt in your dashboard and settings. Same for downgrades. In both directions, you decide — the Stripe Customer Portal handles the switch.

One-click cancel via your billing settings — no retention friction. The subscription ends at the close of your current cycle. Your data stays intact, and WinbackFlow keeps running for free. The next delivered recovery will prompt you to re-subscribe at the tier matching your then-current MRR.

Yes — roughly half the lost revenue most subscription businesses leave on the table. When a card fails we send a three-touch email sequencetimed to lead Stripe’s automatic retries (immediate, ~24h before retry #2, ~24h before the final retry), each with a one-click update-payment link. Auto-stops the moment Stripe collects.

These are rule-based decline-aware emails — not AI-written. Everything shows up in the same dashboard as cancellation winbacks, tagged so you can tell them apart.

Yes — we operate as a data processor under Article 28. See our DPA, Privacy Policy, and Terms for breach notification, subprocessor management, and data-subject rights.