The State of iGaming Compliance Technology Across Regulated Markets

Every operator with more than one licence eventually asks the same question: how much of our compliance stack can we build once and point at every regulator? The honest answer is most of the plumbing, and almost none of the parts a supervisor actually inspects.

The vendor pitch for iGaming compliance technology is a single platform that satisfies Malta, Great Britain and everyone else out of one configuration screen. It is a seductive story because a large part of it is true. The identity checks, the transaction monitoring, the game integrity assurance and the audit logging really are shared machinery, and a firm that rebuilds them per jurisdiction is wasting money. The trouble starts when the shared machinery is mistaken for the whole job. Underneath a common architecture sit obligations that diverge on thresholds, timing and evidence, and those are precisely the points a regulator tests. This is a survey of where the landscape has converged, where it has not, and what that means for anyone running more than one licence.

The controls that genuinely travel

Start with what does generalise, because it is the reason a multi-licence platform is worth building at all. Identity capture, document verification, sanctions and PEP screening, transaction monitoring, self-exclusion enforcement and immutable event logging are functionally the same regardless of which authority you answer to. Every regulated market wants to know that the person playing is who they claim to be, that their money is not dirty, and that you can reconstruct what happened. A well-designed operator builds these as services with a jurisdiction parameter, not as separate stacks. The shared control architecture is real, and it is the sensible default.

Free · 4 minutes

Do you know where AI is already being used in your business — and what it can see?

Fourteen questions on shadow AI, data exposure, oversight, and governance debt — the gap between how fast AI is arriving and how much control you have over it. Banded finding on screen, full sheet by email.

What does not travel is the calibration. The same monitoring engine has to fire on different thresholds, hold data for different periods, and produce evidence in different shapes for each regulator. The engineering that matters is not the control itself; it is the configuration surface that lets one control behave like several without forking the codebase.

Player and age verification: where the shared layer stops

Age and identity verification is the first place the single-platform theory frays. The mechanics are common — capture a document, match a face, check a database — but the trigger points and the follow-through are set locally. Great Britain requires age and identity to be verified before a customer can deposit or gamble, and layers on financial checks that have no clean equivalent elsewhere: the Gambling Commission’s light-touch financial vulnerability checks came into force on 30 August 2024 at a threshold of £500 net deposits in a rolling 30-day period, then dropped to £150 from 28 February 2025. Malta imposes no such affordability regime. An operator serving both cannot run one rulebook; it runs one verification service with two very different downstream flows, and the British flow reaches into data — credit and public-record signals — that a Maltese licence never asks for.

Ongoing KYC compounds the divergence. Verification is not a gate you pass once; it is a state you maintain, refreshed on risk triggers, deposit velocity and time. The refresh logic is where jurisdictions pull apart, and where a lot of the real integration work sits. This is the substance behind player verification technology in licensed iGaming: the hard part is not the initial check but the discipline of keeping it current across estates that define “current” differently.

RNG and RTP: from the annual certificate to continuous monitoring

Game integrity is the most technically distinctive part of iGaming compliance and the part changing fastest. Random number generators and return-to-player figures have traditionally been assured by an independent test house — GLI, eCOGRA, iTech Labs and their peers — issuing a certificate against a regulator’s technical standards. Malta sets a minimum RTP of 85%, streamlined across remote and land-based sectors in 2021 from a previous 92% floor. A certificate is a point-in-time statement: the RNG was sound, and the game paid as configured, on the day it was tested.

The direction of travel is away from that snapshot. Regulators and operators alike are moving toward continuous monitoring — telemetry that watches actual RTP against configured RTP in production, flags drift, and catches the case a game was patched or misconfigured after certification. This is a genuine architectural shift. An annual certificate is a document you file; continuous RTP assurance is a data pipeline you run, with its own storage, alerting and retention obligations. Operators who treat game integrity as a compliance PDF rather than a monitored signal are building to yesterday’s expectation.

AML sits on a different clock

Anti-money-laundering controls are where iGaming stops being a gambling problem and becomes a financial-services one. In Malta, licensees are subject persons under the anti-money-laundering framework supervised by the FIAU alongside the MGA; in Great Britain the obligation runs through the Gambling Commission and the Proceeds of Crime Act. The transaction-monitoring engine is shared, but the reporting obligations, suspicious-activity thresholds and the definition of what must be escalated are set by each regime and, for EU operators, shaped by the incoming single AML rulebook. The control is common; the trigger and the destination of the report are not.

This is the tension a survey has to name plainly: AML and gambling supervision impose long record-retention duties, often five years or more beyond the end of a customer relationship, and those duties are non-negotiable. They collide directly with the data-minimisation instinct of privacy law, which is the next problem.

Residency versus retention

Player data sits under two forces pulling in opposite directions. AML and gambling rules demand you keep transaction and verification records for years. Data-protection law demands you hold personal data no longer than necessary and, in some markets, keep it within defined borders or under defined controls. An operator cannot satisfy both by instinct; it has to design for the conflict — separating the records it is compelled to retain from the personal data it should purge, and being able to show a supervisor exactly which rule governs which field. Add the regulatory pressure some authorities apply toward local data residency or accessible-copy requirements, and a naive single-database design fails two regulators at once. The technical architecture cross-border iGaming actually requires treats retention, deletion and residency as distinct axes, not a single storage decision.

What one platform still cannot absorb

The map, then, is this. The control primitives — verification, screening, monitoring, integrity assurance, logging — are genuinely shared, and building them once is correct. The calibration on top of them is jurisdictional and irreducible: British affordability checks with no Maltese analogue, divergent RTP floors, per-regulator AML reporting, and a retention-versus-residency conflict that no single storage design resolves. A platform that exposes those as configuration rather than hard-coding one regulator’s rules is the right architecture, and it is also the harder one to build.

The failure mode is predictable. A firm buys the single-platform story, configures it to its primary licence, and discovers at the second market’s audit that “one architecture for many regulators” quietly meant “one regulator’s architecture, applied hopefully to the rest.” The shared layer saves you real money. It does not save you the jurisdiction-specific work — it just makes that work visible, which is the point at which most operators find out how much of it they had been ignoring.

Most technology problems are not technology problems. They are control problems.

The systems exist. The investment has been made. The question is whether leadership can understand, direct, evidence, and sustain what those systems produce. Find out where control exists — and where it only appears to.