Connecting your Stripe account | RecoverFlow docs

Docs

Connecting Stripe

Reflects the code as of 28 July 2026. If the product changes and this page does not, that is a bug worth emailing about.

RecoverFlow connects to your Stripe account using Stripe Connect OAuth. You approve the connection inside Stripe's own interface, not ours, and you can withdraw it the same way without asking us.

What the connection allows

What it does not allow

Where the access token lives

The OAuth token is encrypted at rest before it is written to the database, so a database dump on its own does not yield a usable Stripe credential. Merchant records are isolated by tenant at the query layer.

More on the surrounding controls, including the certifications RecoverFlow does not hold, on the security page.

Revoking access

Go to your Stripe Dashboard, find RecoverFlow under connected applications, and revoke it. It takes effect immediately. You do not need to email anyone, and nothing further is billed beyond recoveries already attributed before that point.

This is the important bit: the off switch is on your side, in software you already trust, and it does not route through a retention conversation with us.

Common questions

Does RecoverFlow ever see my customers' card numbers?

No. Card data stays with Stripe. RecoverFlow references payment methods by ID and asks Stripe to attempt the charge, so card numbers never reach our servers. That is what keeps the platform in PCI SAQ A scope.

Can RecoverFlow cancel my customers' subscriptions?

No. The connection does not include changing or cancelling subscriptions. Whether a subscription cancels after failed payments is decided by your own Stripe subscription settings.

How do I disconnect RecoverFlow?

Revoke access from the connected applications section of your own Stripe Dashboard. It is immediate and does not require contacting us.

Is my Stripe token encrypted?

Yes, it is encrypted before being stored, so a database dump alone does not produce a usable credential.