Shuffle vs Stake: 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: unknown. The checked source did not establish full offer terms; see the source check
Mechanism on record: rakeback. The checked source did not establish full offer terms; see the source check
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 | Shuffle | Stake |
|---|---|---|
| Licence | Documented · 2026-09-13 | Documented · 2026-09-13 |
| Payment routes | Documented · 2026-09-12 | Documented · 2026-08-02 |
| Deposit terms | Partial | Partial · 2026-08-02 |
| Withdrawal terms | Partial · 2026-09-12 | Partial · 2026-08-01 |
| Bonus terms | Partial · 2026-09-12 | Partial · 2026-08-02 |
| KYC / verification | Partial · 2026-09-12 | Partial · 2026-08-02 |
| Cashout observation | Partial | Partial |
What the documented record separates
- Bonus mechanism: Shuffle's recorded mechanism is not established; the checked source did not establish full terms. Stake's recorded mechanism is rakeback; the checked source did not establish full terms. A player comparing headline bonuses cannot verify either offer from the checked sources today.
- Research depth on RTP Ledger: Shuffle's record has source-backed claims in 8 of 20 areas. Stake's record has source-backed claims in 16 of 20 areas. Where a record is thin, verify directly with the operator before depositing.
Shuffle
- Research tier
- Source-reviewed record
- Areas with source support
- 8/20
- Source-linked statements
- 15
- First-party test areas
- 0
- Unique sources
- 7
- Latest dated evidence
- 2026-09-13
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
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 | Documented· 1 supported statement The terms name Natural Nine B.V. as the owner and operator of shuffle.com. The regulator certificate binds the same company and company number to the domain. Checked 2026-09-12 | 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 | Documented· 1 supported statement The regulator certificate lists shuffle.com, Natural Nine B.V., licence number OGL/2024/1337/0628 and an active status. The terms cite the same licence number. 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 | 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 |
| 03Country restrictions | Documented· 1 supported statement Clause 8.3 names 14 prohibited jurisdictions. The list runs from Australia to the United States and includes the United Kingdom, Germany, France, Spain, Sweden and the Netherlands. The clause also excludes sanctioned or unlicensable locations. Checked 2026-09-12 | 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 |
| 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 | Documented· 1 supported statement The help-centre article lists every asset accepted for deposits and withdrawals. It names the supported networks for each asset, for example USDT on ERC20, BEP20, TRC20, POL and SOL. Deposits on other networks are not guaranteed to be retrievable. Checked 2026-09-12 | 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 | Partial evidence· 1 supported statement The terms and the supported-assets article name the accepted assets and networks, but they do not state deposit minimums, confirmation requirements or crediting stages. Coverage gaps: deposit.route_terms. 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 | Partial evidence· 2 supported statements Clause 10.2 sets a 100% wagering rule per deposit. Same-wallet, same-network digital-asset withdrawals are exempt. Clauses 10.6 and 10.7 state that the minimum amount and any fee appear in the cashier before confirmation. No fixed figures are published. RTP Ledger has not observed a withdrawal on shuffle.com, so processing time and effective fees are not established. Coverage gaps: first-party withdrawal processing observation. Checked 2026-09-12 | 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 | Partial evidence· 1 supported statement The help-centre article that documented the 100% first-deposit bonus on 2026-08-19 no longer exists, and the bonuses collection lists only weekly, monthly and reload bonuses. RTP Ledger no longer presents the first-deposit offer as documented. Coverage gaps: bonus.economic_terms, bonus.account_eligibility_and_expiry. Checked 2026-09-12 | 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 | Partial evidence· 2 supported statements Clause 5.2 of the terms requires an identity check at a threshold and before the first withdrawal. Accepted documents are a passport, a national identity card or a driving licence. The AML policy adds enhanced due diligence with source-of-funds and source-of-wealth documents. It also allows a withdrawal freeze at a risk-based threshold. RTP Ledger has not run a test account on shuffle.com, so the stage at which verification is requested in practice is not established. Coverage gaps: observed KYC trigger and stage. Checked 2026-09-12 | 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 | Documented· 2 supported statements Clause 8 of the responsible gambling policy offers limits on the amount wagered or lost within a chosen period, set daily, weekly or monthly. Clause 4 lists self-exclusion periods of 1 day, 1 week, 1 month, 6 months or permanent. Clause 9 links BeGambleAware, Gordon Moody, the Responsible Gambling Council and Gamtalk. Checked 2026-09-12 | 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 | Partial evidence· 1 supported statement RTP Ledger has not withdrawn funds from a shuffle.com test account, so cashout speed and fees are not observed. Coverage gaps: cashout.first_party_observation. 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 | Partial evidence· 2 supported statements Clauses 18.1 and 18.2 of the terms route complaints to customer support by email. A complaint the operator cannot resolve can go to the regulator. RTP Ledger has not timed a support request on shuffle.com, so response times are not established. Coverage gaps: timestamped support-response test. Checked 2026-09-12 | 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-09-27, Shuffle has 8 areas with source support. Stake has 16. 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:
- Shuffle: partial evidence; 1 source-linked statement; 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.
acesPublisher-supplied campaign code. It does not confirm bonus eligibility or terms.
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.