What the integration does
Stripe is Vesqo's record of who pays and how much. The first sync reads every subscription there is and how each started or ended; every sync after that reads Stripe's own event log from where the last one stopped, and, connected through Stripe Connect, Stripe's webhooks bring a new subscription, a change, a cancellation or a payment in between.
Each Stripe customer becomes an account in Vesqo, keyed by its customer id and joined to the same company in Sentry, PostHog, your support inbox and your CRM by the domain of its email address. That join is what lets an error or a support thread carry a monthly amount.
What Vesqo reads from Stripe
- Customers: name and email address.
- Subscriptions: plan, amount, interval, status, and when each started, changed or ended.
- Invoices and payments: what succeeded, what failed, and for which subscription.
- Stripe's event log, for the changes between syncs; through Stripe Connect, webhooks for subscription and invoice events too, so a failed payment shows within minutes.
- Nothing else. No card numbers (Stripe keeps those), no payouts, no balance, and no writes.
How it connects
Sign in to Stripe and approve Vesqo through Stripe Connect with read-only access, or paste a restricted key with read access to Customers, Subscriptions, Invoices and Events. Vesqo checks each of those four on connect, so a key missing one permission fails there, with Stripe's own words, and not on the first sync. Disconnecting deletes the credential the same minute.
Why connect Stripe
Sentry counts errors; PostHog counts events; the inbox counts conversations. None of them knows what the people behind those numbers pay. With Stripe connected, every signal about a customer, from a regression to a quiet month, carries their MRR, so the morning brief ranks by money, not by count.
Stripe's own dashboard shows that a payment failed. Vesqo shows that it failed for Cortex, who renew in 25 days, wrote to support twice this week and are using the product 74% less than last month.
Questions Vesqo can answer with it
- Which paying customers hit the errors after v2.14.0, and what do they pay?
- How much MRR is behind the customers affected by this Sentry issue?
- Whose payments failed this month, and has any gone through since?
- What left in cancellations this week, and who was it?
- Which customers pay more than €200 a month and used the product less this month?
Signals it writes
- Payment failed: a payment failed and nothing has succeeded for that subscription since. One per customer, gone the moment a payment goes through.
- MRR down: MRR now against the week before. A tenth lost is a warning, a quarter is critical, with what left when it can say.
- Churn: what was cancelled in the last week, as one picture.
- Renewal risk: an annual subscription about to roll over while payments fail, the inbox hears from them, or they are behind. Worth what they pay a year.
- And the money on every other signal: a release that hurt names the paying customers in it and the MRR at stake; a customer using you less shows what they pay.