Stripe

Connect

1. In NoChurn, test mode first, open Integrations and click Connect Stripe. NoChurn uses Stripe Connect: the API returns the Stripe URL (POST /v1/stripe_connections/authorize) and you approve access on Stripe.
2. NoChurn imports customers, subscriptions, invoices and payment methods, then follows Stripe’s events. POST /v1/stripe_connections/{id}/backfill runs the import again.
3. Choose who retries failed payments: Stripe (Smart Retries, the default) or NoChurn (PATCH /v1/stripe_connections/{id}).

Put your own user id in the Stripe customer’s metadata (metadata.user_id by default; the key is configurable) so that NoChurn links the Stripe customer to the one your app sends, instead of creating a duplicate. NoChurn never sees card numbers: only brand, last 4 digits, expiry and type.

What NoChurn does

Retries	Stripe retries the payment (its own retry settings). NoChurn sends the recovery emails.
Card update	The recovery emails link to a page NoChurn hosts for the customer to update the payment method.
Cancel flow offers	Applied in Stripe: discount, pause, downgrade. An offer the provider cannot apply reaches your backend as a billing.*_requested webhook.
Cancellation	A cancellation requested in the cancel flow is carried out in Stripe.
Disputes	NoChurn gathers the evidence and drafts the reply; a person reviews it before it is sent to the provider.
Events	NoChurn follows Stripe’s webhooks.
Import	The last 12 months are imported when you connect (POST /v1/billing_connections/{id}/backfill imports again).

What NoChurn reads

• Customers and subscriptions
• Invoices and payment attempts, with the decline code
• Payment method type, brand, last 4 digits and expiry (never the card number)
• Disputes and early fraud warnings

What stays with Stripe: card numbers and payment processing; your prices, products and invoices; your stripe account settings. More on the Stripe integration page.

← All integrations