Network Northwest

Markets · Portugal

Small, strict, and held at the regulator

Portugal supervises online gambling through the SRIJ, with the exclusion list held on the regulator's side as in Italy. The regime is tighter than its market size suggests, and the integration is the same shape as the Italian one.

  • SRIJsupervisor
  • Operator fileexclusion authority
  • pt-PTplayer-facing language

The regime

Who supervises and what answers the exclusion question

Supervisor
Serviço de Regulação e Inspeção de Jogos (SRIJ)

The gambling regulation and inspection service, part of Turismo de Portugal.

Self-exclusion source
Operator exclusion file

As in Italy, the list is administered by the regulator rather than exposed for operator query, so your own file is the authority.

Age floor applied
18

Configured per market in your policy and versioned with it.

Processing region
European Union

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

In this market

What the platform does differently here

Exclusion

Source
operator file

Reconciled file, identical recording

The mechanism is the Italian one: your published file is the authority, it is reconciled on every change, and the check records which version answered.

  • Same refusal behaviour as a register hit
  • Version of the file recorded against the check

Language

Player-facing
pt-PT

European Portuguese, not Brazilian

The capture flow a Portuguese player sees is in European Portuguese. It is a small thing that is noticed immediately by the people it is wrong for.

  • SDK strings and document prompts in pt-PT
  • Brazilian Portuguese is a separate string set, not a fallback

Integration

Questions that come up here

Is Portugal worth a separate integration?

It is not a separate integration — that is the argument for the layer. It is a market value in a check you are already making, with its own policy, its own exclusion mechanism and its own language, and none of that reaches your code.