Stake vs TrustDice: the documented differences
Every difference below traces to a dated source: welcome-offer terms, payment coverage, licence and platform facts. Unknown stays unknown, and nothing is aggregated into a safety score. The full 20-area research record for both casinos follows the comparison.
Welcome offer, documented
Mechanism on record: rakeback. The checked source did not establish full offer terms; see the source check
500% Welcome Bonus + 100 Free Spins package (1st deposit: 200% match + 20 Free Spins; 2nd: 100% + 30 FS; 3rd: 200% + 50 FS)
Operator source · checked 2026-08-19 · full terms
Decision areas, side by side
The seven areas a depositor checks first, each with its research status and latest dated check. Statuses measure research coverage, never quality, and never combine into a rating.
| Area | Stake | TrustDice |
|---|---|---|
| Licence | Documented · 2026-09-13 | Documented · 2026-09-13 |
| Payment routes | Documented · 2026-08-02 | Documented · 2026-09-12 |
| Deposit terms | Partial · 2026-08-02 | Partial |
| Withdrawal terms | Partial · 2026-08-01 | Partial · 2026-09-12 |
| Bonus terms | Partial · 2026-08-02 | Partial · 2026-09-12 |
| KYC / verification | Partial · 2026-08-02 | Partial · 2026-09-12 |
| Cashout observation | Partial | Partial |
What the documented record separates
- Bonus mechanism: Stake's recorded mechanism is rakeback; the checked source did not establish full terms. TrustDice's documented offer is a deposit match with published limits. A player comparing headline bonuses can verify TrustDice today.
- Research depth on RTP Ledger: Stake's record has source-backed claims in 16 of 20 areas. TrustDice's record has source-backed claims in 9 of 20 areas. Where a record is thin, verify directly with the operator before depositing.
Stake
- Research tier
- Source-reviewed record
- Areas with source support
- 16/20
- Source-linked statements
- 46
- First-party test areas
- 0
- Unique sources
- 17
- Latest dated evidence
- 2026-09-13
TrustDice
- Research tier
- Source-reviewed record
- Areas with source support
- 9/20
- Source-linked statements
- 19
- First-party test areas
- 0
- Unique sources
- 10
- Latest dated evidence
- 2026-09-13
Every decision area, including the gaps
A source link supports only the scope stated in its cell. Published rules are not treated as an RTP Ledger account test, and no dated source means the area remains explicitly unresearched.
| Evidence area | Stake | TrustDice |
|---|---|---|
| 01Legal operator identity | Documented· 1 supported statement The operator and regulator records bind Medium Rare N.V. to stake.com. Checked 2026-08-02 | Documented· 2 supported statements The terms name Satoshi Gaming Group N.V. as the owner of trustdice.win. The terms give Chamber of Commerce number 151832. The regulator certificate binds the same company and number to the domain. The terms footer names Tahiti Technology Limited as the payment processor for Satoshi Gaming Group N.V. The processor address is in Limassol, Cyprus. Checked 2026-09-12 |
| 02Licence and domain coverage | Documented· 1 supported statement The regulator certificate listed the covered domain, licensee, number and active status. The Curaçao Gaming Control Board's bulk licence registry PDF is dated 2026-09-10. The registry PDF lists the same licence number and Medium Rare N.V., company number 145353. The registry PDF gives an issued date of 9 December 2025 and an expiry date of 9 June 2026. The registry PDF gives a different status: "Assessment in progress". RTP Ledger does not resolve this discrepancy between the two regulator-published sources. Checked 2026-09-13 | Documented· 1 supported statement The regulator certificate names trustdice.win, Satoshi Gaming Group N.V. and licence OGL/2024/664/0280. The certificate lists the licence as Active and names 16/07/2024 as the grant date. The terms cite the same licence number and the Curaçao Gaming Authority. The Curaçao Gaming Control Board's bulk licence registry PDF, dated 2026-09-10, lists the same licence number, company and company number with the status Indefinite. Checked 2026-09-13 |
| 03Country restrictions | Documented· 1 supported statement The global terms enumerate 45 prohibited jurisdictions and prohibit VPN or proxy location manipulation; a named region is not silently expanded to an entire country. Checked 2026-08-01 | Documented· 1 supported statement Clause 3.6 of the terms names 11 jurisdictions and the Dutch Caribbean islands as restricted. Section 2 of the AML policy names a shorter, different list of restricted regions. The AML list adds Cuba, Iran, North Korea, Syria and Crimea, absent from the terms list. France, the United Kingdom, Australia and Spain appear on both lists. The two published lists do not match. Neither list claims to be complete. Checked 2026-09-12 |
| 04Account journey and closure | Partial evidence· 1 supported statement The public terms state the age condition and contractual registration step. Coverage gaps: observed verification journey, observed account-closure journey. Checked 2026-08-01 | Not checked· 0 supported statements Registration, verification stages, account currency and closure journey are not checked. No dated source |
| 05Payment catalogue | Documented· 26 supported statements 9 payments.asset_withdrawal_table records cover BTC, DOGE, ETH, LTC, SOL, TRX, USDC, USDT, XRP. Each record follows the same documented pattern: BTC appears in Stake's public asset-level withdrawal table. The source does not bind the row to a specific network, so RTP Ledger does not treat it as an exact route claim. 17 payments.route_catalogue records cover BTC on Bitcoin, DOGE on Dogecoin, ETH on ERC-20, ETH on BEP-20, LTC on Litecoin, SOL on Solana, TRX on TRC-20, USDC on ERC-20, USDC on BEP-20, USDC on Polygon, USDC on Solana, USDT on ERC-20, USDT on BEP-20, USDT on Polygon, USDT on TRC-20, USDT on Solana, XRP on XRP Ledger. Each record follows the same documented pattern: BTC and Bitcoin appear together in Stake's accepted-networks table for deposits. RTP Ledger does not transfer asset-level withdrawal minimums or fees onto this route. Checked 2026-08-02 | Documented· 1 supported statement The English homepage names BTC, ETH, USDT, LTC and DOGE as supported assets, with USDT on the TRON (TRC20) or Ethereum (ERC20) network. The page states that the exact list of currencies and networks must be checked in the cashier before a transfer. No minimums or fees are published there. Checked 2026-09-12 |
| 06Deposit terms | Partial evidence· 1 supported statement RTP Ledger checked the public crypto withdrawal table, but it does not establish exact deposit-route terms. Deposit minimums, fees, confirmation requirements and crediting stages remain unknown. Coverage gaps: deposit.route_terms. Checked 2026-08-02 | Partial evidence· 1 supported statement The terms set a 10 USDT minimum before withdrawal, tied to a wagering rule rather than to each deposit. No checked page states deposit confirmation counts or crediting stages. Coverage gaps: deposit.route_terms. No dated source |
| 07Withdrawal terms | Partial evidence· 1 supported statement The public terms describe four material withdrawal conditions but do not provide an observed processing time. Coverage gaps: first-party withdrawal processing observation. Checked 2026-08-01 | Partial evidence· 2 supported statements Clause 5.1 states withdrawals usually complete within one hour, and up to 48 hours in some cases. Clauses 5.9 and 5.10 set a 10 USDT minimum deposit and 5 times wagering before withdrawal. Clause 5.6 caps high-value withdrawals at 1,000,000 USDT, or the equivalent, per month. RTP Ledger has not observed a withdrawal on trustdice.win. Actual processing time and effective fees are not established. Coverage gaps: first-party withdrawal processing observation. Checked 2026-09-12 |
| 08Bonus terms | Partial evidence· 1 supported statement Stake publishes that a valid affiliate code entered within 24 hours unlocks rakeback equal to 3.5% of house edge. RTP Ledger does not infer a fixed deposit-match amount, wagering requirement or account-specific eligibility. Coverage gaps: bonus.account_eligibility_and_expiry. Checked 2026-08-02 | Partial evidence· 1 supported statement The promotions page for the welcome package returned HTTP 403 today. An internal record from 19 August 2026 documents a three-deposit match package. The 19 August record has no fresh confirmation against a reachable live page today. Coverage gaps: bonus.economic_terms, bonus.account_eligibility_and_expiry. Checked 2026-09-12 |
| 09KYC and source-of-funds process | Partial evidence· 1 supported statement Published records support possible withdrawal KYC and a detailed source-of-income document list, not the trigger timing for a specific account. Coverage gaps: observed KYC trigger and stage. Checked 2026-08-02 | Partial evidence· 3 supported statements Clause 5.3 allows an identity check for withdrawals over 1 BTC or 2000 EUR. Clause 5.3 also allows a check on any withdrawal amount, at TrustDice's discretion. Clause 4.5 allows an identity check on deposits, including a selfie with documents. The privacy policy lists passport scans, payment slips and bank statements as accepted proofs. The homepage tells players that no personal data or KYC checks are needed to register. Clause 5.3 of the terms requires an identity check above set withdrawal thresholds. Clause 4.5 also allows an identity check on a deposit. The marketing line and the terms describe two different account journeys. RTP Ledger has not run a test account on trustdice.win. The stage where verification is requested in practice is not established. Coverage gaps: observed KYC trigger and stage. Checked 2026-09-12 |
| 10Responsible-gambling controls | Documented· 2 supported statements The help centre publishes loss and wager limits plus a delay before an increase takes effect. The help centre publishes both indefinite self-exclusion and shorter break-in-play options. Checked 2026-08-02 | Documented· 2 supported statements Section 8 of the responsible gaming page offers limits on deposits, wagers, losses and session time. The system blocks further play once a chosen limit is reached. Clause 6.1 lets a player self-exclude by emailing compliance@trustdice.win from the registered address. The terms do not publish fixed self-exclusion duration tiers. Checked 2026-09-12 |
| 11RTP Ledger cashout test | Partial evidence· 1 supported statement RTP Ledger has not registered a completed Stake cashout observation. Published withdrawal rules are not a substitute for a first-party cashout test. Coverage gaps: cashout.first_party_observation. No dated source | Partial evidence· 1 supported statement RTP Ledger has not withdrawn funds from a trustdice.win test account. Cashout speed and fees are not observed. Coverage gaps: cashout.first_party_observation. No dated source |
| 12Complaint handling | Not checked· 0 supported statements Complaint handling and resolution outcomes are not checked in a dated source record. No dated source | Not checked· 0 supported statements Complaint handling and resolution outcomes are not checked in a dated source record. No dated source |
| 13Ownership and related brands | Partial evidence· 1 supported statement The terms call both payment-processing companies wholly owned subsidiaries. Coverage gaps: parent/legal-group relationship, related-brand relationship. Checked 2026-08-01 | Not checked· 0 supported statements Parent, sister-brand and material operating relationships are not checked. No dated source |
| 14Game catalogue and RTP evidence | Documented· 1 supported statement The public Stake Engine catalogue lists game, RTP and event-count records for each mode. RTP Ledger has no permanent archived copy of the catalogue. RTP Ledger does not infer account-specific availability from the catalogue. Checked 2026-08-01 | Not checked· 0 supported statements Casino-specific game availability and deployed RTP evidence are not checked. No dated source |
| 15Fairness and verification | Partial evidence· 1 supported statement Stake publishes the algorithm and inputs for supported verifiable bets. Coverage gaps: reproduced account-bet verification. Checked 2026-08-01 | Partial evidence· 2 supported statements TrustDice Originals show a server-seed hash, client seed and nonce for verification. A player can enter the seed values into a verification tool to check a round. Third-party slots and live-dealer games instead rely on the provider's own certified systems. RTP Ledger has not reproduced a TrustDice Originals bet with the published verification tool. Independent confirmation of a real result is not established. Coverage gaps: reproduced account-bet verification. Checked 2026-09-12 |
| 16Account and withdrawal security | Partial evidence· 2 supported statements The help centre documents 2FA coverage and activation. The help centre documents an extra withdrawal authentication step for supported social logins. Coverage gaps: recovery and session controls. Checked 2026-08-01 | Not checked· 0 supported statements Two-factor authentication (2FA), recovery and withdrawal-protection controls are not checked. No dated source |
| 17Support and escalation | Partial evidence· 1 supported statement The terms publish the channels and stated availability, not observed response quality. Coverage gaps: timestamped support-response test. Checked 2026-08-01 | Partial evidence· 2 supported statements The homepage advertises 24/7 live support. General questions go to support@trustdice.win. Complaints and self-exclusion requests go to compliance@trustdice.win. RTP Ledger has not timed a support request on trustdice.win. Response times are not established. Coverage gaps: timestamped support-response test. Checked 2026-09-12 |
| 18Product and user experience | Not checked· 0 supported statements Product catalogue, devices and observed usability defects are not checked. No dated source | Not checked· 0 supported statements Product catalogue, devices and observed usability defects are not checked. No dated source |
| 19VIP and loyalty mechanics | Partial evidence· 1 supported statement The help centre names recurring promotion and loyalty mechanisms without proving account-specific value. Coverage gaps: effective VIP value and expiry. Checked 2026-08-01 | Not checked· 0 supported statements VIP earning, tiers, expiry and withdrawal interactions are not checked. No dated source |
| 20Privacy and data rights | Partial evidence· 2 supported statements The policy covers the main data lifecycle but does not publish a fixed duration for every category. The help centre distinguishes account closure from complete deletion. Coverage gaps: category-level retention schedule. Checked 2026-08-01 | Not checked· 0 supported statements Controller, collection, retention, transfers and deletion paths are not checked. No dated source |
What the research coverage shows
On 2026-09-27, Stake has 16 areas with source support. TrustDice has 9. These totals measure current RTP Ledger research coverage. They do not measure casino safety or service quality.
Current cashout rows, derived live from each dossier:
- Stake: partial evidence; 1 source-linked statement; 0 dated sources; no dated check.
- TrustDice: partial evidence; 1 source-linked statement; 0 dated sources; no dated check.
The comparison does not infer a completed account test from operator-published terms or from another evidence area.
For an asset/network view, use the Money Hub. For the complete publication rules, read the casino evidence methodology.
Optional operator links, after the evidence
The Stake and TrustDice operator buttons are sponsored affiliate links. RTP Ledger may earn a commission from them. Commercial status does not change evidence status, research order, or publication rules. Verify current operator terms before you deposit.
5savePublisher-supplied campaign code. It does not confirm bonus eligibility or terms.
18+. Gambling involves risk and is not a way to make money. Check local rules, set limits and never gamble money you cannot afford to lose. Get free support at BeGambleAware.org.