Crypto casinos with tested withdrawals

Operators where PayoutDB has either run a first-party withdrawal test or attributed an on-chain payout wallet. One own-tested operator, five observed on-chain.

Direct answer. PayoutDB has completed one first-party withdrawal test: TrustDice, USDT TRC20, 12 May 2026, 8 minutes 40 seconds end-to-end. Four more operators have attributed on-chain payout wallets we observe but have not own-tested yet: Stake, Roobet, Bitcasino.io, Shuffle. This page shows what is verified for each. It is not a top-list ranking.

Evidence ladder

We split evidence into two categories. They are not interchangeable.

Own-tested. PayoutDB deposited, played, withdrew, timed each stage, and verified the settlement on-chain. We hold the receiving wallet, the operator-side approval timestamps, and the transaction hash. KYC outcome is recorded.

On-chain observed. We have attributed an operator's payout wallet via Arkham Intelligence, a reviewer human-verified the attribution, and we index settlement events from a public block explorer. We did not run the withdrawal. The operator-side approval queue is unmeasured.

Anything outside these two categories is excluded from this page. We do not score operators we have neither own-tested nor observed.

Tested withdrawals: current coverage

Tested withdrawals — current coverage
Operator	Network	Evidence	Own-test result	Observed settlements	Where to verify
TrustDice	USDT TRC20	Own-tested	8:40 e2e, KYC triggered	not yet attributed	Full test record →
Stake	USDT ERC20	On-chain observed	not own-tested	75 settlements	Observed payouts →
Roobet	USDT ERC20	On-chain observed	not own-tested	55 settlements	Observed payouts →
Bitcasino.io	USDT ERC20	On-chain observed	not own-tested	48 settlements	Observed payouts →
Shuffle	USDT ERC20	On-chain observed	not own-tested	34 settlements	Observed payouts →

Counts as of page render time. The TrustDice row lacks observed-settlements data because wallet attribution for TrustDice is in progress.

Why TrustDice is currently our only monetized tested operator

TrustDice is the only operator on this page where we hold both a first-party withdrawal test and an active affiliate program.

Test record. TEST-TRU-4f0f1d5b, 12 May 2026, USDT TRC20, 75 USDT withdrawn. Casino-side approval 5 minutes 12 seconds. On-chain settlement 3 minutes 24 seconds. End-to-end 8 minutes 40 seconds. KYC was triggered at the withdrawal step. We submitted government photo ID plus proof of address and were accepted in one review cycle.

What this measures. One withdrawal under one set of conditions on one network. We do not claim every future TrustDice payout will resolve in 8:40. We do claim the test was real and the transaction hash is on the public block explorer.

What we do not hide. We have not yet attributed a TrustDice payout wallet on-chain. The Tier-A label on /casino/trustdice/usdt-trc20/ refers to the own-test, not to settlement coverage. Wallet attribution work is ongoing. Until it lands, the TrustDice row above shows "not yet attributed" under observed settlements rather than a placeholder number.

Full test details and the verifiable transaction hash are on the TrustDice audit page: see test record and operator-side details →

What the on-chain rows mean

Stake, Roobet, Bitcasino.io, and Shuffle each have an attributed USDT ERC20 payout wallet. Counts in the table are real settlements recorded on Ethereum block explorers and verifiable per transaction on the operator's payout-history page.

These rows do not measure operator-side approval time. They do not measure KYC behaviour. They do not prove any individual withdrawal will be approved. They show that the operator's wallet is actively broadcasting USDT transactions on the network we observe.

Why we publish observed-only rows instead of waiting for own-tests: withdrawal evidence is expensive to collect (deposit, play, withdraw, KYC). Observed on-chain data is cheaper and partially answers the question users actually ask ("is this operator still paying out?") even before we run our own test.

What to do with this page

If your search was about a specific operator's withdrawal speed or trouble, the per-operator audit page has more detail than this list:

TrustDice USDT TRC20: full test record at /casino/trustdice/usdt-trc20/
Stake USDT ERC20: observed payout pattern at /casino/stake/usdt-erc20/
Roobet USDT ERC20: observed payout pattern at /casino/roobet/usdt-erc20/
Bitcasino USDT ERC20: observed payout pattern at /casino/bitcasino-io/usdt-erc20/

If you are debugging a stuck withdrawal, the troubleshooting set is more useful than this page:

Withdrawal approved but no transaction hash: /learn/casino-withdrawal-no-tx-hash/
Pending vs confirmed status: /learn/casino-withdrawal-pending-vs-confirmed/
ERC20 transaction confirmed but funds not received: /learn/erc20-withdrawal-confirmed-not-received/

Methodology

How we attribute wallets, what counts as a settlement, and how the own-test protocol works is documented at /methodology/. The split between first-party and observed evidence is covered at /learn/first-party-vs-observed-evidence/.

Frequently asked questions

Why only one own-tested operator?

Own-tests require funded accounts, KYC documents, manual play, and a real withdrawal under timed conditions. We have run one so far (TrustDice, 12 May 2026). The next own-tests are queued behind on-chain attribution work for operators we already cover at the observed level.

Should I sign up at TrustDice because of this page?

The TrustDice link on the per-operator audit page is an affiliate link and PayoutDB earns a commission on signups via it. The commission does not change the test result. For an independent next step, the test details at /casino/trustdice/usdt-trc20/ include the transaction hash and the explorer link for direct verification.

Why is Stake not labelled own-tested here when other pages discuss Stake tests?

Stake reaches Tier-B in our publication-tier system (registry-verified licence plus observed on-chain settlements). It is not own-tested end-to-end with a verified Tier-A test record on USDT ERC20. We use "own-tested" only when PayoutDB ran the deposit, play, withdrawal, and KYC ourselves on the network shown in the row.

How often is the observed-settlements count updated?

The on-chain feed updates whenever the operator's attributed wallet broadcasts a new transaction. The number on this page reflects the count as of the page render time. Per-operator pages show the most recent settlement timestamp.

Where can I see the actual transactions?

Each operator's payout-history page links every settlement to its block-explorer record. Click any "explorer" link on the per-operator page to verify the transaction yourself.

Are these the only operators PayoutDB tracks?

No. We track more operators with per-operator review pages but exclude any operator without a completed own-test or an attributed on-chain payout wallet. Inclusion on this page is evidence-gated.

Compare withdrawal speed by network at /withdrawal-times/. Browse all operator audit pages at /casino/.