Payout Testing Protocol PT-1.0

Generate payout-speed evidence under a consistent, repeatable methodology so results are comparable across operators and over time — measured, not anecdotal. This is where the moat is built: anyone can quote a payout time, but only a consistent, repeated, documented protocol turns it into evidence. Once testing begins, each completed test will become one independent Lab (P1) item in the evidence ledger, superseding the operator's own claim. The programme is launching — no tests have been run yet. Effective 2026-07-03.

0operators tested

39on the schedule

39due now

PT-1.0protocol version

What every test captures

Recorded via a validating intake tool, so no field is skipped. * = required.

FieldType

Casinooperator✔ required

Date/time of testdatetime✔ required

Country tested fromstring✔ required

Device / platformstring✔ required

Payment / withdrawal methodstring✔ required

Deposit amountmoney✔ required

Withdrawal amountmoney✔ required

KYC already completed before withdrawal?bool✔ required

Time withdrawal requesteddatetime✔ required

Time withdrawal approveddatetimeoptional

Time funds receiveddatetime✔ required

Any manual intervention (extra KYC, support contact, delay reason)stringoptional

Supporting evidence (screenshot / email / tx-hash references)refsoptional

Protocol versionversion✔ required

Derived: hoursToFunds = timeFundsReceived − timeRequested; speedBucket is derived from hoursToFunds and drives the Payout component under Trust Score methodology v1.0.

Why these fields

Same protocol version → results are directly comparable.
Real money moves through the full deposit→play→withdraw cycle; no simulated flows.
KYC state is recorded because post-win KYC is the main real-world delay.
Manual interventions are logged, not hidden — a fast median with frequent interventions is a different signal from a uniformly fast operator.

Testing schedule

Top operatorsMonthly — the highest-traffic / highest-score operators.

Broader listQuarterly — the full reviewed list.

Event-triggeredRepeat immediately after any major platform, ownership or policy change.

Current coverage

Live from the ledger. "None yet" is shown honestly — most operators are awaiting their first measured test, which is exactly the work that lifts their Evidence Score.

OperatorCadenceLast measuredStatus

all-slotsmonthly—due

aztec-winsquarterly—due

bcgamequarterly—due

betwaymonthly—due

bitcasinoquarterly—due

captain-cooksquarterly—due

casiniaquarterly—due

cloudbetquarterly—due

cryptoslotsquarterly—due

cryptowinsquarterly—due

duelbitsquarterly—due

euro-palacequarterly—due

fieryplayquarterly—due

gamdomquarterly—due

gaming-clubmonthly—due

ggbetquarterly—due

grand-mondialquarterly—due

hippodromemonthly—due

hitnspinquarterly—due

ice-casinoquarterly—due

jackpot-citymonthly—due

livecasinoquarterly—due

lucky-nuggetquarterly—due

luxury-casinoquarterly—due

onlyspinsquarterly—due

platinum-playmonthly—due

rabonaquarterly—due

river-bellequarterly—due

royal-vegasmonthly—due

ruby-fortunequarterly—due

slotoroquarterly—due

spin-casinomonthly—due

spinitquarterly—due

springbokquarterly—due

v-vegasquarterly—due

verde-casinoquarterly—due

yesplayquarterly—due

yukon-goldquarterly—due

zodiac-casinoquarterly—due

Every test is verifiable and logged with its protocol version, so results stay comparable as the protocol evolves. Payout data is never supplied or paid for by operators. Machine-readable: /data/methodology.json. 18+. Play responsibly.