Connect Stripe

Stripe is the single highest-signal source Herald can read. Connect it alone and the first briefing has a full revenue section.

Connect

1. Go to Settings → Integrations → Stripe.
2. Click Connect Stripe. You’ll be sent to Stripe’s OAuth screen.
3. Pick the account (or sandbox) you want Herald to read.
4. Approve read scopes for customers, subscriptions, invoices, charges, and disputes.

Herald never gets write access. We can’t create charges, refund anything, or change subscription prices.

What gets backfilled

On connect, Herald spawns a backfill fiber inside your Product DO and paginates Stripe’s list endpoints. The default window is 90 days — enough to compute MRR waterfalls, week-over-week churn, and expansion trends on day one. Scale tier extends this to 1 year or full account history.

Progress is live in Settings → Integrations → Stripe: “Stripe: 1,247 / 3,890 events processed.” Backfill survives hibernation and rate limits — close the tab and come back.

What arrives after

Herald subscribes to:

• invoice.paid, invoice.payment_failed
• customer.subscription.created / updated / deleted
• customer.created / updated
• charge.dispute.created

Each webhook is signature-verified, queued, and written to your Durable Object’s SQLite. The MRR rollup recomputes hourly.

Test mode vs. live mode

Herald treats test-mode data as real. If you point us at a Stripe sandbox, expect a briefing that reflects sandbox activity. Switch to a live Connect before trusting the numbers.

Exclude internal accounts

MRR distorts easily with founder and teammate accounts. Tell Herald once, in chat:

MRR excludes accounts with email addresses ending in @helpkit.com.

Herald stores that as a semantic annotation. Every MRR calculation from then on respects it.

Disconnect

Settings → Integrations → Stripe → Disconnect revokes the OAuth token and stops future ingestion. Past Stripe data stays in your tenant until you delete the Product or purge manually under Settings → Data.