Stripe

Capture every Stripe payment and subscription charge from the server, resolved to a customer before it reaches the tools you spend on.

SourcePayments & subscriptions

Request a demo Start free trial

About Stripe

What Stripe is, and why identity matters to it.

Stripe processes the payment. For a lot of businesses it is also the only system that holds a complete, authoritative record of what was actually charged.

That record lives one layer below the storefront, which is why it so often disagrees with what the marketing tools believe happened.

How it works

How Stripe works.

Stripe models money as a sequence of objects — a PaymentIntent that may succeed, fail or be retried, a Charge, sometimes an Invoice and a Subscription above it. A single purchase can produce several of these, and a failed-then-retried payment produces more. Stripe also sits behind the checkout rather than inside it, so it sees the money and not the session that produced it.

With Upstack Data

Get more out of Stripe with Upstack Data.

Upstack reads the settled outcome server-side and resolves it to a person before forwarding, so a retried payment is one conversion rather than three and a refund is not left counted as revenue. Because the resolution happens against the same graph as your storefront events, a Stripe charge and the browse that preceded it belong to one customer — which is the join Stripe itself cannot make, since it never saw the session.

What you can do with it

Three jobs Stripe does once it is connected.

Capture every order server-side
Stripe events are captured from the server rather than the shopper’s browser, so ad blockers, ITP and consent banners stop deciding which of your conversions get counted. Nothing depends on a script surviving the page.
Resolve each event to a person
Every Stripe event is matched against a 750M+ device graph before it leaves, so a phone browse and a desktop checkout resolve to one customer rather than two strangers. Returning buyers are recognised as returning.
The amount that actually settled
Charges are captured after they succeed, with refunds and partial captures reflected, so downstream tools optimise against money received rather than money attempted.