iGaming Regulatory Platform Requirements

A regulation becomes an implementation problem: a wallet threshold, registry connection, player-state rule, intervention workflow, audit record or deployment confirmation. This ledger maps the rule to that operational capability.

Last updated August 20, 2026

What this ledger measures

Each record separates the operator duty, the platform capability needed to implement it and the workflows it changes. It does not infer that a provider is compliant because a similar feature exists elsewhere, and it does not infer a supplier permission from technical readiness. The current dataset covers 11 selected implementation-critical requirements across 5 markets. It prioritizes platform controls with a concrete effective date or current operating consequence; it is not a complete reproduction of licensing, tax, corporate, advertising or game-content law.

Great Britain

Gambling Commission

Remote operators must identify gambling-harm risk, take timely proportionate action and evaluate whether the intervention reduced the risk.

In force · Oct 31, 2023

Status assessed Aug 13, 2026

Required platform capability

Continuous player-risk monitoring, explainable risk indicators, intervention workflow, decision records and outcome evaluation.

Affected workflows

player monitoringresponsible-gambling case managementCRM suppressionaudit trail

Boundary: Remote B2C customer-interaction controls; a supplier feature does not transfer the operator's accountability.

Risk indicators must be assessed in the context of the individual player and connected to a timely intervention process.

Gambling Commission

A financial vulnerability check is required when deposits minus withdrawals exceed GBP 150 in a rolling 30-day period, unless a qualifying recent check already applies.

In force · Feb 28, 2025

Status assessed Aug 13, 2026

Required platform capability

Rolling net-deposit thresholding, customer-specific public-record check integration, risk decisioning, proportionate action and rationale retention.

Affected workflows

wallet ledgerfinancial-risk checksplayer restrictiondecision records

Boundary: Applies to the relevant remote operator licenses; it is not a generic supplier certification.

The check and the resulting action form part of the operator's wider customer-risk assessment.

Brazil

Secretariat of Prizes and Betting

The player registration flow must capture prudential limits for financial loss and elapsed gambling time, and increases cannot take effect immediately.

In force · Feb 8, 2026

Status assessed Aug 13, 2026

Required platform capability

Mandatory limit capture at registration, daily/weekly/monthly enforcement, cooling-off logic, consent versioning and immutable change history.

Affected workflows

registrationwallet limitssession controlterms acceptance

Boundary: Authorized fixed-odds betting operators and their deployed player-account systems.

Limits are part of the required account state rather than an optional responsible-gambling widget.

Secretariat of Prizes and Betting

Authorized operators must interoperate with the centralized self-exclusion service, prevent excluded participation and suppress directed advertising.

In force · Dec 10, 2025

Status assessed Aug 13, 2026

Required platform capability

Central exclusion synchronization, account blocking, marketing suppression, balance-return workflow and regulator-facing status records.

Affected workflows

registrationlogin and wageringCRM suppressionaccount closurebalance return

Boundary: Centralized exclusion across SPA-authorized betting platforms; operator-specific exclusion remains a separate control.

The central status must reach every customer-facing brand and the systems that decide access and marketing eligibility.

Ontario

Alcohol and Gaming Commission of Ontario

Operators must monitor player behavior to identify risk and intervene in a timely manner that is proportionate to the player's risk profile.

In force

Status assessed Aug 13, 2026

Required platform capability

Manual and automated risk monitoring, multi-source player profile, intervention orchestration, employee workflow and effectiveness review.

Affected workflows

player analyticsresponsible-gambling case managementcustomer supportintervention review

Boundary: Ontario operator control environment; third-party platform services do not remove operator responsibility.

Monitoring must remain effective when parts of the gambling offering are delivered by third parties.

Alcohol and Gaming Commission of Ontario / iGaming Ontario

Regulated sites must enforce the centralized BetGuard exclusion state alongside their own operator-level self-exclusion controls.

In force · May 14, 2026

Status assessed Aug 13, 2026

Required platform capability

Central registry integration, cross-brand account blocking, marketing suppression, account-level exclusion and auditable status synchronization.

Affected workflows

registrationlogin and wageringCRM suppressionoperator self-exclusion

Boundary: Ontario regulated internet-gaming sites; land-based and other-jurisdiction exclusion programs remain separate unless explicitly connected.

A generic self-exclusion feature is insufficient without the current centralized and operator-specific workflows.

Alberta

Alberta Gaming, Liquor and Cannabis

Players must receive system-enforced time, deposit and loss limits with daily, weekly and monthly periods and controlled increase timing.

In force · Jul 13, 2026

Status assessed Aug 13, 2026

Required platform capability

Limit configuration and enforcement across wallet and session services, lowest-limit precedence, cooling-off logic and complete change records.

Affected workflows

registrationwallet limitssession limitslimit changes

Boundary: Registered Alberta operator sites and the exact platform deployment used by them.

The limits must be enforced by the operating system rather than presented as informational preferences.

Alberta Gaming, Liquor and Cannabis

Operator systems must connect to Alberta's centralized prohibited-person and self-exclusion services and prevent uncleared registration, login and wagering.

In force · Jul 13, 2026

Status assessed Aug 13, 2026

Required platform capability

Secure registry API connection, eligibility decisioning, repeated re-verification, account blocking, marketing suppression and discrepancy reporting.

Affected workflows

registrationlogin and wageringeligibility recheckCRM suppressionregulatory reporting

Boundary: Registered Alberta operator sites; a supplier registration alone does not establish implementation.

The centralized state must control access throughout the player lifecycle and not only at initial registration.

Alberta Gaming, Liquor and Cannabis

Operators and critical-system suppliers must provide annual technology compliance confirmation for their own deployed scope.

In force · Jul 13, 2026

Status assessed Aug 13, 2026

Required platform capability

Versioned deployment inventory, supplier map, control matrix, vulnerability and penetration-test evidence, remediation tracking and annual executive confirmation.

Affected workflows

release inventorysupplier governancesecurity assurancecontrol attestation

Boundary: The operator confirmation covers the whole solution and third-party integrations; every registered critical supplier has a separate confirmation duty for its own technology.

Platform registration, game testing and annual technology confirmation are separate regulatory layers.

Curaçao

Curaçao Gaming Authority

B2C operators must implement responsible-gaming controls aligned to the target markets and protect minors, excluded players and other vulnerable people.

In force

Status assessed Aug 13, 2026

Required platform capability

Age and identity controls, operator self-exclusion, cooling-off, player limits, marketing suppression, player information and policy evidence.

Affected workflows

registrationplayer limitsself-exclusionmarketing suppressionpolicy governance

Boundary: Curaçao B2C operations and approved domains; supplier licensing and technical product scope remain separate.

The policy must be implemented in the operating system and customer journey, not retained only as a written document.

Curaçao Gaming Authority

By the end of September 2026, operator-initiated exclusion must be functional and additional responsible-gaming tools must cover risks that require controls beyond the core mandatory set.

Scheduled · Sep 30, 2026

Status assessed Aug 13, 2026

Required platform capability

Operator-initiated exclusion workflow, enforced account state, documented risk triggers, configurable reality checks and time controls, and complete intervention records.

Affected workflows

player-risk monitoringoperator-initiated exclusionsession controlsresponsible-gambling case managementaudit trail

Boundary: Curaçao B2C operations and approved domains; the additional tools depend on the operator's risk profile.

This final implementation stage is not yet in force and remains separate from the responsible-gaming controls already required.

Requirement ledger and provider implementation

This page defines the selected duties and platform capabilities. The separate provider market-access register maps provider × market × product status: supplying entity, permission, technical artifact and named deployment. Keeping the two ledgers separate prevents a feature from being treated as compliance and a supplier permission from being treated as a live implementation.