ChurnNote

Stripe

Available

Connect with a read-only restricted key. ChurnNote registers its own webhook and starts detecting churn immediately.

Connecting takes about two minutes and gives you a free Churn Leak Report on your last 30 days. No card, and no signup needed to see the report.

The ChurnNote inbox showing $531 lost in the last 30 days, $551 still recoverable and $365 recovered, above a list of failed payments with decline reasons and monthly amounts.
Demo dataReal ChurnNote screen. Your report uses your own billing data.

What ChurnNote reads

  • Subscriptions: status, plan, amount, interval, start date, cancellation date
  • Invoices: payment failures, decline codes, and successful payments that close a recovery
  • Customers: name and email, so a follow-up can be addressed to a person
  • Products: the plan name shown next to each churned customer
  • Events: used to backfill your last 30 days on first connect

What ChurnNote cannot do

  • See full card numbers. Stripe never exposes them to any API key
  • Move money: no charges, no refunds, no payouts, no transfers
  • Modify or cancel subscriptions
  • Read anything a read-only restricted key does not grant
  • Keep working after you delete the key in Stripe

Permissions you grant

  • Account: Read
  • Customers: Read
  • Subscriptions: Read
  • Products: Read
  • Invoices: Read
  • Events: Read
  • Webhook Endpoints: Write (to register ChurnNote’s own endpoint)

Setup

  1. 1In Stripe, go to Developers → API keys → Create restricted key
  2. 2Grant the seven permissions above, and nothing else
  3. 3Paste the key into ChurnNote. Each permission is probed immediately, so a missing one is named on the spot instead of failing silently later
  4. 4ChurnNote registers its webhook and runs a Recovery Sweep of your last 30 days

Events ChurnNote listens for

  • customer.subscription.created
  • customer.subscription.updated
  • customer.subscription.deleted
  • invoice.payment_failed
  • invoice.paid

Security and key storage

  • The key is encrypted at rest and never displayed again after you paste it
  • It is excluded from your data export
  • It is deleted with your account
  • Revoking the key in Stripe cuts ChurnNote off immediately, with no action needed here

What this unlocks

  • Churn Leak Report on your last 30 days
  • Failed-payment recovery sequence
  • Cancellation follow-ups that get honest replies
  • Reply Intelligence and requests ranked by lost MRR
  • Ship-to-Recover win-backs

Questions

Why a restricted key instead of Stripe Connect OAuth?

OAuth would hand ChurnNote a token with far more power than reading churn requires, and revoking it is a support conversation. A restricted key is narrower, you can see exactly what it grants before you paste it, and you can revoke it yourself in one click.

Does ChurnNote need write access to my subscriptions?

No. The only write permission is Webhook Endpoints, used once to register the endpoint that tells ChurnNote a customer cancelled. Nothing about your customers or their subscriptions is writable.

What happens if I revoke the key?

Detection stops immediately. Data already in ChurnNote stays until you export or delete it.

See your last 30 days of churn, free.

Connect Stripe or Lemon Squeezy and get the report before you pay for anything.

Run my free churn scan

All integrations · Security