Learn
How we test crypto casino payouts
Our payout testing protocol in plain terms: how a test is set up, what we record, how the redacted transaction proof works, and what “evidence level” means.
One test, one wallet, one moment
Every published test is a real withdrawal from a funded account to a wallet we control. We log timestamps at four points: request submitted, request approved, transaction broadcast, wallet received. From those, we derive approval time, settlement time, and total payout time.
The five things we capture
Conditions — network, deposit amount, withdrawal amount, whether KYC triggered. A test only describes the operator's behaviour under these conditions.
Timings — the three durations described above.
KYC outcome — not triggered, partial, or triggered, with any supporting detail.
Network fee — the on-chain fee actually paid, in native units and USD at the time of broadcast.
Redacted transaction proof — first 4 and last 4 characters of the transaction hash, plus a server-side /verify/ redirect to the block explorer. The full hash is never published.
Evidence grades A through E
Every test carries an evidence grade. Level A is our own measured test with full timestamps and an explorer-verifiable transaction. Levels B and C are partial or third-party-corroborated data. Levels D and E are operator claims or unverified reports, included only as context. Rankings are weighted: an operator with one Level A test outranks an operator with five Level D claims, even at identical times.
What a single test does not prove
One test reflects one wallet, one amount, one moment in time. Payout speed varies with network congestion, account history, withdrawal amount, and operator review queues. We re-test on a rolling schedule and publish the changelog on each entity page. We avoid absolute language and report what we measured under stated conditions.