Churnor
Connect Stripe to Churnor
Bring subscription and payment signals into your customer risk workspace. Set up a signed webhook and verify its delivery.
Stripe customer data
Connect your SaaS customers' subscription and payment events to Churnor with signed Stripe webhooks. You need a Churnor product environment and access to your Stripe account's webhook settings. This connector receives customer billing signals; it is separate from paying for a Churnor plan.
- Open Dashboard → Integrations → Stripe and copy the environment's endpoint URL.
- In Stripe Workbench → Webhooks, create an event destination for your account. Choose a webhook endpoint, use snapshot events, enter the copied URL, and select the event types below.
- Reveal the destination's signing secret and save it in Churnor. Use the same test/sandbox or live environment for the endpoint and secret.
- Deliver or replay a supported signed event. Select Check delivery / Retry verification in Churnor. Saving a secret leaves the connector awaiting its first event; successful processing verifies delivery.
Endpoint: /api/webhooks/stripe?project_id=<YOUR_PROJECT_ID>
Subscription and payment events to select
customer.subscription.createdcustomer.subscription.updatedcustomer.subscription.deletedinvoice.payment_failedinvoice.payment_succeeded
Match billing to customer activity
Use the Stripe customer ID (cus_…) as customer_id in Events API requests and CSV imports for this environment. The connector uses that Stripe ID as the customer's external ID. It does not map an application ID from churnor_customer_id or merge customers by email.
What arrives, and what does not
Supported deliveries update available customer details, subscription signals, and recurring revenue when the payload provides it. Billing deliveries are not counted as product activity. Send product events separately to measure usage.
Registering an endpoint receives future changes; it does not fetch existing subscriptions or backfill historical activity. Use CSV for initial customer records. Recurring revenue reflects the supplied billing data, not a guaranteed net-revenue reconciliation.
Troubleshoot delivery
Check the endpoint's project ID, selected event types, signing secret, and test/live environment. Review Stripe delivery logs, correct the configuration, and replay a supported event. Duplicate event IDs are handled without storing another copy. Rotating the secret resets Churnor's verification status.