How BetJudge verifies every figure it publishes

The four provenance labels

Nothing is published on this site without saying where it came from. A wrong licence, RTP, KYC or bonus figure in this vertical is not a content error — it is false regulatory or financial information, so the labels are enforced by the data schema itself rather than by editorial habit.

• Verified by us — checked directly on the live platform with a real account, at the date shown.
• Our own testing data — derived from BetJudge testing we have already carried out and published, such as our timed withdrawal test.
• Our estimate — an informed approximation. Always rendered as an approximation, never as a measurement.
• Not verified yet — we have not established it. The field is left blank and the page states that no claim is being made. It is never filled with a plausible-looking figure.

How bonus codes are verified

A code entry records four things: the code itself, exactly what it unlocks, the condition attached to it, and the date it was last confirmed. All four have to be present before the offer is stated as fact anywhere on the site.

Bonus terms in this vertical change without notice and without any announcement. That makes the verification date part of the answer rather than metadata: an offer confirmed months ago is an offer that may no longer exist. Our build fails if a review displays a bonus benefit without both a confidence label and a verification date.

How withdrawals are timed

Withdrawal speed is measured, not reported. Each platform is tested with a minimum of three real cryptocurrency withdrawals, timed from the moment the request is submitted to the moment the transaction appears on-chain.

Block confirmation time is excluded, because that is network latency and identical across every platform — including it would flatter slow operators and penalise fast ones. Where a platform imposes a pending window before processing, that window is included, because it is time the user actually waits.

How often each figure is re-checked

Different classes of data go stale at different rates, so each has its own review window. A figure past its window is treated as unverified until re-checked, regardless of how confident we were when we first published it.

• Bonus terms and code benefits: every 30 days. The fastest-moving data on the site.
• Average slot RTP: every 90 days, against provider documentation.
• KYC behaviour: every 90 days, or immediately if a reader reports a threshold change.
• Licensing and withdrawal timings: every 180 days, or immediately on any credible report of a change.

What licensing does and does not prove

A casino’s legitimacy rests on a real, verifiable licence — not on how many years it has been operating or how much traffic it attracts. Longevity and popularity are reputation signals; they are not regulatory ones, and we do not treat them as interchangeable.

Where we publish a licensing jurisdiction, it carries its own provenance label independent of the rest of the review. A jurisdiction we have not re-checked against the issuing registry is labelled as our own prior data, not as a confirmed licence.

Where the commercial relationship sits

BetJudge earns a commission when a reader signs up at a reviewed casino through our links. That relationship affects which platforms we can link to; it does not affect any measurement on this site, because the measurements are applied identically to every platform and published with their method attached.

Editorial ranking and measured data are kept visibly separate. Where a listing is ordered by our judgement, the page says so. Where it is ordered by a measured figure — payout speed, RTP — the data decides the order and our opinion does not enter into it.

Frequently asked questions