The document matrix

A traceable connection between a source and a technical question. Inspect its scope, compare the available evidence, and keep a copy.

8 records · 2 jurisdictions · Bounded source recheck

Read the status before the statement. “Requirement” is a narrow source-backed summary within the stated scope. “Context only” is a research reference. “Verified” describes the stated reading task, never product compliance. The MGA directive’s complete current consolidation remains NOT_VERIFIED. Unknown dates remain unknown.

8 of 8 records shown

Select a record ID to open its provenance below. On narrow screens, scroll the table horizontally. Review dates concern editorial checks; they are not expiry dates of law.

Scoped official-source records, rechecked 17 November 2026
Record / jurisdictionStatementTechnical domainUse / verificationDates / review

Great Britain
Provide at least three months of account and gambling history directly, and at least twelve months on request.
RTS 1 — Customer account information ↗
LoggingRequirement

verified

Document: 2024-05-07
Read:

Within editorial review interval


Great Britain
Establish customer identity before permitting gambling, for licences covered by condition 17.1.1.
LCCP 17.1.1 — Customer identity verification ↗
IdentityRequirement

verified

Document: Not established
Read:

Within editorial review interval


Great Britain
Monitor customer activity from account opening to identify harm or potential harm.
LCCP 3.4.3 — Remote customer interaction ↗
Player protectionRequirement

verified

Document: Not established
Read:

Within editorial review interval


Great Britain
Use the software technical-standards guidance to investigate the applicable testing and deployment scope.
Technical standards for gambling software ↗
Game suppliersContext only

verified

Document: 2024-07-01
Read:

Within editorial review interval


Great Britain
Start market scoping with the regulator’s description of remote gambling and British consumers.
Remote sector guidance ↗
IdentityContext only

verified

Document: Not established
Read:

Within editorial review interval


Malta
Distinguish critical gaming supply from the operator’s customer-facing role.
Game Providers and Back Office ↗
Game suppliersContext only

verified

Document: Not established
Read:

Within editorial review interval


Malta
Check the legal entity and relevant URL using official register tools.
Licensee Register and URL Checker ↗
IdentityContext only

verified

Document: Not established
Read:

Within editorial review interval


Malta
Locate the Player Protection Directive and establish its applicable version before mapping controls.
Player Protection Directive — V3, January 2023 ↗
Player protectionContext only

unknown

Document: Not established
Read:

Open verification question

Compare the evidence, question by question

Compare the assessed records for the same research question. An empty cell is a research gap. Different documents and scopes are not equivalent obligations, and this view never produces a compliance score.

6 questions · Great Britain / Malta

Customer account history

Great Britain

RL-001 · Requirement
Provide at least three months of account and gambling history directly, and at least twelve months on request.
Verification: verified. Not a universal retention schedule. Commencement of this wording has not been established.

Malta

No assessed source in this collection. This does not establish that no obligation exists.

Comparison boundary: A British customer-access standard is present. No equivalent Maltese account-history provision was assessed in this collection.

Customer identity before gambling

Great Britain

RL-002 · Requirement
Establish customer identity before permitting gambling, for licences covered by condition 17.1.1.
Verification: verified. Excluded licence types matter. No universal identity, age-check or AML procedure is prescribed here.

Malta

No assessed source in this collection. This does not establish that no obligation exists.

Comparison boundary: The Maltese register entry concerns licensee identity, not a customer-verification rule. Those are different questions.

Customer interaction and player protection

Great Britain

RL-003 · Requirement
Monitor customer activity from account opening to identify harm or potential harm.
Verification: verified. 12 September 2022 applies to paragraph 4, not every part of 3.4.3. This is not a complete account of customer-interaction duties.

Malta

RL-008 · Context only
Locate the Player Protection Directive and establish its applicable version before mapping controls.
Verification: unknown. Current consolidation unverified. Original commencement and later transitions differ. No current Maltese requirement is extracted.

Comparison boundary: A scoped British paragraph is compared with the identity of a Maltese document whose current consolidation is unresolved. These are not equivalent rules.

Software and supply activities

Great Britain

RL-004 · Context only
Use the software technical-standards guidance to investigate the applicable testing and deployment scope.
Verification: verified. No build has been tested. The complete current testing strategy has not been audited; this page is a reading entry point.

Malta

RL-006 · Context only
Distinguish critical gaming supply from the operator’s customer-facing role.
Verification: verified. No specific integration is classified. Application guidance is not a complete legal instrument or proof of authorisation.

Comparison boundary: British deployment/testing guidance and Maltese supply-application guidance describe different boundaries. Neither certifies a particular build.

Checking the licensed entity

Great Britain

No assessed source in this collection. This does not establish that no obligation exists.

Malta

RL-007 · Context only
Check the legal entity and relevant URL using official register tools.
Verification: verified. No register query, individual entity, licence or domain has been assessed.

Comparison boundary: Only the Maltese register entry point was assessed. The gap does not mean that Great Britain has no register.

Remote-market geographic scope

Great Britain

RL-005 · Context only
Start market scoping with the regulator’s description of remote gambling and British consumers.
Verification: verified. The linked passage supports the stated summary. No particular organisation, product or licence has been assessed.

Malta

No assessed source in this collection. This does not establish that no obligation exists.

Comparison boundary: The British remote-sector entry point is present. No equivalent Maltese market-access assessment is included.

What leaves your browser?

Nothing is submitted by this tool. Filters and comparisons operate on this edition’s local collection. Downloads preserve source URLs, document types, dates, scope, missing data and limitations. CSV and TSV use UTF-8, quoted fields, a byte-order mark and spreadsheet-formula escaping.

The thirty-day review interval is an editorial scheduling choice. It is not a legal deadline. An overdue record needs a source recheck; it does not prove that the underlying text changed. A date-filter gap does not establish that a document has no date.

Read how document types affect a claim and how to follow a change notice. Follow our source methodology before using a record in a decision.