Connect Stripe customer context
Show Stripe customer information to your agents without building a custom synchronization service.
What this connection does
The lookup shows matching customers and up to the latest 20 payments and invoices per match, including disputed payments. It does not calculate a complete lifetime revenue or MRR report.
This is an agent-only, read-only lookup. It does not continuously copy your entire database, synchronize edits in both directions, or grant the AI permission to change customer records.
Connect your account
An administrator opens Settings → Integrations → Stripe and selects the relevant site. Use a restricted Stripe key with Customers, Charges and Invoices read access. Keep test and live accounts separate.
Enter credentials only in the authenticated connection form. Do not paste them into widget code, a public repository or a browser-side script. Review and approve the agent-lookup permission, then save.
Look up a customer
Open a conversation with the customer’s email address, then load connected customer details in the Inbox. The connector searches for matching email records. A match supplies context for your team; it does not verify the caller or visitor owns that identity.
An empty result can mean no exact match, insufficient provider permissions, expired credentials or a limited search. Review the reported connection status before concluding the customer does not exist.
Test before relying on it
Use a test customer whose details you know. Confirm the same customer and expected records appear in the Inbox. Try an unmatched email and confirm no unrelated customer is shown. Check that only authorized agents can load the connected details.
Disconnect or replace credentials in settings if access should end. Existing information already saved in a conversation or contact is not automatically erased by disconnecting the provider.
If you need a custom synchronization
A separate server-side integration can use the Contacts API with the authentication described in its reference. Design explicit field mapping, exact identity matching, idempotency, retries and deletion handling. These are responsibilities of that custom integration; the built-in lookup does not implement them for you.
Never put an agent-session token in public client code. Do not assume a search’s first result is the intended contact. Do not interpret a matching email as permission to reveal billing details to a visitor.