RTPLEDGER
RTP LEDGER / CASINO RESEARCH RECORD6 documented · 12 partial · 2 not checked

Stake casino evidence review

This review covers 20 decision areas for Stake, including identity, payments, KYC, player protection, game math, security and service. It identifies each checked area, dated source, RTP Ledger test and unknown state.

Stake
stake.com
Dated source records
6
Partial records
12
Still not checked
2

Evidence record maintained by: RTP Ledger Casino Review Team

Latest dated source in this research record: 2026-08-02
Optional operator link

Review the open evidence gaps before visiting the operator

The research record lists the documented evidence and the open questions. Before you send funds, confirm country access, cashier routes, KYC requirements and current terms with the operator.

Partner linkCommercial
Stake
stake.com
Before you continueCheck the live offer, country access and cashier terms at the operator.
Referral / promo code5save

Use this if signup asks for a code.

Check live terms at Stake(opens in a new tab)
RTP Ledger may earn a commission from this affiliate link. How this works
18+ · Terms apply · Play responsibly
Read the full, source-checked bonus terms →
AdvertisementCasino partners

Other casino partners to compare

Paid alternatives with direct access to their research records. Compare payment routes, restrictions and live terms before choosing.

Partner records
4
Live links
4

Scroll to compare every partner →

Featured partnerCommercial

Shuffle

shuffle.com

Clear public welcome mechanics with the important limits visible.

  • Wager races
  • Weekly bonuses
Referral / promo codeaces

Use this if signup asks for a code.

See Shuffle's live offer(opens in a new tab)
Affiliate link — RTP Ledger may earn a commission. Disclosure
18+ · T&Cs apply · Play responsibly
Featured partnerCommercial

TrustDice

trustdice.win

Documented four-deposit welcome package with the material limits visible.

  • Free faucet
  • Provably fair originals
See TrustDice's live offer(opens in a new tab)
Affiliate link — RTP Ledger may earn a commission. Disclosure
18+ · T&Cs apply · Play responsibly
Featured partnerCommercial

Bitstarz

bitstarz.com

Public four-deposit welcome-package mechanics with material limits visible.

  • Big slots catalogue
  • Crypto + fiat
Referral / promo codeSPINNER

Use this if signup asks for a code.

See BitStarz's live offer(opens in a new tab)
Affiliate link — RTP Ledger may earn a commission. Disclosure
18+ · T&Cs apply · Play responsibly
PartnerCommercial

Roobet

roobet.com

Slots-heavy crypto casino with streamer culture and the RooWards loyalty ladder.

  • RooWards loyalty
  • Daily rakeback tiers
Referral / promo coderakeback

Use this if signup asks for a code.

Visit Roobet · check live terms(opens in a new tab)
Affiliate link — RTP Ledger may earn a commission. Disclosure
18+ · T&Cs apply · Play responsibly

Sponsorship never changes RTP records, source status or editorial order.

Open all casino research →
Research record

Evidence and gaps for player decisions

The record covers 20 areas: access, payments, protection, game math and service. The record separates published claims from RTP Ledger observations. Areas without evidence have an unknown status.

Identity and access

4 / 20

  1. Legal operator identity

    Documented
    Published source

    The operator and regulator records bind Medium Rare N.V. to stake.com.

    Scope: Domain: stake.com; Account scope: public

    Checked 2026-08-02Curaçao Gaming Authority certificate ↗Stake terms ↗
    Claim records · 1
    • stake.operator.legal-entity· Confirmed within scope
      Field: operator.legal_entity
      Recorded value: Medium Rare N.V.; company number 145353
      Claim summary: The operator and regulator records bind Medium Rare N.V. to stake.com.
      What the claim covers: domain=stake.com; account=public
      Evidence basis: Published source
      Checked: 2026-08-02 · Next review: 2026-09-01
      Record owner: desk:casino-reviews
      Independent review pending
      Recorded change history · 2
      1. stake.operator.legal-entity.created.2026-08-01
        Initial record · Changed: 2026-08-01
        Recorded value: Medium Rare N.V.; company number 145353 · Confirmed within scope
        Reason: Initial claim record created from the dated source review.
      2. stake.operator.legal-entity.revised.source-snapshots.2026-08-02
        Revised record · Changed: 2026-08-02
        Previous value: Medium Rare N.V.; company number 145353
        Recorded value: Medium Rare N.V.; company number 145353 · Confirmed within scope
        Reason: Linked unchanged source records to archived source copies captured on 2026-08-02.
      Curaçao Gaming Authority certificate ↗ · Sources for the claim: Domain, company number, operator and licence relationship.
      Source access status: reachable · 2026-08-02 · Archived source copy: stake.cga-certificate.7a8a18f2fb3a0d25f56db5fbd809495cae593cee130b452f37d6e1e4e6634387 · SHA-256 7a8a18f2fb3a0d25f56db5fbd809495cae593cee130b452f37d6e1e4e6634387
      Stake terms ↗ · Sources for the claim: Operator, contract, account, withdrawal, KYC, support and jurisdiction clauses.
      Source access status: not independently recorded · Archived source copy pending

  2. Licence and domain coverage

    Documented
    Published source

    The regulator certificate listed the covered domain, licensee, number and active status.

    Scope: Domain: stake.com; Account scope: public

    Checked 2026-08-02Curaçao Gaming Authority certificate ↗Stake terms ↗
    Claim records · 1
    • stake.licence.cga-status· Confirmed within scope
      Field: licence.cga.status
      Recorded value: OGL/2024/1451/0918; Active when checked
      Claim summary: The regulator certificate listed the covered domain, licensee, number and active status.
      What the claim covers: domain=stake.com; account=public
      Evidence basis: Published source
      Checked: 2026-08-02 · Next review: 2026-09-01
      Record owner: desk:casino-reviews
      Independent review pending
      Recorded change history · 2
      1. stake.licence.cga-status.created.2026-08-01
        Initial record · Changed: 2026-08-01
        Recorded value: OGL/2024/1451/0918; Active when checked · Confirmed within scope
        Reason: Initial claim record created from the dated source review.
      2. stake.licence.cga-status.revised.source-snapshots.2026-08-02
        Revised record · Changed: 2026-08-02
        Previous value: OGL/2024/1451/0918; Active when checked
        Recorded value: OGL/2024/1451/0918; Active when checked · Confirmed within scope
        Reason: Linked unchanged source records to archived source copies captured on 2026-08-02.
      Curaçao Gaming Authority certificate ↗ · Sources for the claim: Domain, company number, operator and licence relationship.
      Source access status: reachable · 2026-08-02 · Archived source copy: stake.cga-certificate.7a8a18f2fb3a0d25f56db5fbd809495cae593cee130b452f37d6e1e4e6634387 · SHA-256 7a8a18f2fb3a0d25f56db5fbd809495cae593cee130b452f37d6e1e4e6634387
      Stake terms ↗ · Sources for the claim: Operator, contract, account, withdrawal, KYC, support and jurisdiction clauses.
      Source access status: not independently recorded · Archived source copy pending

  3. Country restrictions

    Documented
    Published source

    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.

    Scope: Domain: stake.com; Market: global terms; market and regional eligibility still require current local verification; Account scope: public

    Checked 2026-08-01Stake terms ↗
    Claim records · 1
    • stake.country.prohibited-jurisdictions· Confirmed within scope
      Field: country.restricted_markets
      Recorded value: 44 prohibited jurisdictions in the global stake.com terms; regional carve-outs require market-level reading
      Claim summary: 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.
      What the claim covers: domain=stake.com; market=global terms; market and regional eligibility still require current local verification; account=public
      Evidence basis: Published source
      Checked: 2026-08-01 · Next review: 2026-09-01
      Record owner: desk:casino-reviews
      Independent review pending
      Recorded change history · 1
      1. stake.country.prohibited-jurisdictions.created.2026-08-01
        Initial record · Changed: 2026-08-01
        Recorded value: 44 prohibited jurisdictions in the global stake.com terms; regional carve-outs require market-level reading · Confirmed within scope
        Reason: Initial claim record created from the dated source review.
      Stake terms ↗ · Sources for the claim: Operator, contract, account, withdrawal, KYC, support and jurisdiction clauses.
      Source access status: not independently recorded · Archived source copy pending

  4. Account journey and closure

    Partial evidence
    Published source

    The public terms state the age condition and contractual registration step. Coverage gaps: observed verification journey, observed account-closure journey.

    Scope: Domain: stake.com; Account scope: public

    Checked 2026-08-01Stake terms ↗
    Claim records · 1
    • stake.account.age-contract· Confirmed within scope
      Field: account.registration_contract
      Recorded value: 18+ or higher local age; registration creates the player contract
      Claim summary: The public terms state the age condition and contractual registration step.
      What the claim covers: domain=stake.com; account=public
      Evidence basis: Published source
      Checked: 2026-08-01 · Next review: 2026-09-01
      Record owner: desk:casino-reviews
      Independent review pending
      Recorded change history · 1
      1. stake.account.age-contract.created.2026-08-01
        Initial record · Changed: 2026-08-01
        Recorded value: 18+ or higher local age; registration creates the player contract · Confirmed within scope
        Reason: Initial claim record created from the dated source review.
      Stake terms ↗ · Sources for the claim: Operator, contract, account, withdrawal, KYC, support and jurisdiction clauses.
      Source access status: not independently recorded · Archived source copy pending

Money movement and verification

5 / 20

  1. Payment catalogue

    Documented
    Published source

    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.

    Scope: Domain: stake.com; Account scope: public; Asset: BTC, DOGE, ETH, LTC, SOL, TRX, USDC, USDT, XRP; Network: not specified in public table, bitcoin, dogecoin, erc20, bep20, litecoin, solana, trc20, polygon, xrp-ledger; Direction: withdrawal, deposit

    Checked 2026-08-02Stake crypto withdrawal limits ↗Stake accepted blockchain networks ↗
    Claim records · 26
    • stake.payments.withdrawal-table.btc· Confirmed within scope
      Field: payments.asset_withdrawal_table
      Recorded value: BTC
      Claim summary: 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.
      What the claim covers: domain=stake.com; account=public; asset=BTC; network=not specified in public table; direction=withdrawal
      Evidence basis: Published source
      Checked: 2026-08-02 · Next review: 2026-09-01
      Record owner: desk:casino-reviews
      Independent review pending
      Recorded change history · 2
      1. stake.payments.withdrawal-table.btc.created.2026-08-01
        Initial record · Changed: 2026-08-01
        Recorded value: BTC · Confirmed within scope
        Reason: Initial claim record created from the dated source review.
      2. stake.payments.withdrawal-table.btc.revised.source-snapshots.2026-08-02
        Revised record · Changed: 2026-08-02
        Previous value: BTC
        Recorded value: BTC · Confirmed within scope
        Reason: Linked unchanged source records to archived source copies captured on 2026-08-02.
      Stake crypto withdrawal limits ↗ · Sources for the claim: Published asset-level withdrawal minimum and fee table; the page does not bind each value to a network.
      Source access status: reachable · 2026-08-02 · Archived source copy: stake.withdrawal-table.a482b45ed4f174f789cc7ce38361a9493fb14a85f0357c20e165e079b9a7b243 · SHA-256 a482b45ed4f174f789cc7ce38361a9493fb14a85f0357c20e165e079b9a7b243
    • stake.payments.withdrawal-table.doge· Confirmed within scope
      Field: payments.asset_withdrawal_table
      Recorded value: DOGE
      Claim summary: DOGE 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.
      What the claim covers: domain=stake.com; account=public; asset=DOGE; network=not specified in public table; direction=withdrawal
      Evidence basis: Published source
      Checked: 2026-08-02 · Next review: 2026-09-01
      Record owner: desk:casino-reviews
      Independent review pending
      Recorded change history · 2
      1. stake.payments.withdrawal-table.doge.created.2026-08-01
        Initial record · Changed: 2026-08-01
        Recorded value: DOGE · Confirmed within scope
        Reason: Initial claim record created from the dated source review.
      2. stake.payments.withdrawal-table.doge.revised.source-snapshots.2026-08-02
        Revised record · Changed: 2026-08-02
        Previous value: DOGE
        Recorded value: DOGE · Confirmed within scope
        Reason: Linked unchanged source records to archived source copies captured on 2026-08-02.
      Stake crypto withdrawal limits ↗ · Sources for the claim: Published asset-level withdrawal minimum and fee table; the page does not bind each value to a network.
      Source access status: reachable · 2026-08-02 · Archived source copy: stake.withdrawal-table.a482b45ed4f174f789cc7ce38361a9493fb14a85f0357c20e165e079b9a7b243 · SHA-256 a482b45ed4f174f789cc7ce38361a9493fb14a85f0357c20e165e079b9a7b243
    • stake.payments.withdrawal-table.eth· Confirmed within scope
      Field: payments.asset_withdrawal_table
      Recorded value: ETH
      Claim summary: ETH 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.
      What the claim covers: domain=stake.com; account=public; asset=ETH; network=not specified in public table; direction=withdrawal
      Evidence basis: Published source
      Checked: 2026-08-02 · Next review: 2026-09-01
      Record owner: desk:casino-reviews
      Independent review pending
      Recorded change history · 2
      1. stake.payments.withdrawal-table.eth.created.2026-08-01
        Initial record · Changed: 2026-08-01
        Recorded value: ETH · Confirmed within scope
        Reason: Initial claim record created from the dated source review.
      2. stake.payments.withdrawal-table.eth.revised.source-snapshots.2026-08-02
        Revised record · Changed: 2026-08-02
        Previous value: ETH
        Recorded value: ETH · Confirmed within scope
        Reason: Linked unchanged source records to archived source copies captured on 2026-08-02.
      Stake crypto withdrawal limits ↗ · Sources for the claim: Published asset-level withdrawal minimum and fee table; the page does not bind each value to a network.
      Source access status: reachable · 2026-08-02 · Archived source copy: stake.withdrawal-table.a482b45ed4f174f789cc7ce38361a9493fb14a85f0357c20e165e079b9a7b243 · SHA-256 a482b45ed4f174f789cc7ce38361a9493fb14a85f0357c20e165e079b9a7b243
    • stake.payments.withdrawal-table.ltc· Confirmed within scope
      Field: payments.asset_withdrawal_table
      Recorded value: LTC
      Claim summary: LTC 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.
      What the claim covers: domain=stake.com; account=public; asset=LTC; network=not specified in public table; direction=withdrawal
      Evidence basis: Published source
      Checked: 2026-08-02 · Next review: 2026-09-01
      Record owner: desk:casino-reviews
      Independent review pending
      Recorded change history · 2
      1. stake.payments.withdrawal-table.ltc.created.2026-08-01
        Initial record · Changed: 2026-08-01
        Recorded value: LTC · Confirmed within scope
        Reason: Initial claim record created from the dated source review.
      2. stake.payments.withdrawal-table.ltc.revised.source-snapshots.2026-08-02
        Revised record · Changed: 2026-08-02
        Previous value: LTC
        Recorded value: LTC · Confirmed within scope
        Reason: Linked unchanged source records to archived source copies captured on 2026-08-02.
      Stake crypto withdrawal limits ↗ · Sources for the claim: Published asset-level withdrawal minimum and fee table; the page does not bind each value to a network.
      Source access status: reachable · 2026-08-02 · Archived source copy: stake.withdrawal-table.a482b45ed4f174f789cc7ce38361a9493fb14a85f0357c20e165e079b9a7b243 · SHA-256 a482b45ed4f174f789cc7ce38361a9493fb14a85f0357c20e165e079b9a7b243
    • stake.payments.withdrawal-table.sol· Confirmed within scope
      Field: payments.asset_withdrawal_table
      Recorded value: SOL
      Claim summary: SOL 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.
      What the claim covers: domain=stake.com; account=public; asset=SOL; network=not specified in public table; direction=withdrawal
      Evidence basis: Published source
      Checked: 2026-08-02 · Next review: 2026-09-01
      Record owner: desk:casino-reviews
      Independent review pending
      Recorded change history · 2
      1. stake.payments.withdrawal-table.sol.created.2026-08-01
        Initial record · Changed: 2026-08-01
        Recorded value: SOL · Confirmed within scope
        Reason: Initial claim record created from the dated source review.
      2. stake.payments.withdrawal-table.sol.revised.source-snapshots.2026-08-02
        Revised record · Changed: 2026-08-02
        Previous value: SOL
        Recorded value: SOL · Confirmed within scope
        Reason: Linked unchanged source records to archived source copies captured on 2026-08-02.
      Stake crypto withdrawal limits ↗ · Sources for the claim: Published asset-level withdrawal minimum and fee table; the page does not bind each value to a network.
      Source access status: reachable · 2026-08-02 · Archived source copy: stake.withdrawal-table.a482b45ed4f174f789cc7ce38361a9493fb14a85f0357c20e165e079b9a7b243 · SHA-256 a482b45ed4f174f789cc7ce38361a9493fb14a85f0357c20e165e079b9a7b243
    • stake.payments.withdrawal-table.trx· Confirmed within scope
      Field: payments.asset_withdrawal_table
      Recorded value: TRX
      Claim summary: TRX 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.
      What the claim covers: domain=stake.com; account=public; asset=TRX; network=not specified in public table; direction=withdrawal
      Evidence basis: Published source
      Checked: 2026-08-02 · Next review: 2026-09-01
      Record owner: desk:casino-reviews
      Independent review pending
      Recorded change history · 2
      1. stake.payments.withdrawal-table.trx.created.2026-08-01
        Initial record · Changed: 2026-08-01
        Recorded value: TRX · Confirmed within scope
        Reason: Initial claim record created from the dated source review.
      2. stake.payments.withdrawal-table.trx.revised.source-snapshots.2026-08-02
        Revised record · Changed: 2026-08-02
        Previous value: TRX
        Recorded value: TRX · Confirmed within scope
        Reason: Linked unchanged source records to archived source copies captured on 2026-08-02.
      Stake crypto withdrawal limits ↗ · Sources for the claim: Published asset-level withdrawal minimum and fee table; the page does not bind each value to a network.
      Source access status: reachable · 2026-08-02 · Archived source copy: stake.withdrawal-table.a482b45ed4f174f789cc7ce38361a9493fb14a85f0357c20e165e079b9a7b243 · SHA-256 a482b45ed4f174f789cc7ce38361a9493fb14a85f0357c20e165e079b9a7b243
    • stake.payments.withdrawal-table.usdc· Confirmed within scope
      Field: payments.asset_withdrawal_table
      Recorded value: USDC
      Claim summary: USDC 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.
      What the claim covers: domain=stake.com; account=public; asset=USDC; network=not specified in public table; direction=withdrawal
      Evidence basis: Published source
      Checked: 2026-08-02 · Next review: 2026-09-01
      Record owner: desk:casino-reviews
      Independent review pending
      Recorded change history · 2
      1. stake.payments.withdrawal-table.usdc.created.2026-08-01
        Initial record · Changed: 2026-08-01
        Recorded value: USDC · Confirmed within scope
        Reason: Initial claim record created from the dated source review.
      2. stake.payments.withdrawal-table.usdc.revised.source-snapshots.2026-08-02
        Revised record · Changed: 2026-08-02
        Previous value: USDC
        Recorded value: USDC · Confirmed within scope
        Reason: Linked unchanged source records to archived source copies captured on 2026-08-02.
      Stake crypto withdrawal limits ↗ · Sources for the claim: Published asset-level withdrawal minimum and fee table; the page does not bind each value to a network.
      Source access status: reachable · 2026-08-02 · Archived source copy: stake.withdrawal-table.a482b45ed4f174f789cc7ce38361a9493fb14a85f0357c20e165e079b9a7b243 · SHA-256 a482b45ed4f174f789cc7ce38361a9493fb14a85f0357c20e165e079b9a7b243
    • stake.payments.withdrawal-table.usdt· Confirmed within scope
      Field: payments.asset_withdrawal_table
      Recorded value: USDT
      Claim summary: USDT 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.
      What the claim covers: domain=stake.com; account=public; asset=USDT; network=not specified in public table; direction=withdrawal
      Evidence basis: Published source
      Checked: 2026-08-02 · Next review: 2026-09-01
      Record owner: desk:casino-reviews
      Independent review pending
      Recorded change history · 2
      1. stake.payments.withdrawal-table.usdt.created.2026-08-01
        Initial record · Changed: 2026-08-01
        Recorded value: USDT · Confirmed within scope
        Reason: Initial claim record created from the dated source review.
      2. stake.payments.withdrawal-table.usdt.revised.source-snapshots.2026-08-02
        Revised record · Changed: 2026-08-02
        Previous value: USDT
        Recorded value: USDT · Confirmed within scope
        Reason: Linked unchanged source records to archived source copies captured on 2026-08-02.
      Stake crypto withdrawal limits ↗ · Sources for the claim: Published asset-level withdrawal minimum and fee table; the page does not bind each value to a network.
      Source access status: reachable · 2026-08-02 · Archived source copy: stake.withdrawal-table.a482b45ed4f174f789cc7ce38361a9493fb14a85f0357c20e165e079b9a7b243 · SHA-256 a482b45ed4f174f789cc7ce38361a9493fb14a85f0357c20e165e079b9a7b243
    • stake.payments.withdrawal-table.xrp· Confirmed within scope
      Field: payments.asset_withdrawal_table
      Recorded value: XRP
      Claim summary: XRP 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.
      What the claim covers: domain=stake.com; account=public; asset=XRP; network=not specified in public table; direction=withdrawal
      Evidence basis: Published source
      Checked: 2026-08-02 · Next review: 2026-09-01
      Record owner: desk:casino-reviews
      Independent review pending
      Recorded change history · 2
      1. stake.payments.withdrawal-table.xrp.created.2026-08-01
        Initial record · Changed: 2026-08-01
        Recorded value: XRP · Confirmed within scope
        Reason: Initial claim record created from the dated source review.
      2. stake.payments.withdrawal-table.xrp.revised.source-snapshots.2026-08-02
        Revised record · Changed: 2026-08-02
        Previous value: XRP
        Recorded value: XRP · Confirmed within scope
        Reason: Linked unchanged source records to archived source copies captured on 2026-08-02.
      Stake crypto withdrawal limits ↗ · Sources for the claim: Published asset-level withdrawal minimum and fee table; the page does not bind each value to a network.
      Source access status: reachable · 2026-08-02 · Archived source copy: stake.withdrawal-table.a482b45ed4f174f789cc7ce38361a9493fb14a85f0357c20e165e079b9a7b243 · SHA-256 a482b45ed4f174f789cc7ce38361a9493fb14a85f0357c20e165e079b9a7b243
    • stake.payments.deposit-route.btc.bitcoin· Confirmed within scope
      Field: payments.route_catalogue
      Recorded value: BTC on Bitcoin
      Claim summary: 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.
      What the claim covers: domain=stake.com; account=public; asset=BTC; network=bitcoin; direction=deposit
      Evidence basis: Published source
      Checked: 2026-08-02 · Next review: 2026-09-01
      Record owner: desk:casino-reviews
      Independent review pending
      Recorded change history · 2
      1. stake.payments.deposit-route.btc.bitcoin.created.2026-08-01
        Initial record · Changed: 2026-08-01
        Recorded value: BTC on Bitcoin · Confirmed within scope
        Reason: Initial claim record created from the dated source review.
      2. stake.payments.deposit-route.btc.bitcoin.revised.source-snapshots.2026-08-02
        Revised record · Changed: 2026-08-02
        Previous value: BTC on Bitcoin
        Recorded value: BTC on Bitcoin · Confirmed within scope
        Reason: Linked unchanged source records to archived source copies captured on 2026-08-02.
      Stake accepted blockchain networks ↗ · Sources for the claim: Stake's accepted-networks table pairs Bitcoin (BTC) with the native Bitcoin network.
      Source access status: reachable · 2026-08-02 · Archived source copy: stake.accepted-networks.ad7da5ee27ee4beb8a0570b72c915eb14b1c20092ac11405e4fed35f3e629a7b · SHA-256 ad7da5ee27ee4beb8a0570b72c915eb14b1c20092ac11405e4fed35f3e629a7b
    • stake.payments.deposit-route.doge.dogecoin· Confirmed within scope
      Field: payments.route_catalogue
      Recorded value: DOGE on Dogecoin
      Claim summary: DOGE and Dogecoin appear together in Stake's accepted-networks table for deposits. RTP Ledger does not transfer asset-level withdrawal minimums or fees onto this route.
      What the claim covers: domain=stake.com; account=public; asset=DOGE; network=dogecoin; direction=deposit
      Evidence basis: Published source
      Checked: 2026-08-02 · Next review: 2026-09-01
      Record owner: desk:casino-reviews
      Independent review pending
      Recorded change history · 2
      1. stake.payments.deposit-route.doge.dogecoin.created.2026-08-01
        Initial record · Changed: 2026-08-01
        Recorded value: DOGE on Dogecoin · Confirmed within scope
        Reason: Initial claim record created from the dated source review.
      2. stake.payments.deposit-route.doge.dogecoin.revised.source-snapshots.2026-08-02
        Revised record · Changed: 2026-08-02
        Previous value: DOGE on Dogecoin
        Recorded value: DOGE on Dogecoin · Confirmed within scope
        Reason: Linked unchanged source records to archived source copies captured on 2026-08-02.
      Stake accepted blockchain networks ↗ · Sources for the claim: Stake's accepted-networks table pairs Dogecoin (DOGE) with the native Dogecoin network.
      Source access status: reachable · 2026-08-02 · Archived source copy: stake.accepted-networks.ad7da5ee27ee4beb8a0570b72c915eb14b1c20092ac11405e4fed35f3e629a7b · SHA-256 ad7da5ee27ee4beb8a0570b72c915eb14b1c20092ac11405e4fed35f3e629a7b
    • stake.payments.deposit-route.eth.erc20· Confirmed within scope
      Field: payments.route_catalogue
      Recorded value: ETH on ERC-20
      Claim summary: ETH and ERC-20 appear together in Stake's accepted-networks table for deposits. RTP Ledger does not transfer asset-level withdrawal minimums or fees onto this route.
      What the claim covers: domain=stake.com; account=public; asset=ETH; network=erc20; direction=deposit
      Evidence basis: Published source
      Checked: 2026-08-02 · Next review: 2026-09-01
      Record owner: desk:casino-reviews
      Independent review pending
      Recorded change history · 2
      1. stake.payments.deposit-route.eth.erc20.created.2026-08-01
        Initial record · Changed: 2026-08-01
        Recorded value: ETH on ERC-20 · Confirmed within scope
        Reason: Initial claim record created from the dated source review.
      2. stake.payments.deposit-route.eth.erc20.revised.source-snapshots.2026-08-02
        Revised record · Changed: 2026-08-02
        Previous value: ETH on ERC-20
        Recorded value: ETH on ERC-20 · Confirmed within scope
        Reason: Linked unchanged source records to archived source copies captured on 2026-08-02.
      Stake accepted blockchain networks ↗ · Sources for the claim: Stake's accepted-networks table pairs Ethereum (ETH) with ERC-20.
      Source access status: reachable · 2026-08-02 · Archived source copy: stake.accepted-networks.ad7da5ee27ee4beb8a0570b72c915eb14b1c20092ac11405e4fed35f3e629a7b · SHA-256 ad7da5ee27ee4beb8a0570b72c915eb14b1c20092ac11405e4fed35f3e629a7b
    • stake.payments.deposit-route.eth.bep20· Confirmed within scope
      Field: payments.route_catalogue
      Recorded value: ETH on BEP-20
      Claim summary: ETH and BEP-20 appear together in Stake's accepted-networks table for deposits. RTP Ledger does not transfer asset-level withdrawal minimums or fees onto this route.
      What the claim covers: domain=stake.com; account=public; asset=ETH; network=bep20; direction=deposit
      Evidence basis: Published source
      Checked: 2026-08-02 · Next review: 2026-09-01
      Record owner: desk:casino-reviews
      Independent review pending
      Recorded change history · 2
      1. stake.payments.deposit-route.eth.bep20.created.2026-08-01
        Initial record · Changed: 2026-08-01
        Recorded value: ETH on BEP-20 · Confirmed within scope
        Reason: Initial claim record created from the dated source review.
      2. stake.payments.deposit-route.eth.bep20.revised.source-snapshots.2026-08-02
        Revised record · Changed: 2026-08-02
        Previous value: ETH on BEP-20
        Recorded value: ETH on BEP-20 · Confirmed within scope
        Reason: Linked unchanged source records to archived source copies captured on 2026-08-02.
      Stake accepted blockchain networks ↗ · Sources for the claim: Stake's accepted-networks table pairs Ethereum (ETH) with BSC (BEP-20).
      Source access status: reachable · 2026-08-02 · Archived source copy: stake.accepted-networks.ad7da5ee27ee4beb8a0570b72c915eb14b1c20092ac11405e4fed35f3e629a7b · SHA-256 ad7da5ee27ee4beb8a0570b72c915eb14b1c20092ac11405e4fed35f3e629a7b
    • stake.payments.deposit-route.ltc.litecoin· Confirmed within scope
      Field: payments.route_catalogue
      Recorded value: LTC on Litecoin
      Claim summary: LTC and Litecoin appear together in Stake's accepted-networks table for deposits. RTP Ledger does not transfer asset-level withdrawal minimums or fees onto this route.
      What the claim covers: domain=stake.com; account=public; asset=LTC; network=litecoin; direction=deposit
      Evidence basis: Published source
      Checked: 2026-08-02 · Next review: 2026-09-01
      Record owner: desk:casino-reviews
      Independent review pending
      Recorded change history · 2
      1. stake.payments.deposit-route.ltc.litecoin.created.2026-08-01
        Initial record · Changed: 2026-08-01
        Recorded value: LTC on Litecoin · Confirmed within scope
        Reason: Initial claim record created from the dated source review.
      2. stake.payments.deposit-route.ltc.litecoin.revised.source-snapshots.2026-08-02
        Revised record · Changed: 2026-08-02
        Previous value: LTC on Litecoin
        Recorded value: LTC on Litecoin · Confirmed within scope
        Reason: Linked unchanged source records to archived source copies captured on 2026-08-02.
      Stake accepted blockchain networks ↗ · Sources for the claim: Stake's accepted-networks table pairs Litecoin (LTC) with the native Litecoin network.
      Source access status: reachable · 2026-08-02 · Archived source copy: stake.accepted-networks.ad7da5ee27ee4beb8a0570b72c915eb14b1c20092ac11405e4fed35f3e629a7b · SHA-256 ad7da5ee27ee4beb8a0570b72c915eb14b1c20092ac11405e4fed35f3e629a7b
    • stake.payments.deposit-route.sol.solana· Confirmed within scope
      Field: payments.route_catalogue
      Recorded value: SOL on Solana
      Claim summary: SOL and Solana appear together in Stake's accepted-networks table for deposits. RTP Ledger does not transfer asset-level withdrawal minimums or fees onto this route.
      What the claim covers: domain=stake.com; account=public; asset=SOL; network=solana; direction=deposit
      Evidence basis: Published source
      Checked: 2026-08-02 · Next review: 2026-09-01
      Record owner: desk:casino-reviews
      Independent review pending
      Recorded change history · 2
      1. stake.payments.deposit-route.sol.solana.created.2026-08-01
        Initial record · Changed: 2026-08-01
        Recorded value: SOL on Solana · Confirmed within scope
        Reason: Initial claim record created from the dated source review.
      2. stake.payments.deposit-route.sol.solana.revised.source-snapshots.2026-08-02
        Revised record · Changed: 2026-08-02
        Previous value: SOL on Solana
        Recorded value: SOL on Solana · Confirmed within scope
        Reason: Linked unchanged source records to archived source copies captured on 2026-08-02.
      Stake accepted blockchain networks ↗ · Sources for the claim: Stake's accepted-networks table pairs Solana (SOL) with the native Solana network.
      Source access status: reachable · 2026-08-02 · Archived source copy: stake.accepted-networks.ad7da5ee27ee4beb8a0570b72c915eb14b1c20092ac11405e4fed35f3e629a7b · SHA-256 ad7da5ee27ee4beb8a0570b72c915eb14b1c20092ac11405e4fed35f3e629a7b
    • stake.payments.deposit-route.trx.trc20· Confirmed within scope
      Field: payments.route_catalogue
      Recorded value: TRX on TRC-20
      Claim summary: TRX and TRC-20 appear together in Stake's accepted-networks table for deposits. RTP Ledger does not transfer asset-level withdrawal minimums or fees onto this route.
      What the claim covers: domain=stake.com; account=public; asset=TRX; network=trc20; direction=deposit
      Evidence basis: Published source
      Checked: 2026-08-02 · Next review: 2026-09-01
      Record owner: desk:casino-reviews
      Independent review pending
      Recorded change history · 2
      1. stake.payments.deposit-route.trx.trc20.created.2026-08-01
        Initial record · Changed: 2026-08-01
        Recorded value: TRX on TRC-20 · Confirmed within scope
        Reason: Initial claim record created from the dated source review.
      2. stake.payments.deposit-route.trx.trc20.revised.source-snapshots.2026-08-02
        Revised record · Changed: 2026-08-02
        Previous value: TRX on TRC-20
        Recorded value: TRX on TRC-20 · Confirmed within scope
        Reason: Linked unchanged source records to archived source copies captured on 2026-08-02.
      Stake accepted blockchain networks ↗ · Sources for the claim: Stake's accepted-networks table pairs Tron (TRX) with TRC-20.
      Source access status: reachable · 2026-08-02 · Archived source copy: stake.accepted-networks.ad7da5ee27ee4beb8a0570b72c915eb14b1c20092ac11405e4fed35f3e629a7b · SHA-256 ad7da5ee27ee4beb8a0570b72c915eb14b1c20092ac11405e4fed35f3e629a7b
    • stake.payments.deposit-route.usdc.erc20· Confirmed within scope
      Field: payments.route_catalogue
      Recorded value: USDC on ERC-20
      Claim summary: USDC and ERC-20 appear together in Stake's accepted-networks table for deposits. RTP Ledger does not transfer asset-level withdrawal minimums or fees onto this route.
      What the claim covers: domain=stake.com; account=public; asset=USDC; network=erc20; direction=deposit
      Evidence basis: Published source
      Checked: 2026-08-02 · Next review: 2026-09-01
      Record owner: desk:casino-reviews
      Independent review pending
      Recorded change history · 2
      1. stake.payments.deposit-route.usdc.erc20.created.2026-08-01
        Initial record · Changed: 2026-08-01
        Recorded value: USDC on ERC-20 · Confirmed within scope
        Reason: Initial claim record created from the dated source review.
      2. stake.payments.deposit-route.usdc.erc20.revised.source-snapshots.2026-08-02
        Revised record · Changed: 2026-08-02
        Previous value: USDC on ERC-20
        Recorded value: USDC on ERC-20 · Confirmed within scope
        Reason: Linked unchanged source records to archived source copies captured on 2026-08-02.
      Stake accepted blockchain networks ↗ · Sources for the claim: Stake's accepted-networks table pairs USD Coin (USDC) with ERC-20.
      Source access status: reachable · 2026-08-02 · Archived source copy: stake.accepted-networks.ad7da5ee27ee4beb8a0570b72c915eb14b1c20092ac11405e4fed35f3e629a7b · SHA-256 ad7da5ee27ee4beb8a0570b72c915eb14b1c20092ac11405e4fed35f3e629a7b
    • stake.payments.deposit-route.usdc.bep20· Confirmed within scope
      Field: payments.route_catalogue
      Recorded value: USDC on BEP-20
      Claim summary: USDC and BEP-20 appear together in Stake's accepted-networks table for deposits. RTP Ledger does not transfer asset-level withdrawal minimums or fees onto this route.
      What the claim covers: domain=stake.com; account=public; asset=USDC; network=bep20; direction=deposit
      Evidence basis: Published source
      Checked: 2026-08-02 · Next review: 2026-09-01
      Record owner: desk:casino-reviews
      Independent review pending
      Recorded change history · 2
      1. stake.payments.deposit-route.usdc.bep20.created.2026-08-01
        Initial record · Changed: 2026-08-01
        Recorded value: USDC on BEP-20 · Confirmed within scope
        Reason: Initial claim record created from the dated source review.
      2. stake.payments.deposit-route.usdc.bep20.revised.source-snapshots.2026-08-02
        Revised record · Changed: 2026-08-02
        Previous value: USDC on BEP-20
        Recorded value: USDC on BEP-20 · Confirmed within scope
        Reason: Linked unchanged source records to archived source copies captured on 2026-08-02.
      Stake accepted blockchain networks ↗ · Sources for the claim: Stake's accepted-networks table pairs USD Coin (USDC) with BSC (BEP-20).
      Source access status: reachable · 2026-08-02 · Archived source copy: stake.accepted-networks.ad7da5ee27ee4beb8a0570b72c915eb14b1c20092ac11405e4fed35f3e629a7b · SHA-256 ad7da5ee27ee4beb8a0570b72c915eb14b1c20092ac11405e4fed35f3e629a7b
    • stake.payments.deposit-route.usdc.polygon· Confirmed within scope
      Field: payments.route_catalogue
      Recorded value: USDC on Polygon
      Claim summary: USDC and Polygon appear together in Stake's accepted-networks table for deposits. RTP Ledger does not transfer asset-level withdrawal minimums or fees onto this route.
      What the claim covers: domain=stake.com; account=public; asset=USDC; network=polygon; direction=deposit
      Evidence basis: Published source
      Checked: 2026-08-02 · Next review: 2026-09-01
      Record owner: desk:casino-reviews
      Independent review pending
      Recorded change history · 2
      1. stake.payments.deposit-route.usdc.polygon.created.2026-08-01
        Initial record · Changed: 2026-08-01
        Recorded value: USDC on Polygon · Confirmed within scope
        Reason: Initial claim record created from the dated source review.
      2. stake.payments.deposit-route.usdc.polygon.revised.source-snapshots.2026-08-02
        Revised record · Changed: 2026-08-02
        Previous value: USDC on Polygon
        Recorded value: USDC on Polygon · Confirmed within scope
        Reason: Linked unchanged source records to archived source copies captured on 2026-08-02.
      Stake accepted blockchain networks ↗ · Sources for the claim: Stake's accepted-networks table pairs USD Coin (USDC) with Polygon.
      Source access status: reachable · 2026-08-02 · Archived source copy: stake.accepted-networks.ad7da5ee27ee4beb8a0570b72c915eb14b1c20092ac11405e4fed35f3e629a7b · SHA-256 ad7da5ee27ee4beb8a0570b72c915eb14b1c20092ac11405e4fed35f3e629a7b
    • stake.payments.deposit-route.usdc.solana· Confirmed within scope
      Field: payments.route_catalogue
      Recorded value: USDC on Solana
      Claim summary: USDC and Solana appear together in Stake's accepted-networks table for deposits. RTP Ledger does not transfer asset-level withdrawal minimums or fees onto this route.
      What the claim covers: domain=stake.com; account=public; asset=USDC; network=solana; direction=deposit
      Evidence basis: Published source
      Checked: 2026-08-02 · Next review: 2026-09-01
      Record owner: desk:casino-reviews
      Independent review pending
      Recorded change history · 2
      1. stake.payments.deposit-route.usdc.solana.created.2026-08-01
        Initial record · Changed: 2026-08-01
        Recorded value: USDC on Solana · Confirmed within scope
        Reason: Initial claim record created from the dated source review.
      2. stake.payments.deposit-route.usdc.solana.revised.source-snapshots.2026-08-02
        Revised record · Changed: 2026-08-02
        Previous value: USDC on Solana
        Recorded value: USDC on Solana · Confirmed within scope
        Reason: Linked unchanged source records to archived source copies captured on 2026-08-02.
      Stake accepted blockchain networks ↗ · Sources for the claim: Stake's accepted-networks table pairs USD Coin (USDC) with Solana.
      Source access status: reachable · 2026-08-02 · Archived source copy: stake.accepted-networks.ad7da5ee27ee4beb8a0570b72c915eb14b1c20092ac11405e4fed35f3e629a7b · SHA-256 ad7da5ee27ee4beb8a0570b72c915eb14b1c20092ac11405e4fed35f3e629a7b
    • stake.payments.deposit-route.usdt.erc20· Confirmed within scope
      Field: payments.route_catalogue
      Recorded value: USDT on ERC-20
      Claim summary: USDT and ERC-20 appear together in Stake's accepted-networks table for deposits. RTP Ledger does not transfer asset-level withdrawal minimums or fees onto this route.
      What the claim covers: domain=stake.com; account=public; asset=USDT; network=erc20; direction=deposit
      Evidence basis: Published source
      Checked: 2026-08-02 · Next review: 2026-09-01
      Record owner: desk:casino-reviews
      Independent review pending
      Recorded change history · 2
      1. stake.payments.deposit-route.usdt.erc20.created.2026-08-01
        Initial record · Changed: 2026-08-01
        Recorded value: USDT on ERC-20 · Confirmed within scope
        Reason: Initial claim record created from the dated source review.
      2. stake.payments.deposit-route.usdt.erc20.revised.source-snapshots.2026-08-02
        Revised record · Changed: 2026-08-02
        Previous value: USDT on ERC-20
        Recorded value: USDT on ERC-20 · Confirmed within scope
        Reason: Linked unchanged source records to archived source copies captured on 2026-08-02.
      Stake accepted blockchain networks ↗ · Sources for the claim: Stake's accepted-networks table pairs Tether (USDT) with ERC-20.
      Source access status: reachable · 2026-08-02 · Archived source copy: stake.accepted-networks.ad7da5ee27ee4beb8a0570b72c915eb14b1c20092ac11405e4fed35f3e629a7b · SHA-256 ad7da5ee27ee4beb8a0570b72c915eb14b1c20092ac11405e4fed35f3e629a7b
    • stake.payments.deposit-route.usdt.bep20· Confirmed within scope
      Field: payments.route_catalogue
      Recorded value: USDT on BEP-20
      Claim summary: USDT and BEP-20 appear together in Stake's accepted-networks table for deposits. RTP Ledger does not transfer asset-level withdrawal minimums or fees onto this route.
      What the claim covers: domain=stake.com; account=public; asset=USDT; network=bep20; direction=deposit
      Evidence basis: Published source
      Checked: 2026-08-02 · Next review: 2026-09-01
      Record owner: desk:casino-reviews
      Independent review pending
      Recorded change history · 2
      1. stake.payments.deposit-route.usdt.bep20.created.2026-08-01
        Initial record · Changed: 2026-08-01
        Recorded value: USDT on BEP-20 · Confirmed within scope
        Reason: Initial claim record created from the dated source review.
      2. stake.payments.deposit-route.usdt.bep20.revised.source-snapshots.2026-08-02
        Revised record · Changed: 2026-08-02
        Previous value: USDT on BEP-20
        Recorded value: USDT on BEP-20 · Confirmed within scope
        Reason: Linked unchanged source records to archived source copies captured on 2026-08-02.
      Stake accepted blockchain networks ↗ · Sources for the claim: Stake's accepted-networks table pairs Tether (USDT) with BSC (BEP-20).
      Source access status: reachable · 2026-08-02 · Archived source copy: stake.accepted-networks.ad7da5ee27ee4beb8a0570b72c915eb14b1c20092ac11405e4fed35f3e629a7b · SHA-256 ad7da5ee27ee4beb8a0570b72c915eb14b1c20092ac11405e4fed35f3e629a7b
    • stake.payments.deposit-route.usdt.polygon· Confirmed within scope
      Field: payments.route_catalogue
      Recorded value: USDT on Polygon
      Claim summary: USDT and Polygon appear together in Stake's accepted-networks table for deposits. RTP Ledger does not transfer asset-level withdrawal minimums or fees onto this route.
      What the claim covers: domain=stake.com; account=public; asset=USDT; network=polygon; direction=deposit
      Evidence basis: Published source
      Checked: 2026-08-02 · Next review: 2026-09-01
      Record owner: desk:casino-reviews
      Independent review pending
      Recorded change history · 2
      1. stake.payments.deposit-route.usdt.polygon.created.2026-08-01
        Initial record · Changed: 2026-08-01
        Recorded value: USDT on Polygon · Confirmed within scope
        Reason: Initial claim record created from the dated source review.
      2. stake.payments.deposit-route.usdt.polygon.revised.source-snapshots.2026-08-02
        Revised record · Changed: 2026-08-02
        Previous value: USDT on Polygon
        Recorded value: USDT on Polygon · Confirmed within scope
        Reason: Linked unchanged source records to archived source copies captured on 2026-08-02.
      Stake accepted blockchain networks ↗ · Sources for the claim: Stake's accepted-networks table pairs Tether (USDT) with Polygon.
      Source access status: reachable · 2026-08-02 · Archived source copy: stake.accepted-networks.ad7da5ee27ee4beb8a0570b72c915eb14b1c20092ac11405e4fed35f3e629a7b · SHA-256 ad7da5ee27ee4beb8a0570b72c915eb14b1c20092ac11405e4fed35f3e629a7b
    • stake.payments.deposit-route.usdt.trc20· Confirmed within scope
      Field: payments.route_catalogue
      Recorded value: USDT on TRC-20
      Claim summary: USDT and TRC-20 appear together in Stake's accepted-networks table for deposits. RTP Ledger does not transfer asset-level withdrawal minimums or fees onto this route.
      What the claim covers: domain=stake.com; account=public; asset=USDT; network=trc20; direction=deposit
      Evidence basis: Published source
      Checked: 2026-08-02 · Next review: 2026-09-01
      Record owner: desk:casino-reviews
      Independent review pending
      Recorded change history · 2
      1. stake.payments.deposit-route.usdt.trc20.created.2026-08-01
        Initial record · Changed: 2026-08-01
        Recorded value: USDT on TRC-20 · Confirmed within scope
        Reason: Initial claim record created from the dated source review.
      2. stake.payments.deposit-route.usdt.trc20.revised.source-snapshots.2026-08-02
        Revised record · Changed: 2026-08-02
        Previous value: USDT on TRC-20
        Recorded value: USDT on TRC-20 · Confirmed within scope
        Reason: Linked unchanged source records to archived source copies captured on 2026-08-02.
      Stake accepted blockchain networks ↗ · Sources for the claim: Stake's accepted-networks table pairs Tether (USDT) with TRX/Tron (TRC-20).
      Source access status: reachable · 2026-08-02 · Archived source copy: stake.accepted-networks.ad7da5ee27ee4beb8a0570b72c915eb14b1c20092ac11405e4fed35f3e629a7b · SHA-256 ad7da5ee27ee4beb8a0570b72c915eb14b1c20092ac11405e4fed35f3e629a7b
    • stake.payments.deposit-route.usdt.solana· Confirmed within scope
      Field: payments.route_catalogue
      Recorded value: USDT on Solana
      Claim summary: USDT and Solana appear together in Stake's accepted-networks table for deposits. RTP Ledger does not transfer asset-level withdrawal minimums or fees onto this route.
      What the claim covers: domain=stake.com; account=public; asset=USDT; network=solana; direction=deposit
      Evidence basis: Published source
      Checked: 2026-08-02 · Next review: 2026-09-01
      Record owner: desk:casino-reviews
      Independent review pending
      Recorded change history · 2
      1. stake.payments.deposit-route.usdt.solana.created.2026-08-01
        Initial record · Changed: 2026-08-01
        Recorded value: USDT on Solana · Confirmed within scope
        Reason: Initial claim record created from the dated source review.
      2. stake.payments.deposit-route.usdt.solana.revised.source-snapshots.2026-08-02
        Revised record · Changed: 2026-08-02
        Previous value: USDT on Solana
        Recorded value: USDT on Solana · Confirmed within scope
        Reason: Linked unchanged source records to archived source copies captured on 2026-08-02.
      Stake accepted blockchain networks ↗ · Sources for the claim: Stake's accepted-networks table pairs Tether (USDT) with Solana.
      Source access status: reachable · 2026-08-02 · Archived source copy: stake.accepted-networks.ad7da5ee27ee4beb8a0570b72c915eb14b1c20092ac11405e4fed35f3e629a7b · SHA-256 ad7da5ee27ee4beb8a0570b72c915eb14b1c20092ac11405e4fed35f3e629a7b
    • stake.payments.deposit-route.xrp.xrp-ledger· Confirmed within scope
      Field: payments.route_catalogue
      Recorded value: XRP on XRP Ledger
      Claim summary: XRP and XRP Ledger appear together in Stake's accepted-networks table for deposits. RTP Ledger does not transfer asset-level withdrawal minimums or fees onto this route.
      What the claim covers: domain=stake.com; account=public; asset=XRP; network=xrp-ledger; direction=deposit
      Evidence basis: Published source
      Checked: 2026-08-02 · Next review: 2026-09-01
      Record owner: desk:casino-reviews
      Independent review pending
      Recorded change history · 2
      1. stake.payments.deposit-route.xrp.xrp-ledger.created.2026-08-01
        Initial record · Changed: 2026-08-01
        Recorded value: XRP on XRP Ledger · Confirmed within scope
        Reason: Initial claim record created from the dated source review.
      2. stake.payments.deposit-route.xrp.xrp-ledger.revised.source-snapshots.2026-08-02
        Revised record · Changed: 2026-08-02
        Previous value: XRP on XRP Ledger
        Recorded value: XRP on XRP Ledger · Confirmed within scope
        Reason: Linked unchanged source records to archived source copies captured on 2026-08-02.
      Stake accepted blockchain networks ↗ · Sources for the claim: Stake's accepted-networks table lists Ripple (XRP) with the network label Ripple.
      Source access status: reachable · 2026-08-02 · Archived source copy: stake.accepted-networks.ad7da5ee27ee4beb8a0570b72c915eb14b1c20092ac11405e4fed35f3e629a7b · SHA-256 ad7da5ee27ee4beb8a0570b72c915eb14b1c20092ac11405e4fed35f3e629a7b

  2. Deposit terms

    Partial evidence
    Published source

    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.

    Scope: Domain: stake.com; Account scope: public; Asset: supported crypto assets; Network: not established; Direction: deposit

    Checked 2026-08-02Stake crypto withdrawal limits ↗
    Claim records · 1
    • stake.deposit.route-terms-gap· Unknown
      Field: deposit.route_terms
      Recorded value: Exact deposit minimum, fee, confirmations and crediting stages are not established by the current public withdrawal table
      Claim summary: 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.
      What the claim covers: domain=stake.com; account=public; asset=supported crypto assets; network=not established; direction=deposit
      Evidence basis: Published source
      Checked: 2026-08-02 · Next review: 2026-09-01
      Record owner: desk:casino-reviews
      Independent review pending
      Recorded change history · 2
      1. stake.deposit.route-terms-gap.created.2026-08-01
        Initial record · Changed: 2026-08-01
        Recorded value: Exact deposit minimum, fee, confirmations and crediting stages are not established by the current public withdrawal table · Unknown
        Reason: Initial claim record created from the dated source review.
      2. stake.deposit.route-terms-gap.revised.source-snapshots.2026-08-02
        Revised record · Changed: 2026-08-02
        Previous value: Exact deposit minimum, fee, confirmations and crediting stages are not established by the current public withdrawal table
        Recorded value: Exact deposit minimum, fee, confirmations and crediting stages are not established by the current public withdrawal table · Unknown
        Reason: Linked unchanged source records to archived source copies captured on 2026-08-02.
      Stake crypto withdrawal limits ↗ · Sources for the claim: Published asset-level withdrawal minimum and fee table; the page does not bind each value to a network.
      Source access status: reachable · 2026-08-02 · Archived source copy: stake.withdrawal-table.a482b45ed4f174f789cc7ce38361a9493fb14a85f0357c20e165e079b9a7b243 · SHA-256 a482b45ed4f174f789cc7ce38361a9493fb14a85f0357c20e165e079b9a7b243

  3. Withdrawal terms

    Partial evidence
    Published source

    The public terms describe four material withdrawal conditions but do not provide an observed processing time. Coverage gaps: first-party withdrawal processing observation.

    Scope: Domain: stake.com; Account scope: public; Asset: crypto; Network: operator-supported; Direction: withdrawal

    Checked 2026-08-01Stake terms ↗
    Claim records · 1
    • stake.withdrawal.crypto-rules· Confirmed within scope
      Field: withdrawal.crypto.published_rules
      Recorded value: 100% deposit turnover; live minimum; discretionary fee; additional KYC possible
      Claim summary: The public terms describe four material withdrawal conditions but do not provide an observed processing time.
      What the claim covers: domain=stake.com; account=public; asset=crypto; network=operator-supported; direction=withdrawal
      Evidence basis: Published source
      Checked: 2026-08-01 · Next review: 2026-09-01
      Record owner: desk:casino-reviews
      Independent review pending
      Recorded change history · 1
      1. stake.withdrawal.crypto-rules.created.2026-08-01
        Initial record · Changed: 2026-08-01
        Recorded value: 100% deposit turnover; live minimum; discretionary fee; additional KYC possible · Confirmed within scope
        Reason: Initial claim record created from the dated source review.
      Stake terms ↗ · Sources for the claim: Operator, contract, account, withdrawal, KYC, support and jurisdiction clauses.
      Source access status: not independently recorded · Archived source copy pending

  4. KYC and source-of-funds process

    Partial evidence
    Published source

    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.

    Scope: Domain: stake.com; Account scope: public; Asset: crypto; Network: operator-supported; Direction: withdrawal

    Checked 2026-08-02Stake terms ↗Stake source-of-income guide ↗
    Claim records · 1
    • stake.kyc.withdrawal-sof· Confirmed within scope
      Field: kyc.withdrawal_and_source_of_funds
      Recorded value: Additional KYC may be requested; published source-of-income document classes exist
      Claim summary: Published records support possible withdrawal KYC and a detailed source-of-income document list, not the trigger timing for a specific account.
      What the claim covers: domain=stake.com; account=public; asset=crypto; network=operator-supported; direction=withdrawal
      Evidence basis: Published source
      Checked: 2026-08-02 · Next review: 2026-09-01
      Record owner: desk:casino-reviews
      Independent review pending
      Recorded change history · 2
      1. stake.kyc.withdrawal-sof.created.2026-08-01
        Initial record · Changed: 2026-08-01
        Recorded value: Additional KYC may be requested; published source-of-income document classes exist · Confirmed within scope
        Reason: Initial claim record created from the dated source review.
      2. stake.kyc.withdrawal-sof.revised.source-snapshots.2026-08-02
        Revised record · Changed: 2026-08-02
        Previous value: Additional KYC may be requested; published source-of-income document classes exist
        Recorded value: Additional KYC may be requested; published source-of-income document classes exist · Confirmed within scope
        Reason: Linked unchanged source records to archived source copies captured on 2026-08-02.
      Stake terms ↗ · Sources for the claim: Operator, contract, account, withdrawal, KYC, support and jurisdiction clauses.
      Source access status: not independently recorded · Archived source copy pending
      Stake source-of-income guide ↗ · Sources for the claim: Published classes and requirements for source-of-income documents.
      Source access status: reachable · 2026-08-02 · Archived source copy: stake.source-of-income.b13785845f46741196419805ee8e1caf4af9d4d32c63f07184756cd3e71e89a3 · SHA-256 b13785845f46741196419805ee8e1caf4af9d4d32c63f07184756cd3e71e89a3

  5. Bonus terms

    Partial evidence
    Published source

    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.

    Scope: Domain: stake.com; Account scope: public

    Checked 2026-08-02Stake welcome-offer guide ↗
    Claim records · 1
    • stake.bonus.welcome-rakeback· Confirmed within scope
      Field: bonus.economic_terms
      Recorded value: Valid affiliate code within 24 hours unlocks rakeback equal to 3.5% of house edge; no fixed deposit-match value is claimed
      Claim summary: 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.
      What the claim covers: domain=stake.com; account=public
      Evidence basis: Published source
      Checked: 2026-08-02 · Next review: 2026-09-01
      Record owner: desk:casino-reviews
      Independent review pending
      Recorded change history · 2
      1. stake.bonus.welcome-rakeback.created.2026-08-01
        Initial record · Changed: 2026-08-01
        Recorded value: Valid affiliate code within 24 hours unlocks rakeback equal to 3.5% of house edge; no fixed deposit-match value is claimed · Confirmed within scope
        Reason: Initial claim record created from the dated source review.
      2. stake.bonus.welcome-rakeback.revised.source-snapshots.2026-08-02
        Revised record · Changed: 2026-08-02
        Previous value: Valid affiliate code within 24 hours unlocks rakeback equal to 3.5% of house edge; no fixed deposit-match value is claimed
        Recorded value: Valid affiliate code within 24 hours unlocks rakeback equal to 3.5% of house edge; no fixed deposit-match value is claimed · Confirmed within scope
        Reason: Linked unchanged source records to archived source copies captured on 2026-08-02.
      Stake welcome-offer guide ↗ · Sources for the claim: Published rakeback mechanic, 3.5% of house edge and 24-hour code-entry window.
      Source access status: reachable · 2026-08-02 · Archived source copy: stake.welcome-offer.180e08998a657e39ab91bf0d92b75388c6b50cdbb6e1c091f8c4679b21ec0c78 · SHA-256 180e08998a657e39ab91bf0d92b75388c6b50cdbb6e1c091f8c4679b21ec0c78

Protection, ownership and recourse

4 / 20

  1. Responsible-gambling controls

    Documented
    Published source

    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.

    Scope: Domain: stake.com; Account scope: public

    Checked 2026-08-02Stake gambling limits ↗Stake self-exclusion ↗Stake break in play ↗
    Claim records · 2
    • stake.rg.loss-wager-limits· Confirmed within scope
      Field: responsible_gambling.loss_and_wager_limits
      Recorded value: Daily, weekly and monthly limits; 24-hour delay for increases
      Claim summary: The help centre publishes loss and wager limits plus a delay before an increase takes effect.
      What the claim covers: domain=stake.com; account=public
      Evidence basis: Published source
      Checked: 2026-08-02 · Next review: 2026-09-01
      Record owner: desk:casino-reviews
      Independent review pending
      Recorded change history · 2
      1. stake.rg.loss-wager-limits.created.2026-08-01
        Initial record · Changed: 2026-08-01
        Recorded value: Daily, weekly and monthly limits; 24-hour delay for increases · Confirmed within scope
        Reason: Initial claim record created from the dated source review.
      2. stake.rg.loss-wager-limits.revised.source-snapshots.2026-08-02
        Revised record · Changed: 2026-08-02
        Previous value: Daily, weekly and monthly limits; 24-hour delay for increases
        Recorded value: Daily, weekly and monthly limits; 24-hour delay for increases · Confirmed within scope
        Reason: Linked unchanged source records to archived source copies captured on 2026-08-02.
      Stake gambling limits ↗ · Sources for the claim: Loss and wager limits plus the cooling-off rule for increases.
      Source access status: reachable · 2026-08-02 · Archived source copy: stake.gambling-limits.c446175abff02aa0ee7e558b60e28a8da224cd53c419382ff4e6ebdc94ffc3ca · SHA-256 c446175abff02aa0ee7e558b60e28a8da224cd53c419382ff4e6ebdc94ffc3ca
    • stake.rg.self-exclusion-break· Confirmed within scope
      Field: responsible_gambling.exclusion_and_break
      Recorded value: Indefinite exclusion with six-month minimum review period; temporary breaks published
      Claim summary: The help centre publishes both indefinite self-exclusion and shorter break-in-play options.
      What the claim covers: domain=stake.com; account=public
      Evidence basis: Published source
      Checked: 2026-08-02 · Next review: 2026-09-01
      Record owner: desk:casino-reviews
      Independent review pending
      Recorded change history · 2
      1. stake.rg.self-exclusion-break.created.2026-08-01
        Initial record · Changed: 2026-08-01
        Recorded value: Indefinite exclusion with six-month minimum review period; temporary breaks published · Confirmed within scope
        Reason: Initial claim record created from the dated source review.
      2. stake.rg.self-exclusion-break.revised.source-snapshots.2026-08-02
        Revised record · Changed: 2026-08-02
        Previous value: Indefinite exclusion with six-month minimum review period; temporary breaks published
        Recorded value: Indefinite exclusion with six-month minimum review period; temporary breaks published · Confirmed within scope
        Reason: Linked unchanged source records to archived source copies captured on 2026-08-02.
      Stake self-exclusion ↗ · Sources for the claim: Indefinite self-exclusion access path and minimum period.
      Source access status: reachable · 2026-08-02 · Archived source copy: stake.self-exclusion.422d2d46ef8c4741ff1fed031a7e7e119ae3b473a7cb595bca9228eee81d1d9f · SHA-256 422d2d46ef8c4741ff1fed031a7e7e119ae3b473a7cb595bca9228eee81d1d9f
      Stake break in play ↗ · Sources for the claim: Published temporary break periods and reopening behaviour.
      Source access status: reachable · 2026-08-02 · Archived source copy: stake.break-in-play.0f4ef9efd6caee6911a67a0a7e65a043f087e096171edad5642486e38cacb80b · SHA-256 0f4ef9efd6caee6911a67a0a7e65a043f087e096171edad5642486e38cacb80b

  2. RTP Ledger cashout test

    Partial evidence
    RTP Ledger research status; no test evidence

    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.

    Scope: Domain: stake.com; Account scope: rtpledger_test_account; Asset: not tested; Network: not tested; Direction: withdrawal

    No dated source
    Claim records · 1
    • stake.cashout.test-status· Unknown
      Field: cashout.test_status
      Recorded value: No completed RTP Ledger cashout observation is registered
      Claim summary: RTP Ledger has not registered a completed Stake cashout observation. Published withdrawal rules are not a substitute for a first-party cashout test.
      What the claim covers: domain=stake.com; account=rtpledger_test_account; asset=not tested; network=not tested; direction=withdrawal
      Evidence basis: RTP Ledger research status; no test evidence
      Checked: 2026-08-01 · Next review: 2026-09-01
      Record owner: desk:casino-reviews
      Independent review pending
      Recorded change history · 1
      1. stake.cashout.test-status.created.2026-08-01
        Initial record · Changed: 2026-08-01
        Recorded value: No completed RTP Ledger cashout observation is registered · Unknown
        Reason: Initial claim record created from the dated source review.

  3. Complaint handling

    Not checked
    No evidence basis

    Complaint handling and resolution outcomes are not checked in a dated source record.

    Scope: No sourced claim is published for this area.

    No dated source

Game math, fairness and security

3 / 20

  1. Game catalogue and RTP evidence

    Documented
    Published source

    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.

    Scope: Domain: fair.stake-engine.com; Account scope: public

    Checked 2026-08-01Stake Engine catalogue ↗
    Claim records · 1
    • stake.game-rtp.engine-catalogue· Confirmed within scope
      Field: game_rtp.stake_engine_catalogue_fields
      Recorded value: Public catalogue lists game, RTP and event-count records for each mode
      Claim summary: 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.
      What the claim covers: domain=fair.stake-engine.com; account=public
      Evidence basis: Published source
      Checked: 2026-08-01 · Next review: 2026-09-01
      Record owner: desk:casino-reviews
      Independent review pending
      Recorded change history · 1
      1. stake.game-rtp.engine-catalogue.created.2026-08-01
        Initial record · Changed: 2026-08-01
        Recorded value: Public catalogue lists game, RTP and event-count records for each mode · Confirmed within scope
        Reason: Initial claim record created from the dated source review.
      Stake Engine catalogue ↗ · Sources for the claim: Public game, mode, RTP and event-count catalogue fields checked by RTP Ledger.
      Source access status: not independently recorded · Archived source copy pending

  2. Fairness and verification

    Partial evidence
    Published source

    Stake publishes the algorithm and inputs for supported verifiable bets. Coverage gaps: reproduced account-bet verification.

    Scope: Domain: stake.com; Account scope: public

    Checked 2026-08-01Stake provably-fair implementation ↗
    Claim records · 1
    • stake.fairness.hmac-implementation· Confirmed within scope
      Field: fairness.published_algorithm
      Recorded value: HMAC-SHA256 with server seed, client seed, nonce and cursor
      Claim summary: Stake publishes the algorithm and inputs for supported verifiable bets.
      What the claim covers: domain=stake.com; account=public
      Evidence basis: Published source
      Checked: 2026-08-01 · Next review: 2026-09-01
      Record owner: desk:casino-reviews
      Independent review pending
      Recorded change history · 1
      1. stake.fairness.hmac-implementation.created.2026-08-01
        Initial record · Changed: 2026-08-01
        Recorded value: HMAC-SHA256 with server seed, client seed, nonce and cursor · Confirmed within scope
        Reason: Initial claim record created from the dated source review.
      Stake provably-fair implementation ↗ · Sources for the claim: Algorithm, inputs, seed commitment and nonce/cursor mechanics.
      Source access status: not independently recorded · Archived source copy pending

  3. Account and withdrawal security

    Partial evidence
    Published source

    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.

    Scope: Domain: stake.com; Account scope: public; Direction: both, withdrawal

    Checked 2026-08-01Stake 2FA guide ↗Stake withdrawal OAuth guide ↗
    Claim records · 2
    • stake.security.two-factor· Confirmed within scope
      Field: security.two_factor_authentication
      Recorded value: Optional 2FA covers login, withdrawal and fund-sending actions
      Claim summary: The help centre documents 2FA coverage and activation.
      What the claim covers: domain=stake.com; account=public; direction=both
      Evidence basis: Published source
      Checked: 2026-08-01 · Next review: 2026-09-01
      Record owner: desk:casino-reviews
      Independent review pending
      Recorded change history · 1
      1. stake.security.two-factor.created.2026-08-01
        Initial record · Changed: 2026-08-01
        Recorded value: Optional 2FA covers login, withdrawal and fund-sending actions · Confirmed within scope
        Reason: Initial claim record created from the dated source review.
      Stake 2FA guide ↗ · Sources for the claim: 2FA coverage and activation flow.
      Source access status: not independently recorded · Archived source copy pending
    • stake.security.withdrawal-oauth· Confirmed within scope
      Field: security.withdrawal_oauth_reverification
      Recorded value: Social-login accounts may require OAuth re-verification for withdrawal
      Claim summary: The help centre documents an extra withdrawal authentication step for supported social logins.
      What the claim covers: domain=stake.com; account=public; direction=withdrawal
      Evidence basis: Published source
      Checked: 2026-08-01 · Next review: 2026-09-01
      Record owner: desk:casino-reviews
      Independent review pending
      Recorded change history · 1
      1. stake.security.withdrawal-oauth.created.2026-08-01
        Initial record · Changed: 2026-08-01
        Recorded value: Social-login accounts may require OAuth re-verification for withdrawal · Confirmed within scope
        Reason: Initial claim record created from the dated source review.
      Stake withdrawal OAuth guide ↗ · Sources for the claim: Re-verification step for supported social-login withdrawals.
      Source access status: not independently recorded · Archived source copy pending

Service, product and policy

4 / 20

  1. Support and escalation

    Partial evidence
    Published source

    The terms publish the channels and stated availability, not observed response quality. Coverage gaps: timestamped support-response test.

    Scope: Domain: stake.com; Account scope: public

    Checked 2026-08-01Stake terms ↗
    Claim records · 1
    • stake.support.published-channels· Confirmed within scope
      Field: support.published_channels
      Recorded value: Email and live chat, described as 24/7
      Claim summary: The terms publish the channels and stated availability, not observed response quality.
      What the claim covers: domain=stake.com; account=public
      Evidence basis: Published source
      Checked: 2026-08-01 · Next review: 2026-09-01
      Record owner: desk:casino-reviews
      Independent review pending
      Recorded change history · 1
      1. stake.support.published-channels.created.2026-08-01
        Initial record · Changed: 2026-08-01
        Recorded value: Email and live chat, described as 24/7 · Confirmed within scope
        Reason: Initial claim record created from the dated source review.
      Stake terms ↗ · Sources for the claim: Operator, contract, account, withdrawal, KYC, support and jurisdiction clauses.
      Source access status: not independently recorded · Archived source copy pending

  2. Product and user experience

    Not checked
    No evidence basis

    Product catalogue, devices and observed usability defects are not checked.

    Scope: No sourced claim is published for this area.

    No dated source

  3. VIP and loyalty mechanics

    Partial evidence
    Published source

    The help centre names recurring promotion and loyalty mechanisms without proving account-specific value. Coverage gaps: effective VIP value and expiry.

    Scope: Domain: stake.com; Account scope: public

    Checked 2026-08-01Stake promotions guide ↗
    Claim records · 1
    • stake.vip.published-mechanisms· Confirmed within scope
      Field: vip.published_mechanisms
      Recorded value: Rakeback, Weekly boost, Monthly bonus, Level-up bonus
      Claim summary: The help centre names recurring promotion and loyalty mechanisms without proving account-specific value.
      What the claim covers: domain=stake.com; account=public
      Evidence basis: Published source
      Checked: 2026-08-01 · Next review: 2026-09-01
      Record owner: desk:casino-reviews
      Independent review pending
      Recorded change history · 1
      1. stake.vip.published-mechanisms.created.2026-08-01
        Initial record · Changed: 2026-08-01
        Recorded value: Rakeback, Weekly boost, Monthly bonus, Level-up bonus · Confirmed within scope
        Reason: Initial claim record created from the dated source review.
      Stake promotions guide ↗ · Sources for the claim: Published promotion and loyalty mechanism names.
      Source access status: not independently recorded · Archived source copy pending

  4. Privacy and data rights

    Partial evidence
    Published source

    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.

    Scope: Domain: stake.com; Account scope: public

    Checked 2026-08-01Stake privacy policy ↗Stake account deletion guide ↗
    Claim records · 2
    • stake.privacy.policy-coverage· Confirmed within scope
      Field: privacy.policy_coverage
      Recorded value: Controller, data categories, purposes, sharing, transfers and purpose-based retention
      Claim summary: The policy covers the main data lifecycle but does not publish a fixed duration for every category.
      What the claim covers: domain=stake.com; account=public
      Evidence basis: Published source
      Checked: 2026-08-01 · Next review: 2026-09-01
      Record owner: desk:casino-reviews
      Independent review pending
      Recorded change history · 1
      1. stake.privacy.policy-coverage.created.2026-08-01
        Initial record · Changed: 2026-08-01
        Recorded value: Controller, data categories, purposes, sharing, transfers and purpose-based retention · Confirmed within scope
        Reason: Initial claim record created from the dated source review.
      Stake privacy policy ↗ · Sources for the claim: Controller, data categories, processing, retention, transfers and deletion rights.
      Source access status: not independently recorded · Archived source copy pending
    • stake.privacy.deletion-limits· Confirmed within scope
      Field: privacy.deletion_and_closure
      Recorded value: Deletion may be limited by legal retention duties; account closure remains available
      Claim summary: The help centre distinguishes account closure from complete deletion.
      What the claim covers: domain=stake.com; account=public
      Evidence basis: Published source
      Checked: 2026-08-01 · Next review: 2026-09-01
      Record owner: desk:casino-reviews
      Independent review pending
      Recorded change history · 1
      1. stake.privacy.deletion-limits.created.2026-08-01
        Initial record · Changed: 2026-08-01
        Recorded value: Deletion may be limited by legal retention duties; account closure remains available · Confirmed within scope
        Reason: Initial claim record created from the dated source review.
      Stake account deletion guide ↗ · Sources for the claim: Difference between closure and complete deletion under retention duties.
      Source access status: not independently recorded · Archived source copy pending
Evidence synthesis

What the current record supports

The research record contains 6 documented areas, 12 partial areas and 2 unchecked areas. The counts describe research coverage only.

Dated source records

  • Legal operator identity
  • Licence claim
  • Country restrictions
  • Published payment records
  • Responsible-gambling controls
  • Game and RTP evidence

Partial records

  • Account journey and closure
  • Deposit terms
  • Withdrawal terms
  • Bonus terms
  • KYC and source-of-funds process
  • RTP Ledger cashout test
  • Ownership and related brands
  • Fairness verification
  • Account security
  • Support and escalation
  • VIP and loyalty mechanics
  • Privacy and data rights

Still not checked

  • Complaint handling
  • Product and user experience
Before you deposit

What to check before visiting the operator

The record still needs more evidence or editorial review. The highest-priority open area is Withdrawal terms. The RTP Ledger cashout-test status is RTP Ledger cashout test: Partial records. Published terms do not confirm a completed payout.

Evidence for this decision · critical
Withdrawal terms · Open the supporting record

The public terms describe four material withdrawal conditions but do not provide an observed processing time. Coverage gaps: first-party withdrawal processing observation.

Scope: Domain: stake.com; Account scope: public; Asset: crypto; Network: operator-supported; Direction: withdrawal · Checked 2026-08-01 · 1 linked source

Cashout-test record
stake.cashout.test-status · Open the supporting recordunknown

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.

Use this page as a research checklist. The current record cannot support a decision based on RTP Ledger-tested deposits, withdrawals or support. Compare other casino research records and payment routes for the exact asset and network before making a decision.

sourced research record · 46 source-linked claims · 16/20 areas with a supported claim

Open the Money Route Finder after reviewing these evidence gaps →

Questions and answers

What has RTP Ledger checked about Stake?

The research record covers 20 areas: 6 documented, 12 partial and 2 unchecked. Each area shows its status, scope, date and linked source. The counts describe research coverage.

Who operates Stake, and can I open an account?

Legal identity: documented. Licence: documented. Country restrictions: documented. Registration and closure: partially documented. A licence name does not confirm domain or country coverage.

What is known about Stake deposits, withdrawals, KYC and bonuses?

Payment catalogue: documented. Deposit terms: partially documented. Withdrawal terms: partially documented. KYC and source of funds: partially documented. Bonus terms: partially documented. A listed asset alone does not prove network, direction, limit or availability for your account.

How does Stake protect players, and what happens when something goes wrong?

Responsible-gambling controls: documented. RTP Ledger cashout test: partially documented. Complaint handling: not checked. Ownership links: partially documented. A pending test has an unknown status.

Has RTP Ledger checked Stake games, RTP and fairness?

Game and RTP evidence: documented. Reproducible fairness: partially documented. Account and withdrawal security: partially documented. Provider or catalogue data alone does not prove the configuration available in your account.

What is known about Stake support, product, VIP and privacy?

Support and escalation: partially documented. Product and user experience: not checked. VIP and loyalty: partially documented. Privacy and data rights: partially documented. Published availability and observed performance remain separate.

This review uses a shared method with 20 evidence areas. Each status describes research coverage within a stated scope. Affiliate status cannot change the evidence or its status. Read the complete methodology.

See how RTP Ledger selects sourcesReport a data issue

This page may earn a commission from a marked operator link. Evidence order and research states are independent of that relationship.

18+ · Terms apply · Play responsibly — BeGambleAware.org