The Stripe integration puts billing context where support happens: an agent opening a ticket can see what the customer pays for and what they were last charged, without switching to Stripe.
Add Stripe from Integrations and paste a Stripe API key. Nothing else to configure — there's no destination to pick, because nothing is sent to Stripe.
Three steps, in order:
If the contact carries stripeCustomerId as custom data, that customer is used.
Otherwise Gleap searches Stripe for a customer with the same email address.
If that finds nothing and the email is on a company domain — not a free provider like gmail.com — it searches for customers at that domain.
The domain step is what makes the integration useful in B2B, where the person writing in is rarely the one who pays. Where several customers match, the one with an active subscription wins.
Sending the customer id is still the reliable route:
Gleap.identify("user-123", {
email: "[email protected]",
customData: { stripeCustomerId: "cus_ABC123" },
});The customer, their subscriptions, and their most recent charges. Enough to tell whether someone is a paying customer, on which plan, and whether their last payment went through — which is often the actual answer to the question they're asking.
Usually the contact has no email address, or their email in Gleap isn't the one on the Stripe account — a work address in your product and a personal one in billing is enough to break the match. Sending stripeCustomerId removes the guesswork for good.
Also check the key: one restricted so far that it can't read customers fails silently, and the panel simply stays empty.
