Skip to main content
Connecting Stripe is how you bring verified revenue into Clickbase — real money confirmed by your payment provider. Once connected, Clickbase imports your billing history and keeps it live, then attributes each payment back to the visit that earned it. No tracking code is required for any of this.

​
What you’ll need

A Stripe restricted secret key, not your full secret key. A restricted key (starting rk_live_… or rk_test_…) grants only the read access Clickbase needs. It’s stored encrypted and is never shown again once saved. A key with the wrong prefix, a test key used in production, or a key Stripe rejects will be refused.

​
Connect

Connecting runs as a short, guided flow on the site’s Revenue settings:
  1. Connect — paste your Stripe restricted key.
  2. Align currency — set the site’s reporting currency to your Stripe account’s settlement currency, so all the imported amounts line up.
  3. Select products — choose which Stripe products to import. This allowlist filters what gets ingested.
  4. Import — Clickbase starts the backfill.
Selecting products happens before the import starts, on purpose: the allowlist filters ingestion but doesn’t remove history that’s already been imported, so choosing first keeps your data cleanly filterable.

​
What gets imported

Clickbase pulls your full payment history — charges, refunds, disputes, invoices, subscriptions, and customers — and then keeps it live going forward. The import runs in the background across those resources; if any one resource stalls, you can retry just that resource, and it resumes from where it left off rather than restarting from scratch.

​
Verified vs reported revenue

This is the key distinction to keep straight: Verified revenue is confirmed by your payment provider and drives the numbers you bill and forecast on. Reported revenue is a browser signal — useful for attribution, but anyone can fire it from their console, so it never counts as real money and never reaches your Revenue page. Only Stripe and the Payments API can produce verified revenue. See Track revenue for the full picture.

​
Attribution

Once Stripe is connected, payments are matched back to the visitor, campaign, and source that produced them. Payments that can’t be matched land under Unattributed. See Revenue attribution for how the matching works and how to improve it.

​
Security notes

Clickbase never exposes your Stripe key or webhook secret through any surface — both are stored encrypted. The full API for the connect flow is documented under Stripe integration.