How we verify a betting site
Real-world testing is what TopBetting actually does. We open accounts, move real money, and record what happens — then keep the proof. This page shows the process and the standard of evidence behind every finding.
The testing process, end to end
Every operator goes through the same sequence, performed by a real person on Nigerian networks with real money.
- Register — create a genuine account and document onboarding.
- Deposit — fund the account across common Nigerian payment methods.
- KYC — complete identity verification as a real user would.
- Withdraw — request and track a real payout (the decisive test).
- Support — contact customer support and record responsiveness.
- App & platform — use the app/site on local networks.
- Capture — every step is captured as dated, hashed evidence.
Evidence: Each step produces captured evidence stored under chain-of-custody. See where →
The six things we test
Findings are organised into six areas. Withdrawals matter most because being paid is the point.
- Withdrawal & Payments — whether you actually get paid, and how reliably.
- Licensing & Legitimacy — real, verifiable licensing and corporate identity.
- KYC & Account Integrity — fair, lawful checks; no arbitrary lockouts.
- Deposits & Funding — funding that works across Nigerian methods.
- Customer Support — reachable, competent help.
- App & Platform — a usable, stable app/site locally.
Evidence: How each area converts to a score is documented in the methodology. See where →
Where the evidence comes from
Evidence is a first-class part of the platform, not a screenshot dump. For every verified claim we hold a provable chain:
- Capture — the original (receipt, screenshot, support log, licence record) is recorded with who/when/where.
- Hash — a SHA-256 fingerprint is taken at capture, so any later alteration is detectable.
- Chain of custody — an append-only log records capture → redaction → publication.
- Redaction — personal data is removed in a separate, separately-hashed copy; originals are never published.
Evidence: On a verified operator, redacted proof appears in its Evidence panel, each tied to a dated test. No operator is verified yet, so none is published. See where →
How often we re-test
Operators change, so verified areas expire and are re-tested on a schedule. Withdrawals/deposits are re-checked most often; licensing least often.
| Area | Counts fully until | Expires after |
|---|---|---|
| Withdrawal · Deposit | 60 days | 90 days |
| Support · App | 120 days | 180 days |
| KYC | 150 days | 240 days |
| Licensing | 270 days | 365 days |
Evidence: Freshness is enforced by the Trust Engine; see the methodology for how decay affects coverage. See where →
What we're verifying now
Our verification pipeline is shown honestly — what's being tested, what's queued, and what was recently verified. As real runs happen, this fills from the verification record.
Evidence: Every entry here links to the operator and the dated tests behind it. See where →
Our standard
How verified findings become a score: Methodology. Why our findings are independent: How we stay independent.