How we verify payment claims
W3Gamble publishes fees, KYC, and payout speed as two columns: declared (the public claim) and checked (our confirmation). If we have not checked a value, the page says "not verified". Numbers come from data files, not from hand-edited HTML.
Why we focus on crypto rails
Crypto deposits remove banks and card processors from the session. What remains is the network (fees, confirmations) and the operator (queue, KYC, cashout rules). Our job is to make those remaining risks readable before you send funds.
Where the data lives
Operators, networks, coins, bonuses, and KYC rules are JSON files validated with Zod at build time. Broken dates, missing sources, or dangling references fail the production build. Templates cannot invent a fee.
Declared vs checked
Declared is what the operator or a public
source states. Checked is what we
measured or confirmed. When checked is empty
(null), the UI shows "not verified". We do not copy the
declared value into checked to look complete.
License and some limit fields follow the same pattern. Until we have a checked value, the Checked column stays "not verified".
Freshness
Every numeric fact needs a checked_at date (YYYY-MM-DD)
and a source URL. Check dates appear next to tables only
when the checked value is present. Unverified rows show as
Declared only.
Listing badges use the listing check date when at least one payment fact is checked: Fresh ≤ 14 days, Aging 15-45 days, Stale after 45 days. Stale does not hide a listing - it means treat claims carefully until we re-check.
Cards may also show a Catalog refreshed stamp. That is
an editorial rebuild cadence (about every three days). It is not a substitute for a cashier
verification and does not rewrite checked_at in the data.
KYC labels
Operator KYC policy is one of: none,
optional, required,
threshold. Each maps to a short rule card (summary +
triggers). A "no KYC" badge only appears when policy is
none or the matching feature flag is set. A fast payout
sample alone does not earn a Fast payout badge.
Compare pages
/compare/ only pairs operators of
the same type. URLs are alphabetical (a-vs-b) so each
matchup has one canonical page. Tables use the same declared/checked rules as listing cards.
Operator slugs cannot contain -vs- (reserved).
Outbound Visit buttons
Visit buttons open the operator site in a new tab with
noopener,noreferrer. Destination URLs are not shown in the
page status bar.
When catalog slices exist
A network or coin catalog page is published only when that rail is verified (or stale but still published) and at least one active operator of that type uses it. Empty slices are not built and do not appear in the sitemap.
Coin pages under /no-kyc/ and
/fast-withdrawal/ generate only when an active listing uses
that coin on a publishable network - so we do not create thin URLs for unused assets.
Bonuses
Promo offers live under /bonuses/. Bonus figures never mix into network fee pages. Bonus links only resolve for active operators.
Review cycle
- Capture a public source (cashier, help page, license registry, or similar).
- Enter the declared claim so it can be audited.
- Add a checked value only after confirmation; otherwise leave null.
- Publish: build validates schema, then static pages regenerate.
- Re-check over time; Aging/Stale badges flag stale high-traffic cards first.
What we do not publish
No APKs, predictors, signal bots, "guaranteed" systems, or invented fee tables. If a number is not in sourced data, it is not shown as verified.
Corrections
Send the page URL and a better source via Contact. We update the data file, not a one-off HTML patch.
