Self-exclusion checks
A self-exclusion register lists people who have asked to be barred from gambling. Serving one is a licence breach in every regulated market that operates a register, and the obligation sits on the operator, not on the player. Zyphe calls the register as part of the verification flow, so the answer arrives with the identity evidence rather than from a separate system the operator has to reconcile afterwards.
What it does
The check runs against the register for the market the player is in, using the identity Zyphe has just verified. Because the person has been verified from a government document rather than from a typed name, the lookup is made on confirmed identity data, which is what makes a register answer dependable: a register match is only as good as the name and date of birth it was given.
Zyphe integrates the national registers by default where one exists:
| Register | Market | Notes |
|---|---|---|
| GAMSTOP | United Kingdom | Participation is a condition of a remote operating licence |
| Spelpaus | Sweden | Checked at registration and again at every login, as Spelinspektionen requires |
| Coalition for Fantasy Sports / idPair | United States, daily fantasy sports | Cross-operator self-exclusion for fantasy contests |
Where a market's register is less mature, or where an operator participates in a scheme not listed above, the check is added through the same policy layer rather than requiring an integration release.
When it runs
The register is not consulted once. A player can self-exclude at any time, including after they have onboarded, so the check runs:
- At signup, before the account is usable.
- At first deposit, because that is the point where money first moves.
- On configurable triggers thereafter, so a player who excludes mid-relationship is caught before the next deposit rather than at a periodic review.
A positive result rejects the action and is recorded with the rest of the verification evidence, which is the record a regulator asks for when it examines how an excluded player reached the product.
Where it sits
Self-exclusion is a licence control, not an identity control, and it depends on identity being settled first. In a typical flow it follows document verification and liveness, alongside the age check, and it runs again on the deposit path.
Document verification → Liveness → Age → Self-exclusion → (deposit path: self-exclusion again)
Related
- Antifraud controls, the map of every check
- Document verification, the identity the register is queried with
- AML, sanctions, PEP and adverse media screening, which is a separate obligation