Affiliate tracking with no site at all. Just a Payment Link.
No page builder, no app — just a shareable Stripe Payment Link. Paste one script tag anywhere the link is shared from, append the stamp at click time, and Qanary tracks every conversion.
one script tag, one click-time param. that's the whole integration.
- ~10 minutes, no developer required
- Works with nothing but a shareable link
- Free plan, no card required
There's no site to instrument. The link still needs to attribute.
However you're tracking referrals on Stripe Payment Links today — a spreadsheet, a generic pixel, or nothing yet — attribution needs to survive ad blockers, the commission math needs to survive an audit, and the payout needs to go out on a rail you already use. Here's what one script tag adds:
Tracking it yourself
Basic click tracking at best — no coupon-code fallback for ad blockers or podcasts, no fraud check before a commission is owed, and payouts mean a manual spreadsheet.
Qanary
One script tag in your site's <head>. Coupon-code fallback, fraud checks before
commission, and payouts through Wise or PayPal — the same system whether
you're on Stripe Payment Links or anywhere else.
Paste, stamp, verify. Three steps.
1. Paste the tracking snippet — your site's <head>. It sets the
first-party attribution cookie when a visitor lands with
?via=AFFILIATE_CODE and records the touchpoint.
2. Carry the referral into checkout — Payment Links accept ?client_reference_id=... — append the stamp at click time with a small script that finds your buy.stripe.com links and appends client_reference_id from Qanary.checkoutStamp().
3. Verify — open your site with a test ?via=,
run a test-mode checkout, and confirm the conversion lands attributed — or ask
your coding agent to run the MCP diagnose_attribution tool.
<script src="https://app.qanary.cloud/qanary.js" data-qanary="YOUR_PROGRAM_SLUG" async></script>
Paste this exact tag into your site's <head>, publish, and it's
live. Swap YOUR_PROGRAM_SLUG for the program slug from your
Qanary dashboard.
One tag. Three jobs.
Sets the attribution cookie
Reads ?via=AFFILIATE_CODE off the URL the moment a visitor lands
and records the touchpoint — no configuration beyond the program slug.
Stamps the Payment Link itself
Appends client_reference_id to any buy.stripe.com link at click time — no backend, no Checkout Session code required.
Verifiable end to end
Ask your coding agent to run diagnose_attribution and it walks
visit → identify → webhook → attribution → ledger, so a stalled conversion is
never a mystery.
Whatever's sharing the link.
A link in bio or newsletter
No landing page at all — just a Payment Link shared directly. The click-time script appends the stamp before the visitor ever leaves for Stripe.
A single product, no storefront
Selling one thing with no need for a full site? A Payment Link plus this snippet is the entire commerce and attribution stack.
Coupon codes for offline shares
For a podcast mention or a printed flyer with no clickable link at all, a personal coupon code attributes the sale instead.
Migrating from another tool
Swap the old tracking snippet for Qanary's wherever the link currently lives — existing ?via= links your affiliates already shared keep working.
See it side by side.
| Capability | Tracking it yourself | Qanary |
|---|---|---|
| Setup time on Stripe Payment Links | Custom dev project | ~10 minutes |
| Works with nothing but a shareable link | No | Yes |
| Fraud checked before commission is owed | No | Yes |
| Falls back with no page to instrument | No | Yes, via coupon codes |
It works the day you publish.
- Live the moment you publish. The snippet is a plain script tag pasted into a field Stripe Payment Links already gives you — nothing to submit for review, nothing to wait on.
- Doesn't slow down your site. Loads with
async, so it never blocks page rendering while it sets the attribution cookie. - Coupon codes cover the rest. A podcast mention or a DM with no link at all still attributes through a coupon code — see links & coupon codes.
- An agent can paste it for you. Point Claude Code, Cursor, or Codex at Qanary's llms.txt and it can install the snippet and verify it in one prompt.
Fair questions.
Where exactly does the snippet go if I don't have a full site?
Anywhere the Payment Link is shared from — a simple landing page, a link-in-bio tool, or any page with a <head> you control. The snippet and the click-time script both need to load there.
Does the snippet slow down my site?
No — it loads with the async attribute, so it fetches in the
background and never blocks page rendering.
What does the click-time script actually do?
It finds links pointing at buy.stripe.com on the page and appends ?client_reference_id=... from Qanary.checkoutStamp() the moment before the visitor clicks through.
What if there's truly no page at all — just a shared link?
Use a coupon code instead. Give each affiliate a personal code baked into their own Payment Link, or applied at checkout, and Qanary attributes the sale with zero snippet involved.
Can an AI agent install this for me?
Yes — point Claude Code, Cursor, or Codex at Qanary's llms.txt
and it can install the tracking snippet and wire a webhook from a single
prompt. See the AI agent page for the exact setup.
Everything you need to start tracking.
Paste the snippet. Start tracking tonight.
Join the waitlist now; when registration opens, wire your Payment Link in ten minutes.
Join the waitlist