Connect Stripe | Docs | Fivo University

Stripe knows whether a customer is actually paying. Connecting it lets the Brain enrich the people it already knows with their plan, revenue and payment state, so you can ask who is at risk, not just who is unhappy.

What it adds to your Brain

Fivo reads your Stripe customers and their subscriptions, and keeps the ones that matter now:

Customers with an active or past due subscription.
Customers whose subscription was canceled in the last 90 days, so recent churn stays visible.

For each of them the graph gets a customer with its plan, status, start date, monthly recurring revenue and the date the subscription ended or is scheduled to end. Plan names come from your Stripe product names when the key can read products; otherwise from the price's nickname or what it bills.

Stripe never creates a person in your graph: a customer is linked to a person only when the graph already knows that email from another source. Customers without a subscription, on trial, unpaid or canceled long ago are left out.

Example question: "Which companies we met last month are past due in Stripe, and what plan are they on?"

Before you start

You need a Stripe Dashboard role that can create API keys.
Fivo takes a restricted key that you create in Stripe, not your secret key. Give it read permission on customers and subscriptions, and optionally on products so plans carry their product name. Fivo never needs write access.
Have your Stripe account ID at hand (it starts with "acct_"). A restricted key cannot tell Fivo which account it belongs to, so Fivo asks you.

Step by step

In the Stripe Dashboard, create a restricted API key with read access to customers and subscriptions (and products if you want product names). Copy it; Stripe shows it only once.
Open Integrations in the app and choose Stripe.
Click Connect. Fivo asks you to paste an API key created in your Stripe account and checks it with Stripe before saving it.
Enter your Stripe account ID (acct_...). This field is required.
Optionally paste a Webhook signing secret (whsec_...). If you do, Fivo shows you a Webhook URL: paste it as the webhook destination in your Stripe dashboard so Fivo receives updates as they happen.
Continue. Fivo confirms the connection and starts reading.

What happens next

Fivo reads your whole account: every customer with its subscriptions, then recently canceled subscriptions. Stripe cannot say "what changed since", so each regular sync pass re-reads the account and the 90-day churn window is re-evaluated at least once a day. A change without a new dated event, such as a price edit, waits for the next dated event before it is applied.

If you set up the webhook, billing events (customer or subscription changes, invoices paid or failed) trigger a fresh read of the account, so changes arrive sooner.

Who can see what: a restricted key cannot list your Stripe team, so with organization scope Stripe material is readable by the organization owner, and in a personal graph by its owner. People linked to a customer keep the visibility they had from their own sources. See Permissions: what your Brain can see.

Disconnect

Open Integrations, select Stripe and click Disconnect. Fivo stops reading and deletes the stored key. What the Brain already learned stays in the graph; connecting the same account again resumes reading. To take Stripe material out of the graph, use Remove from graph on the Stripe source in the AI Brain view. You can also revoke the restricted key in Stripe at any time.

Troubleshooting

"Stripe rejected this key." The key is wrong, revoked, or lacks read access to customers. Create a new restricted key and try again.
The account ID does not have the expected format. It must start with "acct_" followed by letters and digits. Copy it from your Stripe account settings.
Nothing appears yet. Only customers with an active, past due or recently canceled subscription enter the graph, and a customer is linked to a person only if the graph already knows that email. Connect your CRM, calendar or email first so there is someone to link to.
Webhook events do not arrive. Check that the Webhook URL from Fivo is the destination in Stripe and that the signing secret you pasted belongs to that endpoint. Even without the webhook, the regular pass keeps the account up to date.

integration
billing