Requirements Hub
This hub groups requirements by control domain. Each domain includes a checklist-style view of minimum expectations and the typical artefacts used to evidence controls — mapped to role-based scope (Operator, Supplier, Affiliate).
How to use this page
Open a domain → read minimum expectations → align artefacts → map to your scope → build your evidence pack.
Evidence pack concept
Each requirement set includes policies + procedures + logs + monitoring rules + reporting outputs.
Next step
If you’re preparing submission, move to the application process and Registered Agent pathway.
Requirement domains
Pick a domain. Each page has checklists + artefact mapping.
AML/CFT
KYC, risk scoring, monitoring, SAR-style reporting readiness.
Responsible gaming
Player protection, limits, self-exclusion, intervention workflows.
Technical & security
Access control, logging, SDLC, incident response, uptime controls.
Governance & people
Accountability, competence, training, third-party management.
Fairness & integrity
Game integrity, testing evidence, change control, audit trails.
Reporting & recordkeeping
Retention schedules, incident logs, periodic returns, audit readiness.
Complaints & disclosures
Transparent communications, dispute routing, response SLAs.
Third-party & outsourcing
Vendor due diligence, contracts, monitoring, exit planning.
Evidence pack basics
Most submissions boil down to a repeatable artefact stack. The pages in this hub map expectations to these artefacts.
Operator vs Supplier vs Affiliate
Different roles mean different controls. Operator pages emphasise onboarding, funds flow and player protection. Supplier pages emphasise security, uptime, logging and integrity. Affiliate pages emphasise disclosures and record retention.
Recommended start points
If you’re building an evidence pack from scratch.
Note: Requirements are presented as operational expectations and evidence patterns for clarity.