Platform · 06

Onboarding is where the obligation starts.

A player verified in March can be sanctioned in June and self-excluded in September. A platform that only runs at registration tells you about none of it.

Continuousre-screening
Automaticcase reopening
Webhookor pull

What is watched

Three clocks, running independently

Lists

Cadence
on every list change

Sanctions and PEP changes re-screen the book

When a list changes, the players it could affect are re-screened — not at the next login, and not at an annual review.

Only the delta is screened, so the cost is the change and not the book
A new hit reopens the case with the original evidence attached

Registers

Cadence
continuous

Exclusion changes reach you the same day

A player who self-excludes after registering is the single most consequential change that can happen to an account, and it has to arrive as an event rather than be discovered at the next login.

Register-backed markets are reconciled continuously
Operator-file markets are reconciled on every file change you publish

Documents

Notice
ahead of expiry

Expiry is a date, so it can be anticipated

A document that expires does not invalidate the verification that used it, but it does start a clock on the next one. The clock is visible before it runs out.

Advance notice rather than an expiry event
Re-verification reuses the file rather than starting from nothing

Lifecycle

Where monitoring attaches

A monitoring hit reopens a closed case rather than creating an unrelated one.

1
The case is the unit
A reopened case carries its original evidence, so a reviewer sees the history rather than a fresh alert with no context.
2
Review returns to collecting
When more evidence is needed the case moves back a state rather than failing. The state machine is honest about the fact that most reviews end in a pass.