Reference table

Evidence classTypical useEditorial treatment
Regulator/licence registerRules, scope, licensed entity, complaint pathPrimary source; link exact page and review date
Payment provider/bankProduct mechanics and trace terminologyAttribute to provider; avoid universalising
Operator terms/helpAccount-specific process examplesDate and identify as operator-specific
Search results/autocompleteDemand and intent discoveryRecord query/date/geo; not volume or truth
Google TrendsRelative interest in a comparisonPreserve comparison/time/geo; never convert to searches
CalculationRTP, payout or edge illustrationShow assumptions and arithmetic
Editorial inferenceRoute diagnosis or content decisionLabel as inference and state uncertainty

Source hierarchy

Use current legislation and regulator guidance first for regulatory claims, then official provider documentation for payment mechanics. Operator help pages can illustrate a process but cannot establish an industry-wide rule. Independent editorial pages may reveal common user questions and competing formats, but are not copied and do not override primary sources.

Search and demand evidence

Keyword wording comes from dated GB Google Autocomplete observations, manual local search samples and a Google Trends comparison where available. Autocomplete showing a phrase is a wording signal—not monthly search volume. Trends is a relative 0–100 index within a specific comparison—not absolute searches. Volume, keyword difficulty and CPC fields remain blank unless a named licensed source supplies them.

No fabricated experience

The site must not say “we tested”, “we deposited”, “we withdrew” or imply an operator account review unless the action actually occurred under a documented, lawful protocol. Screenshots must be genuine, dated and redacted. Generated illustrations are labelled as editorial artwork and must not imitate a bank, casino or regulator interface.

Updates and corrections

High-change pages—payments, rules, phone numbers and complaint procedures—need scheduled source checks. A correction should preserve the original publication/review date, state the corrected fact and cite the replacement source. Material errors affecting safety, money or legal routing should be prioritised.

Readers need a visible corrections contact before launch. The contact address is intentionally not invented in this draft.

Advertising disclosure and commercial policy

The current mode is : Payout Case receives no referral payment from the links in this preview and contains no affiliate redirects, operator CTAs, bonuses, sponsored rankings or paid placements. External links point to cited sources or public support resources and are not gambling sign-up routes.

If the model changes, historic pages require review, commercial relationships must be disclosed beside the affected content, and editorial conclusions must remain independently controlled. No such change is authorised by this brief, and no advertising slot or fallback offer is present in the GB build.

Language, safety and review

Write in en-GB for adults in England, Scotland and Wales. Avoid urgency, celebration of wins and “risk-free” language. Place responsible-gambling help near high-risk topics. Legal, privacy and medical statements should be reviewed by an appropriate professional before production publication.

Practical next steps

  1. Classify every material claim by evidence type.
  2. Link the exact source and record the review date.
  3. State geographic, account and product limitations.
  4. Run a safety and commercial-language check.
  5. Log corrections without silently rewriting the record.

Frequently asked questions

Why are search volumes blank?

No licensed keyword-volume source was available. The project does not invent volume, difficulty or CPC from autocomplete or Trends.

Can an operator help page prove an industry rule?

No. It proves only what that page stated for that operator and date unless a regulator or common standard establishes a broader rule.

How are corrections submitted?

A public corrections contact must be configured before launch. The draft does not invent an email address or organisation identity.

Research notes · Privacy notice · Responsible gambling · Complaint process

Sources

Sources reviewed 16 November 2026. Recheck time-sensitive details before publication.