Cloudbet vs Stake: the documented differences

The terms preamble names Halcyon Super Holdings B.V. as the operator of cloudbet.com. The preamble gives company number 148526 and an address at Boulevard 03. The Curaçao Gaming Authority certificate binds the same company, company number and domain. The privacy policy gives a different postal address for the same company: Boulevard 50. RTP Ledger does not resolve this address discrepancy.

Checked 2026-09-27

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

Checked 2026-08-02

The terms cite licence OGL/2024/328/0599. The Curaçao Gaming Authority’s own certificate lookup confirms the same licence number. The certificate lookup shows a grant date of 23/05/2025 and a current status of Active. The CGA’s own bulk licence registry PDF is dated 2026-09-10. The registry PDF lists the same licence number and company. The registry PDF gives a different issued date, 23 November 2025, and a different expiry date, 23 May 2026. The registry PDF gives a different status: "Assessment in progress". RTP Ledger does not resolve this discrepancy between the two CGA-published sources.

Checked 2026-09-27

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

Clause 7.1.3 bars a user physically located in 19 named countries or territories from betting or withdrawing funds. The list includes Australia, Austria, Belgium, China (Macau and Hong Kong SAR), Curaçao, Cuba, France, Germany, Iran, Lithuania and Malta. It also includes Myanmar, the Netherlands, North Korea, Singapore, Syria, Spain, the United States of America and its territories, and the United Kingdom. Clause 7.1.3 also bars three named regions in Ukraine: Crimea, Donetsk and Luhansk.

Checked 2026-09-27

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

Registration, verification stages, account currency and closure journey are not checked.

No dated source

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

Checked 2026-08-01

The crypto transaction fees page lists 30 currencies. Each currency shows one or more accepted networks, for example USDT on Ethereum, BNB Smart Chain, Avalanche C-Chain, Solana, Polygon, TRON and The Open Network. The page states that Cloudbet charges no deposit fee. It attributes withdrawal fees to the blockchain network and says these fees can change without notice. Withdrawal minimums are listed separately in the table; the text does not attribute those minimums to the network.

Checked 2026-09-27

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

The crypto transaction fees page states a deposit fee of zero for every listed asset. It does not state a deposit minimum, a confirmation-count requirement or a crediting stage for any asset. RTP Ledger found no other page that states the deposit minimum, confirmations or crediting stage. Coverage gaps: deposit.route_terms.

No dated 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.

Checked 2026-08-02

The crypto transaction fees page states that Cloudbet charges no deposit fee. The page states that the blockchain network sets a flat withdrawal fee. The page states that this fee can change without notice. Clause 7.1.10.1 reserves the right to add a handling charge of up to 5% on deposits and withdrawals. Clause 7.5.8 gives a 24-hour window for a refund request. The window extends to 30 calendar days if the user claims that another person accessed the account. RTP Ledger has not observed a withdrawal on cloudbet.com, so processing time and effective fees are not established. Coverage gaps: first-party withdrawal processing observation.

Checked 2026-09-27

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

The promotion page checked on 26 September 2026 describes a Cash Vault separately from the $2,500 reload and rakeback amount. Clause 8.4 of the terms retains a $2,500 package cap. The previous total-cap and no-wagering summary is withheld pending reconciliation. The separate stored claim that all slots contribute 100% is also withdrawn: clause 8.5 now defines contribution by RTP. Earlier evidence remains in this claim’s history; this check was limited to the changed bonus sources. Section 8.4 states account eligibility, first-deposit activation, a 30-day period and a $2,500 package cap. The promotion page describes the Cash Vault separately from reloads and casino rakeback. RTP Ledger has not established how the stated cap and expiry apply to the whole current offer, so the earlier combined eligibility-and-expiry claim is withheld. This is a public-source check, not an account test or partner confirmation. Coverage gaps: bonus.economic_terms, bonus.account_eligibility_and_expiry.

Checked 2026-09-26

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

Clause 18.1.5 requires identity verification once cumulative deposits reach or exceed USD 2,200. Clause 18.1.3 names Sumsub as the contracted provider for automated KYC verification. Clause 7.5.7 lets Cloudbet ask for identification, proof of address, a card check and a photo before paying a withdrawal. RTP Ledger has not run a test account on cloudbet.com, so the stage at which verification is requested in practice is not established. Coverage gaps: observed KYC trigger and stage.

Checked 2026-09-27

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

The responsible-gambling page publishes a deposit limit with daily, weekly (7-day) or monthly (30-day) duration options. A stricter limit takes effect immediately. A less strict limit, or a cancelled limit, takes effect after a 24-hour wait. RTP Ledger found no separate wager limit or net-loss limit tool on the page. The responsible-gambling page offers cooling-off for 24 hours, 7 days, 1 month or 3 months. Betting is disabled during cooling-off. The page offers self-exclusion for 1 year, 3 years, 5 years or a lifetime. The page describes a lifetime exclusion as irreversible. The page names four help organisations: Gamblers Anonymous, GambleAware, Gambling Therapy and Gamtalk.

Checked 2026-09-27

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

RTP Ledger has not withdrawn funds from a cloudbet.com test account, so cashout speed and fees are not observed. Coverage gaps: cashout.first_party_observation.

No dated source

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

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

No dated source

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

No dated source

Parent, sister-brand and material operating relationships are not checked.

No dated source

The terms call both payment-processing companies wholly owned subsidiaries. Coverage gaps: parent/legal-group relationship, related-brand relationship.

Checked 2026-08-01

The fairness and RNG testing page states that RNGs are certified and tested externally before going live. It states that the theoretical RTP for a game appears in that game’s own information or help section. It states that analysis comparing the actual RTP to the theoretical RTP is carried out quarterly. This custom field name does not match the schema’s Stake Engine catalogue field. Cloudbet publishes a certification and review statement instead of a per-game RTP catalogue. Coverage gaps: game_rtp.stake_engine_catalogue_fields.

Checked 2026-09-12

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

The provably fair page states that Cloudbet Originals combine a server seed, a client seed and a nonce. It names SHA3-256 as the algorithm that creates the Commitment and the Round Signature. It names SHAKE256 as the algorithm that turns the Round Signature into the outcome stream. The page states a player can reproduce the Commitment and verify a round once the seeds are revealed. Coverage gaps: reproduced account-bet verification.

Checked 2026-09-12

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

Checked 2026-08-01

Two-factor authentication (2FA), recovery and withdrawal-protection controls are not checked.

No dated 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.

Checked 2026-08-01

The homepage footer lists a Help Center, labelled "Find answers easily", and live chat, labelled "Get Support 24/7". Clause 7.1.10.2 of the terms gives support@cloudbet.com as the contact address for reactivating a suspended account. RTP Ledger has not timed a support request on cloudbet.com, so response times are not established. Coverage gaps: timestamped support-response test.

Checked 2026-09-12

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

Checked 2026-08-01

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

No dated source

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

No dated source

VIP earning, tiers, expiry and withdrawal interactions are not checked.

No dated source

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

Controller, collection, retention, transfers and deletion paths are not checked.

No dated 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.

Checked 2026-08-01