Crypto-Compliant.
Not a licence. Not a jurisdiction claim. A proof standard.
Crypto-Compliant is a cCasino evidence-first verification label for gambling products that use digital assets or crypto-adjacent payment rails. We do not claim legality, licensing, or jurisdictional eligibility without primary sources. If evidence is missing, the field stays Not verified.
🛡️ Evidence-first baseline controls
- AML/CTF risk controls for digital value transfers
- SoF / SoW gating where required by the operator’s risk model
- Documented custody/settlement and payout pathways
- Public-facing transparency for payments and key terms
⛔ Not a “licensed crypto casino” list
- No licensing claims without regulator registry evidence
- No “provably fair” claims without testable documentation + audit artifact (if claimed)
- No “reserves verified” claims without a signed, time-stamped proof and methodology
- No jurisdictional “allowed in X” claims without a primary legal/regulatory source
Fail-Closed rule: If a field cannot be proven from a primary source or an auditable artifact, it remains “Not verified”. This includes licensing, jurisdiction, ownership, custody, solvency, and game integrity claims.
Crypto-Compliant Controls
| Control | Fail-Closed requirement | Minimum evidence pack | Pass criteria | Status |
|---|---|---|---|---|
| 1) Licensing / jurisdiction | No legality or “licensed” claims without a regulator registry hit or primary legal source. | Registry URL + screenshot/PDF snapshot + as-of date. | Registry hit exists and matches entity ↔ brand relationship. | ⚪ Framework |
| 2) AML/CTF controls | Documented AML/CTF policy covering digital value transfers and trigger-based reviews. | Policy doc + version + owner + effective date. | Policy is current and scope covers rails used. | ⚪ Framework |
| 3) SoF / SoW gating | SoF/SoW procedures where risk requires it. | Procedure + trigger rules + escalation path. | Procedure is auditable and consistent with AML approach. | ⚪ Framework |
| 4) Payments transparency | Clear disclosure of supported assets/rails, fees, and processing windows (as-of dated). | Payments/T&Cs snapshot + URL + timestamp. | Disclosures are consistent and user-facing. | ⚪ Framework |
| 5) Custody & settlement model | Explain who holds funds, custody structure, and settlement timing. | ToS clauses + corporate disclosure + processor disclosure. | Custody chain is explicit and not contradictory. | ⚪ Framework |
| 6) Game integrity | No “provably fair” claims unless the method is documented and testable. | Published method + verification steps + audit artifact (if claimed). | Method is verifiable and matches production behavior. | ⚪ Framework |
| 7) Reserves / solvency | No “reserves verified” claims without signed, time-stamped proof and methodology. | Signed report + scope + methodology + date. | Proof is attributable, time-bound, and method is explicit. | ⚪ Framework |
| 8) Consumer protection | Dispute route, limits/self-exclusion disclosures, and responsible gambling controls (as-of dated). | RG page + policy snapshot + contact/dispute mechanism. | Controls exist and are publicly disclosed. | ⚪ Framework |
Operator list policy (global): This page does not publish a global “crypto casino list” as verified/compliant because there is no single global regulator register for “crypto”. Operators are listed as Not verified unless a jurisdiction-specific registry hit and a full evidence pack exist.
Candidate Operators
| Operator / Site | Claimed model | Fail-closed gaps | What cCasino needs to verify | Status |
|---|---|---|---|---|
| StakeCandidate only — no certification label applied. | Digital-asset payments (unverified on this page) | Missing regulator registry evidence for a specific jurisdiction + missing auditable evidence pack fields (AML/SoF/custody/payments disclosures). | Add jurisdiction page(s) + registry hits + evidence pack (T&Cs, payments, AML disclosures, dispute/RG, integrity methodology if claimed). | ⚪ Not verified |
Rule: A candidate becomes “Crypto-Compliant” only after a complete evidence pack is stored and (where applicable) a jurisdiction registry hit exists.
Evidence Pack Template
| Field | Value | Evidence source | As-of date | Fail-closed rule |
|---|---|---|---|---|
| Operator legal entity | Not verified | Registry/filing link | YYYY-MM-DD | Blank if no primary source |
| Jurisdiction | Not verified | Law/regulator source | YYYY-MM-DD | No inference |
| Licence | Not verified | Regulator register URL | YYYY-MM-DD | Must be registry-hit |
| AML policy | Not verified | Policy doc link/version | YYYY-MM-DD | No doc = fail |
| SoF / SoW | Not verified | Procedure + triggers | YYYY-MM-DD | No procedure = not compliant |
| Payments disclosure | Not verified | Payments page snapshot | YYYY-MM-DD | Must be consistent |
| Custody & settlement | Not verified | ToS clauses + disclosure | YYYY-MM-DD | Unknown custody = not verified |
| Game integrity | Not verified | Method + audit artifact | YYYY-MM-DD | Claims require proof |
| Consumer protection | Not verified | RG page + dispute route | YYYY-MM-DD | No artifacts = not verified |
Implementation note: Store evidence_source URLs and as-of dates per field. Do not infer relationships between brands, entities, or jurisdictions without a primary source.