Network Northwest

Markets · Germany

The most mechanised of the five

Germany turned player protection into infrastructure. A central blocking file, compulsory connection, a query before access to play — the obligations are unusually concrete, and so is the integration against them.

  • GGLsupervisor
  • OASISblocking file
  • Pre-accessquery timing

The regime

Who supervises and what answers the exclusion question

Supervisor
Gemeinsame Glücksspielbehörde der Länder (GGL)

The joint authority supervising licensed gambling under the 2021 State Treaty.

Self-exclusion source
OASIS

The central blocking file operated by the Regierungspräsidium Darmstadt. Connection is compulsory for licensed operators and the check precedes access to play.

Age floor applied
18

Configured per market in your policy and versioned with it.

Processing region
United Kingdom or European Union

Chosen once per operator. Data does not leave the chosen region.

In this market

What the platform does differently here

Exclusion

At
registration + login
Covers
self and third-party

The query precedes access, by design

OASIS holds both self-imposed exclusions and bans entered by third parties, and the match runs before the player reaches the product rather than alongside it.

  • Identity is resolved first, so the query runs on normalised data
  • Both exclusion kinds are returned as a hit; the distinction is recorded, not weighed

Identity

Primary
Personalausweis

German document series, read properly

The national identity card is the document most German registrations present, and the routing prefers the sources that read its series best rather than treating all documents alike.

  • Issuing-authority-level routing rather than country-level
  • Residence permits handled as first-class documents, not exceptions

Limits

Scope
beyond our boundary

Cross-operator limits are a platform problem, not a product one

The German regime also runs central deposit-limit machinery that sits outside identity verification. We check the exclusion file and return the identity; the limit file is a separate obligation and we say so rather than implying coverage we do not have.

  • Our scope is stated so the gap is visible at integration time, not at audit time

Integration

Questions that come up here

Is the OASIS result cached?

No. The value of a pre-access query is that it reflects the file at that moment; a cached answer from this morning is an answer about this morning. Each required check is a live query, and the timestamp recorded is the query's.

What happens if OASIS is unreachable?

The check does not return pass. An exclusion query that could not be answered is reported as such, and your policy decides whether that holds the registration or routes it to review — which is a decision with licence consequences and therefore yours, not a default we pick for you.