Connect Stripe to Customer Spine
Payments, subscriptions and invoices, attached to the customer who paid. Revenue on a profile comes from here.
Where the data goes
Every teamspace gets one endpoint for all sources — the signature header each vendor sends tells us which integration delivered the event. You are given the real one when you sign in — the last segment is your teamspace id.
https://ingest.customerspine.com/ingest/<your-teamspace-id>Method POST · Header Stripe-Signature
How it authenticates
Stripe signs every request and gives you the signing secret when you create the endpoint. You paste that secret into Customer Spine — we cannot generate it, because Stripe signs with its own value.
Steps
- 1Create the endpoint in StripeIn the Stripe Dashboard, open Developers → Webhooks and add an endpoint. Paste the URL above as the endpoint URL.
- 2Choose which events to sendSelect the customer, payment_intent, invoice and checkout.session events you care about. customer.created, customer.updated and payment_intent.succeeded are the ones that build the most useful profile. Sending everything also works — anything we do not recognise is stored raw and ignored.
- 3Copy the signing secretAfter the endpoint is created Stripe shows a signing secret beginning with whsec_. Reveal it, copy it, and paste it into Customer Spine on the Sources screen.
- 4Send a test eventUse Stripe's “Send test webhook” button. A 200 back means it is wired; the profile appears once a real customer event arrives.
Worth knowing
Stripe signatures expire after five minutes, so a replayed old request is rejected. That is deliberate and needs no configuration.