Shuffle vs Stake: evidence coverage across 20 areas
This page compares the depth and traceability of RTP Ledger research. Both casino records use the same fixed structure. You can see documented evidence, partial work, and areas that RTP Ledger has not checked. The comparison is not a casino score or recommendation.
Shuffle
- Research tier
- Research record in progress
- Areas with source support
- 0/20
- Source-linked statements
- 0
- First-party test areas
- 0
- Unique sources
- 3
- Latest dated evidence
- 2026-08-19
Stake
- Research tier
- Source-reviewed record
- Areas with source support
- 16/20
- Source-linked statements
- 46
- First-party test areas
- 0
- Unique sources
- 16
- Latest dated evidence
- 2026-08-02
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 | Shuffle | Stake |
|---|---|---|
| 01Legal operator identity | Partial evidence· 0 supported statements A legacy operator name exists. RTP Ledger withholds the name from the decision record until a source covers the domain. No dated source | Documented· 1 supported statement The operator and regulator records bind Medium Rare N.V. to stake.com. Checked 2026-08-02 |
| 02Licence and domain coverage | Partial evidence· 0 supported statements A legacy licence category exists. The record has no sources for the entity, number, domain coverage or current regulator status. No dated source | Documented· 1 supported statement The regulator certificate listed the covered domain, licensee, number and active status. Checked 2026-08-02 |
| 03Country restrictions | Documented· 0 supported statements 11 restricted jurisdictions are reported in the checked terms. Availability still depends on the player's location and current operator rules. Checked 2026-07-13 | Documented· 1 supported statement The global terms enumerate 44 prohibited jurisdictions and prohibit VPN or proxy location manipulation; a named region is not silently expanded to an entire country. Checked 2026-08-01 |
| 04Account journey and closure | Not checked· 0 supported statements Registration, verification stages, account currency and closure journey are not checked. No dated source | 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 |
| 05Payment catalogue | Partial evidence· 0 supported statements 9 crypto assets appear in checked published material. Deposit and withdrawal direction are not checked separately; limits and fees are shown only where published. Checked 2026-07-11 | 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 |
| 06Deposit terms | Not checked· 0 supported statements Deposit minimums, fees, conversion and crediting stages are not checked by route. No dated source | 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 |
| 07Withdrawal terms | Not checked· 0 supported statements Withdrawal limits, fees, pending rules and approval stages are not checked by route. No dated source | 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 |
| 08Bonus terms | Documented· 0 supported statements The checked source documents the bonus mechanics. Missing fields remain unknown. Checked 2026-08-19 | 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 |
| 09KYC and source-of-funds process | Not checked· 0 supported statements KYC and source-of-funds handling are not checked in a sourced claim. No dated source | 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 |
| 10Responsible-gambling controls | Not checked· 0 supported statements Self-exclusion, limits, cooling-off and their access paths are not checked. No dated source | 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 |
| 11RTP Ledger cashout test | Not checked· 0 supported statements RTP Ledger cashout testing is not checked or claimed for this casino. No dated source | 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 |
| 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 | Not checked· 0 supported statements Parent, sister-brand and material operating relationships are not checked. No dated source | 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 |
| 14Game catalogue and RTP evidence | Not checked· 0 supported statements Casino-specific game availability and deployed RTP evidence are not checked. No dated source | 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 |
| 15Fairness and verification | Not checked· 0 supported statements Audit certificates and reproducible provably-fair implementations are not checked. No dated source | 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 |
| 16Account and withdrawal security | Not checked· 0 supported statements Two-factor authentication (2FA), recovery and withdrawal-protection controls are not checked. No dated source | 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 |
| 17Support and escalation | Not checked· 0 supported statements Published support access and timestamped response tests are not checked. No dated source | 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 |
| 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 | Not checked· 0 supported statements VIP earning, tiers, expiry and withdrawal interactions are not checked. No dated source | 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 |
| 20Privacy and data rights | Not checked· 0 supported statements Controller, collection, retention, transfers and deletion paths are not checked. No dated source | 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 |
What the research coverage shows
On 2026-08-19, Stake has 16 areas with source support. Shuffle has 0. The Stake and Shuffle source-support totals measure current RTP Ledger research coverage. They do not measure casino safety or service quality.
Current cashout rows, derived live from each dossier:
- Shuffle: not checked; 0 source-linked statements; 0 dated sources; no dated check.
- Stake: 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 Shuffle and Stake 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.
acesUse this if signup asks for a code.
5saveUse this if signup asks for a code.
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.