Estimate a website's Stripe revenue from its checkout traffic
See how many visits a website sends to Stripe Checkout each month, rank sellers by checkout traffic and turn it into a revenue range with your own assumptions.
Last updated 2026-11-05
Black Friday deposit bonus
Every qualifying top-up earns free credit, on top of any other offer.
Ends November 30
"How much does this product make?" is one of the most searched questions about any online business, and the honest answer is that nobody outside the company knows. Stripe doesn't publish anyone's revenue, and neither does anyone else. What you can measure from outside is one step before the money: how many visitors a website sends to a hosted checkout page such as checkout.stripe.com. Every visit there is a person who clicked "Pay" or "Subscribe". Lovely Router's referral traffic sources tool returns, for any checkout domain, every site that sends it visitors, with estimated visits per month, in one call for $0.06. This page shows how to read those numbers, how to turn them into a revenue range with assumptions you choose, and where that range stops being trustworthy.
Hand it to your AI agent
Copy this prompt into Claude Code, Cursor, Codex or any coding agent. It tells the agent where the docs are and how to use your API key.
Find which websites send visitors to checkout.stripe.com and give me a table of the domains I name with their monthly checkout visits and change, plus a revenue range from the conversion and price assumptions I give (label it as an estimate). Use the Lovely Router data tools: each returns JSON and is billed per result.
- Docs (read first): https://lovelyrouter.com/docs/tools/find.md and https://lovelyrouter.com/docs/tools/run.md
- Plan first: POST https://lovelyrouter.com/v1/tools/suggest with `{"task": "<my task in plain words>"}` (free). It returns the tools to run in order, each with an example `input`, the `input_required` fields, an estimated cost and a ready-made `run` request. Replace the example values with my task's; if a field is unclear, read the tool with GET https://lovelyrouter.com/v1/tools/<id>. To browse instead, POST https://lovelyrouter.com/v1/tools/discover searches the catalog.
- Show me the plan and its estimated cost (`total_est_cost_usd`) before running anything large.
- Run: POST https://lovelyrouter.com/v1/tools/<id>/run with `{"input": {...}, "max_results": N}`. A 200 has the finished run with `items`; a 202 means it is still running, so poll the `poll` path until `status` is `succeeded`, `failed`, `timed_out` or `stopped`.
- Only delivered results are billed. Keep max_results small on the first run, check the output, then scale up.
- If you support MCP, connect https://lovelyrouter.com/mcp instead (Streamable HTTP, same key; https://lovelyrouter.com/docs/tools/mcp.md) and use suggest_tools, get_tool and run_tool.
- Auth: read my API key from the LOVELY_API_KEY environment variable and send it as `Authorization: Bearer $LOVELY_API_KEY`. Never print or commit the key. If it is not set, ask me to create one at https://lovelyrouter.com/app/keys.
- Billing is prepaid: every call is charged to my balance, so test with a small request before running anything large.
- Every docs page is plain Markdown; the full index is https://lovelyrouter.com/llms.txt.
My task: <the domains to compare and the conversion and price ranges to assume>What you can and can't learn
| You can measure | You can't measure |
|---|---|
| Which sites send visitors to a checkout domain, ranked | How many of those visitors paid |
| Each site's estimated visits there, month by month, for six months | What they paid, or how often they renew |
| Whether a site's checkout traffic is growing or fading | Refunds, discounts, taxes or currency |
| How a site compares with its rivals on the same checkout | Sales through checkouts on the seller's own domain or other providers |
So the result is a traffic ranking with a trend, not a revenue figure. Any revenue number you put next to it is your model, built from a conversion rate and a price you assume. Treat it as a hypothesis to compare products with, never as a fact about one company.
How it works
Look up the checkout domain
Run
site-referralswith"website": "checkout.stripe.com". One run returns every referring site in the report, largest first, each with visits for every month of the last six months.Find the sites you care about
Filter the rows by
domainfor the products you want to compare, or keep the top of the list to see who sends the most people to pay. Group bycategoryto see which kinds of products lead.Add your assumptions
Multiply each site's monthly checkout visits by a conversion rate range and a price range that you choose and can defend. Print the assumptions next to every number you share.
Pull checkout visits per referring site
curl https://lovelyrouter.com/v1/tools/site-referrals/run \
-H "Authorization: Bearer $LOVELY_API_KEY" \
-H "content-type: application/json" \
-d '{"input": {"website": "checkout.stripe.com"}, "max_results": 1}'The Python below runs the lookup, reads every page of the report (reading pages is free), and prints a range for the sites you name. The conversion and price ranges are placeholders: set them from what you know about the market.
import os, requests
BASE = "https://lovelyrouter.com/v1"
H = {"Authorization": f"Bearer {os.environ['LOVELY_API_KEY']}"}
res = requests.post(f"{BASE}/tools/site-referrals/run", headers=H, timeout=90,
json={"input": {"website": "checkout.stripe.com"}, "max_results": 1})
run = res.json()
while res.status_code == 202: # a report can take a few minutes
res = requests.get(f"{BASE}/tools/runs/{run['id']}", headers=H, params={"wait": 60}, timeout=90)
run = res.json()
rows, offset = [], 0
while offset is not None:
page = requests.get(f"{BASE}/tools/runs/{run['id']}", headers=H, params={"offset": offset}, timeout=90).json()
rows += page["items"]
offset = page.get("next_offset")
by_domain = {r["domain"]: r for r in rows}
# YOUR assumptions, not data: what share of checkout visits pay, and what a payment is worth.
CONVERSION = (0.10, 0.30) # 10-30 % of checkout visits complete a payment
PRICE = (15, 40) # average amount per payment, in your currency
for site in ["example-ai-app.com", "rival-one.com", "rival-two.io"]:
r = by_domain.get(site)
if not r or not r["monthly"]:
print(f"{site:<22} not in the report")
continue
last = r["monthly"][-1]
low = last["visits"] * CONVERSION[0] * PRICE[0]
high = last["visits"] * CONVERSION[1] * PRICE[1]
print(f"{site:<22} {last['month']}: {last['visits']:>9,} checkout visits "
f"({r['change_percent']}% over the period) -> modelled {low:,.0f}-{high:,.0f} a month")The range is wide on purpose. A three-fold spread in conversion times a two-fold spread in price gives a six-fold range, which is about how much you really know.
What the report looks like
For checkout.stripe.com, the report covering April to September 2026 listed 2,402 referring sites, and the checkout received between 38 and 45 million referral visits a month. Each row looks like this:
{ "domain": "elevenlabs.io", "visits": 7261497, "share_percent": 3.7, "change_percent": -2.4, "is_new": false,
"global_rank": 1128, "category": "Programming and Developer Software", "period": "2026-04-01..2026-09-30",
"monthly": [{ "month": "2026-04", "visits": 1405290 }, { "month": "2026-05", "visits": 1160215 }, { "month": "2026-06", "visits": 1113851 },
{ "month": "2026-07", "visits": 1090064 }, { "month": "2026-08", "visits": 1261235 }, { "month": "2026-09", "visits": 1230843 }] }visits is the site's total over the period, share_percent its share of all referral visits the checkout received, and monthly the same visits month by month. The run's report adds the checkout's own monthly totals and the visits not credited to any site. The full field list is on the site referrals use case.
Read the numbers carefully
The figures are Similarweb's estimates of visits, good for ranking sites and spotting trends, not for exact counts. Small sites may not appear at all.
People open a checkout, compare plans, leave, and come back. One buyer can be several visits; many visits buy nothing.
A product that sends people to checkout from its own app or pricing page shows up under its own domain. A payment provider's page can show up too: in the report above, paypal.com was the second-largest referrer.
Sellers that use checkouts on their own domain, embedded payment forms, app stores or other providers send few or no visits there. A product missing from the list may still be selling a lot.
Stripe-hosted pages are not all on one domain, and other providers have their own. Each domain is its own report and its own $0.06 lookup.
Better questions than "how much do they make"
The same data answers questions you can actually rely on:
Compare the first and last month of each competitor's monthly visits. A product whose checkout traffic doubled in six months is growing, whatever its revenue.
Filter is_new for sites that started sending people to the checkout in this period.
Divide a site's monthly checkout visits by its total monthly visits from website traffic ($0.003 per site). A higher ratio means more of its visitors reach a payment page.
Sum visits by category to see which kinds of products send the most people to pay.
To let an agent do it, connect the MCP server and ask: "Run site-referrals for checkout.stripe.com, find these five domains in the rows, and give me a table of their monthly checkout visits and change. Don't estimate revenue; just rank them."
What you pay
Which sites send traffic to any website or checkout page: every referrer over the last six months, ranked by visits, with each one's visits per month, share, change, new senders, rank and category. The run's report adds the site's total referral visits per month.
Estimated traffic for websites from Similarweb: monthly visits, ranks, traffic sources, top countries, engagement.
$0.06 per checkout domain you look up, however many referring sites its report holds; reading the pages again is free. A run that fails costs nothing. Website traffic adds $0.003 per site. There is no subscription: top up from $5 and one balance pays for data tools, models and the browser agent. See pricing.
Frequently asked questions
Can I see a company's Stripe revenue?+
No. Neither Stripe nor anyone else publishes it. What this tool measures is the estimated number of visits a site sends to a checkout page, which you can turn into a revenue range only with assumptions of your own.
How accurate is a revenue estimate built this way?+
Not very, for any single company: conversion rates and prices vary a lot, and the visits are modelled. It is more useful for ranking competitors against each other and seeing who is growing, where the same errors apply to everyone.
Why isn't a product I know in the list?+
It may sell through a checkout on its own domain, an embedded payment form, an app store or another provider, or it may be too small to measure. Try the other checkout domains it might use.
How far back does the data go?+
Six months, with visits for each month. Run the lookup again each month and keep the results to build a longer history.
Do I need a Similarweb or Stripe account?+
No. You send a domain with your Lovely Router API key and get JSON back.
For partner and affiliate research on the same report, see who sends traffic to any website; for total visits across a list of rivals, competitor website traffic benchmarking. Ready to look one up? Open the tool page and type a checkout domain.