Stripe

Connect Stripe to bring in payments, subscriptions, and invoices — read-only.

Stripe brings your payments, subscriptions, and invoices into Kula Intelligence, so the AI can answer money questions from your real revenue.

What we read — and what we don't

• We read: customers, charges, subscriptions, invoices, and payment intents — read-only.
• We don't: create charges, issue refunds, change subscriptions, or move money. Ever. Full card numbers are never stored; only the last four digits are visible, and only at the Full permission level.

What you'll need

• A Stripe restricted API key with read access (created in your Stripe dashboard — you control exactly what it can see).
• A few minutes in your Stripe dashboard to add a webhook (so new payments arrive promptly).

How to connect

1. In Stripe → Developers → API keys, create a restricted key with read permission for customers, charges, subscriptions, invoices, and payment intents.
2. In Kula, open Connectors → Stripe, paste the key, and click Test. A green result means the key works.
3. Click Connect, then register the webhook URL Kula shows you in your Stripe dashboard and run the quick test. This is what lets new payments flow in near-real-time.
4. Start the import to pull your payment history (12 months is a good start).

Good to know

• If you skip the webhook, Stripe still works — Kula just checks for new payments on a schedule instead of instantly.
• Your Stripe key is stored encrypted and only ever used to read. Rotating the key in Stripe? Just paste the new one and re-test.

If it stops working

A Stripe error almost always means the key was rotated or revoked. Create a fresh restricted key and re-enter it. Full recovery steps are in Keeping your connectors healthy.