Log inStart free

Payments

Know which posts bring Stripe customers

Read-only. Matches each payment to the visit that led to it.

Available to connect
Access
Read-only
Connection
Restricted API key
History
90 days, then as they happen
Connect StripeSee Home in the demo →

Which post paid for your Stripe subscriptions?

Stripe tells you who paid and how much. It does not tell you that the customer first read your launch thread, came back from a Reddit comment two days later, then subscribed. upTake puts that missing first half next to your Stripe data, for SaaS makers who sell plans or one-off purchases through Stripe Checkout or Payment Links.

For example: you post the same feature on X and on LinkedIn, each with its own tagged link. A week later, the Stripe charges of new customers sit under the post that brought them, so the next announcement goes where buyers actually came from, not where the likes were.

Passing the source to Stripe yourself, if you want to

upTake does not need any change to your checkout: it matches a Stripe payment to the visit that came shortly before it, and marks that match as estimated. If you want an exact match, Stripe lets you attach your own data to the payment, and upTake reads it first.

On a Checkout Session, Stripe accepts a client_reference_id of up to 200 characters and a metadata map; metadata on the session is not copied to the payment or the subscription unless you also set payment_intent_data.metadata or subscription_data.metadata. Stripe allows up to 50 metadata keys per object, keys of up to 40 characters and values of up to 500.

With Payment Links, you add parameters to the link itself: client_reference_id, and the five utm_ parameters (source, medium, campaign, content, term), each up to 150 characters. Stripe's documentation says UTM values are carried on the redirect after payment, which needs the confirmation behaviour set to redirect to your site.

Read on November 18, 2026: Stripe: Checkout Session parameters, Stripe: metadata, Stripe: Payment Links URL parameters.

From a post to a Stripe payment

  1. 1. The postReddit · r/SideProjectShared with indiepdf.com/?ut=reddit
  2. 2. Visits and signups1,204 visits · 88 signupsRecorded by the upTake script
  3. 3. Payments in Stripe9 customers · $431Matched to the visit before the payment
Example IndiePDF, the demo project. Invented to illustrate, not a customer's results.

What upTake reads from Stripe

upTake reads your paid orders and subscription payments from Stripe: the amount, the currency, the date, and the identifiers of the payment and of the customer. The first sync goes back 90 days; after that, only what is new is fetched, and a payment already imported is never counted twice. Each payment is then matched to the visit that led to it: exactly when your checkout passes upTake's visitor identifier, otherwise by time, and a payment matched by time is always shown as estimated.

How to connect Stripe

  1. You need an upTake project first; creating one takes 5 minutes.
  2. Click Connect on the Integrations page; a small window asks for what Stripe needs.
  3. Restricted API key: In Stripe: Developers → API keys → Create restricted key. Read access to Charges, Customers, Checkout Sessions and Subscriptions only. Never paste your secret key (sk_…).
  4. Webhook signing secret (optional): The signing secret of the endpoint you added in step 1. Without it, new payments arrive with the next automatic sync, within a few hours.
  5. upTake checks it with Stripe before saving it.
  6. To receive payments as they happen, in Stripe: Developers → Webhooks → Add endpoint. Paste this address, pick the events charge.succeeded and charge.refunded, then copy the signing secret (whsec_…).

On the Stripe side, see Stripe's documentation on API keys and restricted keys.

What you see afterwards

Your revenue appears on the overview, split by the source that brought each customer: the post, the link or the release behind it. The weekly report tells you which actions paid and which only brought attention. Revenue is always shown apart from visits, and anything upTake had to estimate is marked as estimated.

Privacy and access

  • upTake never reads or stores card numbers. It never moves money, issues a refund or changes anything in your Stripe account.
  • Your visitors' IP addresses are never stored.
  • Keys and accesses are stored encrypted and never sent back to your browser. Your data is hosted in the European Union.
  • Disconnect Stripe at any time: upTake stops at once, and what was imported stays until you delete it.

Questions about Stripe

Does upTake need write access to my Stripe account?

No. upTake only reads payments. It never moves money, issues a refund or changes anything in your Stripe account.

How far back does upTake import Stripe payments?

The first sync goes back 90 days. After that, only new payments are fetched, and a payment already imported is never counted twice.

What happens when a payment cannot be tied to a visit?

It still counts in your revenue, shown as not traced to a source. A payment matched by time instead of by identifier is always marked as estimated.

Why a restricted key instead of my secret key?

A restricted key can be limited to reading Charges, Customers, Checkout Sessions and Subscriptions, so upTake cannot create, refund or change anything even if the key leaked. upTake refuses a secret key (sk_…) when you paste one.

Do I need to add metadata to my Stripe Checkout?

No. Without it, upTake matches each payment to the visitor seen on your site in the 30 minutes before, and marks it as estimated. Metadata only makes the match exact.

Does upTake read card numbers from Stripe?

No. It reads payments, customers, Checkout Sessions and subscriptions with a restricted read-only key. Card data never reaches upTake.

Use Stripe in your own project

Free plan · No card · 5-minute setup

Connect StripeSee Home in the demo