INTEGRATIONS

Integrations

Connect Stripe, a billing platform, a merchant of record, a payment provider, an app store or a help desk, or send everything through the API.

NoChurn reads your billing from Stripe, another billing tool, or your own code. Help desks add their conversations on top. Connect them from Integrations in the dashboard, test mode first; GET /v1/billing_providers lists the billing tools with their guide.

What each tool lets NoChurn do differs: who retries a failed payment, whether there is a page to update the card, which offers can be applied, and whether disputes can be answered. Each page below says it, from the same table NoChurn’s code reads.

Most used

Billing platforms

Merchants of record

They collect the payment and answer disputes themselves; NoChurn adds the cancel flow, win-back, the churn score and your data.

Payment providers

App stores

Apple and Google keep the payment, the retries and the cancel button. NoChurn reads every subscription change; customers are linked only when your app passes its user id at purchase.

Your own billing system, by webhooks

  • Custom billing: NoChurn reads the webhooks your billing system already sends, through a mapping you test on a sample.

Help desks

Read only. Conversations are matched to customers by email and used in the churn score, the churn drivers and dispute evidence.

Your user id in each tool

NoChurn reads your own user id (external_id) in each billing tool at one place: Stripe’s customer metadata.user_id by default (external_id_metadata_key on the account), or the field you set on the connection (internal_id_field, PATCH /v1/billing_connections/{id}). With it, a customer from the tool is linked to the one your app sends instead of becoming a duplicate.