v1.2.0 · published 20/07/2026
What "verified" means
Verified figures come from read-only connections to a business's payment provider (Stripe in V1). We never handle the money and cannot move it; the access is read-only by scope, and members can revoke it in one click — tokens are deleted immediately and syncing stops.
To be precise about the claim: this confirms money moved through the connected rails, refund-adjusted. It is not an audit of the business's total revenue or profit — deeper checks arrive with the Fully Verified (bank cross-check) tier.
The maths
Net revenue for a day = succeeded charges − refunds − disputes, with chargeback reversals added back. All figures are computed in whole cents. V1 verifies AUD accounts only: if non-AUD activity appears, verification pauses and the account is flagged for review rather than mixing currencies into one number — multi-currency conversion (at month-end RBA rates, with the rate stored) arrives in a later version. Days bucket on UTC calendar dates.
Monthly milestones ($1k, $10k, $50k months) are calendar months where net revenue meets the threshold — net, not gross: a month that only crosses the line before refunds does not count.
The 14-day settling window
Badges are not issued the moment a threshold is crossed. We wait 14 days after the month ends so refunds and disputes have time to land. What survives the window is what gets certified. And certification is not forever-immune to facts: if a later refund or chargeback drops a certified month below its threshold, the badge comes off public display while a human reviews it — restored if the dispute resolves in the business's favour, withdrawn with a dated correction if it doesn't.
Anomaly review
Automated checks flag patterns associated with manufactured revenue: refund ratios above 15% of gross, disputes above 2%, one customer providing more than 60% of a milestone month, the same card funding repeated charges, and end-of-month volume spikes beyond 8× the trailing median. A flag pauses the milestone — it is not shown publicly while under review. A human reviews every flag: cleared milestones proceed to certification; upheld flags revoke the milestone, and revocations are published, not deleted.
Tiers
Listed — on the registry, no active verification. Verified — active read-only connection, at least 14 days of history, no upheld integrity flags. If a connection breaks and stays broken, the badge does not silently persist: the business returns to Listed and its public page says so.
How the AI Visibility Score is sampled
We ask AI models the questions real customers ask ("best electrician in Brisbane") and measure whether a business appears, where it ranks, and in what light. Honesty about the method: we sample provider APIs (OpenAI, Google, Anthropic models) as proxies for consumer AI surfaces — close relatives of what ChatGPT, Gemini and Claude users see, not the consumer products themselves. Model answers vary between runs, so scores are smoothed across two runs and carry a confidence label; a single-run score is marked "insufficient data" rather than presented as settled. Mentions and rankings are detected by deterministic code; a model grades sentiment only, and every grade stores a reference to the exact response it judged. Prompt sets are versioned — when the questions change, the version shown with your score changes with them.
Corrections
Mistakes are corrected in public. Methodology changes bump the version number you see on this page; corrections to published figures appear as dated entries on the corrections page. Nothing is silently edited.
What we don't do
No exact revenue figures are shown publicly in V1 — badges and bands only, and bands only where the member opts in. Customer emails from payment data are stored hashed. Financial access tokens are sealed (public-key encryption) at rest. Payment data is never used to train shared models.