Your payment processor is the billing platform where your subscriptions and customers actually live. Connecting it lets churn.io read a subscriber's plan when they try to cancel and apply retention offers — discounts, pauses, free months, and plan changes — directly to their live subscription, then carry out the cancellation if they still leave. This article covers connecting Stripe, the access we request, and disconnecting.
Supported payment processors
Stripe is fully supported today. You can connect it in a couple of clicks and start applying offers to real subscriptions.
These processors appear on your Integrations page marked Coming soon and can't be connected yet:
Chargebee
Recurly
Braintree
Adyen
Mollie
Don't see your billing platform? Use the Request integration button on the Integrations page to let our team know.
💡 Why connecting matters
Without a connected processor, your cancel flow can show surveys and offers, but it can't apply a discount or pause, or cancel the subscription. That's why churn.io requires a connected Stripe account before a flow can go live or an A/B test can start.
Who can connect a processor
Only members with the right permissions can view and manage integrations: you need an Owner, Admin, or Developer role. Members and viewers will see an "access restricted" message instead of the integrations grid.
Integrations are connected per business. If you manage more than one business, make sure the correct one is selected before you connect — the connection only applies to the business that's currently active.
Connecting Stripe
churn.io connects to Stripe through the Stripe Marketplace using a secure authorization flow — there are no API keys to copy or paste. You simply approve the connection inside your own Stripe account.
Step 1: Open Integrations
In the sidebar, go to Integrations.
Find the Stripe card in the grid and click Connect.
Step 2: Launch the Stripe Marketplace
In the Connect Stripe dialog, click Install from Stripe Marketplace.
You'll be taken to Stripe to review and approve the connection.
Step 3: Approve and return
Sign in to Stripe if prompted, choose the account you want to connect, and approve the requested access.
Stripe sends you back to churn.io, where you'll see a brief Connecting your account screen while we finish the setup.
Once it reads Stripe connected, you're returned to the Integrations page and the Stripe card now shows a green Connected badge with your account name.
⚠️ If the connection fails
If Stripe returns an error, you'll see a "Something went wrong" screen with a Back to Integrations button. Return to Integrations and click Connect to try again. Always start the connection from within churn.io so it can match the result to your account securely.
What access churn.io requests
During the Stripe approval step you'll be asked to grant a focused set of permissions. churn.io requests only what it needs to act on the offers you've configured:
Read customer and subscription details, to identify who is cancelling and show their plan.
Update, pause, and cancel subscriptions, to action accepted offers and confirmed cancellations.
Read and create coupons, to apply discount and free-month offers without creating duplicates.
Read product and invoice data, to display subscription information and calculate saved revenue.
Your credentials are encrypted and stored securely, and are never shown back to you or your team after connecting.
After you connect
Once Stripe is connected, churn.io reviews your recent subscription history so your usage and saved-revenue figures can be calculated, and your flows and A/B tests can now go live and apply offers to real subscriptions.
Disconnecting a processor
To remove a connection, go to Integrations, find the connected Stripe card, and click Disconnect. The card returns to its unconnected state, and you can reconnect at any time by clicking Connect again.
⚠️ Disconnecting stops offers from being applied
While no processor is connected, your flows can't apply discounts or pauses, or cancel subscriptions through Stripe. Reconnect before relying on your flows again.