Stripe context on every conversation

When a customer writes in, the first question your team usually asks is "do they pay us, and how much?" Ochre's Stripe integration answers that before you read the message.

What you get

After connecting Stripe, every end user with a matching email gets a Stripe block on their Customer 360 panel. The block shows:

• MRR. The current monthly recurring revenue from this customer's active subscriptions.
• Plan. The product or price nickname they're subscribed to.
• Lifetime value. Sum of all paid invoices since they became a customer.
• Payment status. Active, past due, canceled, or trialing, with a colored badge.

Each row links out to the corresponding object in Stripe so you can dig deeper without leaving Ochre and then jumping to the right account.

Read-only by design

The Stripe integration is read-only via Stripe Connect. Ochre never charges, refunds, or modifies subscriptions. That's deliberate: billing is high-stakes, and we'd rather your team click through to Stripe for any change than risk an accidental edit. If you need to issue a refund, the link in the Stripe block opens the right invoice and you finish the action there.

For the broader integration setup, see stripe-integration.

Backfill on connect

Connecting Stripe kicks off a backfill. Ochre walks your customer list and matches each Stripe customer to an existing Ochre end user by email. Where there's a match, the context block is attached. Where there isn't, the Stripe customer is held in a lookup table; the next time someone with that email writes in, their record is created and the Stripe block is attached at the same time. We call this lazy matching: we don't create empty end-user records for everyone in your Stripe account, only for people who actually contact you.

Backfill usually finishes within minutes. Larger accounts (50k+ Stripe customers) can take longer; you'll see a progress indicator on the integrations page.

Lazy matching for new conversations

When a brand-new email writes in, Ochre creates the end user, then checks the Stripe lookup table for that address. If there's a hit, the Stripe block appears on the first message. No webhook setup, no manual link.

If the customer's Stripe email doesn't match the email they're writing from (common: company billing email vs. user's personal email), you can manually link them by editing the email on the customer panel, or merging two records. See customer-merge.

How the AI uses it

The AI agent sees the same Stripe context the human does. That means a customer asking "when does my plan renew?" will get an answer based on their actual subscription period, not a generic doc snippet. You can also write routing rules that depend on plan tier or MRR; see routing-rules.

If you'd rather the AI not have access to billing fields, you can revoke its read scope under integration-permissions.

Triage and filtering

Stripe context unlocks a few common workflows.

• Filter the inbox by MRR. Sort high-value accounts to the top.
• Auto-tag past-due customers. Combine a Stripe condition with a routing rule to flag billing-blocked conversations.
• Custom-field segments. Pair MRR with custom fields like region or account manager to slice the inbox.

Troubleshooting

If a customer's Stripe block isn't showing, the most common cause is an email mismatch. Check the email on the Ochre end-user record against the email on the Stripe customer. Aliases on the Ochre side will be matched too, so you can add their billing email as an alias instead of merging.

For a fuller checklist, see stripe-not-showing.

Disconnecting

Disconnecting Stripe removes all blocks from customer panels and stops the AI from referencing billing data in replies. Cached context is purged within minutes. See disconnecting-integrations.

Stripe context is one of the highest-leverage integrations in Ochre. If you're paid by your customers, connect it on day one and let the rest of the product get smarter.