DGA Attribute Descriptions

This document describes the data fields produced by Fortuna Compliance on behalf of a casino operator in each DGA-regulated integration. It covers TamperToken, ROFUS, and SAFE reporting attributes.

TamperToken

A TamperToken is a digital signature issued by the Danish Gambling Authority's TamperToken service. Every SAFE report file must be sealed with a TamperToken — opened before the file is written and closed (finalised) immediately after.

Open token (TamperTokenHent)

Close token (TamperTokenLuk)

ROFUS

ROFUS (Register Over Frivilligt Udelukkede Spillere) is the Danish self-exclusion and problem-gambling register operated by the Danish Gambling Authority. Operators are required to check it before allowing a customer to play or receive marketing.

Common request attributes

The following attributes are present in every ROFUS request:

Every request is also authenticated with your DGA credentials, which are configured for your account during onboarding — you don't need to supply them per call.

Gambler check (GamblerCheck)

Checks whether a person is voluntarily self-excluded from gambling.

Status mapping:

CSRP check (GamblerCSRPValidation)

Checks whether a person is registered in the Credit Register for Problem Gamblers (CSRP) and whether they are a minor.

CSRP status mapping:

Age status mapping:

Commercial (marketing) check (GamblerCasinoCheck)

Checks whether a person has opted out of casino marketing communications.

Marketing status mapping:

Combined evaluation

The evaluation endpoint runs all three checks in a single call and derives two composite blocking flags:

SAFE Reporting

SAFE (Spillemyndighedens Afregnings- og Forretningsdata Enviroment) is the DGA's mandatory reporting system. Operators must submit session data, jackpot events, and daily summary reports as XML files sealed with a TamperToken signature.

The tables below follow DGA's own Description of Attributes spreadsheet exactly — one table per XML structure (KasinospilPrSessionStruktur, JackpotUdløsningStruktur, End Of Day), in DGA's attribute order. What it means paraphrases DGA's own definition of the attribute, to help you fill in the "Applicant's description/interpretation" column DGA asks for. Where it comes from explains how Fortuna Compliance arrives at the value.

For attributes you supply: the source field is a starting point, not the finished answer. DGA expects your description of what you actually send and why — e.g. for SpillerInformationIdentifikation you should describe your own player-ID scheme, not just point at a field name in our API. For attributes Fortuna Compliance supplies on your behalf (file IDs, your licence certificate ID, etc.), you can use our description directly since the value isn't yours to define.

KasinospilPrSessionStruktur (Session report)

One file per session batch, with one entry per session you've reported via POST /api/safe/sessions (see SAFE reporting).

JackpotUdløsningStruktur (Jackpot report)

One file per jackpot event you've reported via POST /api/safe/jackpots (see SAFE reporting).

End Of Day report

One file per calendar day you've reported via POST /api/safe/endofday, with one entry per clientTotals row you submit (see SAFE reporting).

Coverage note: every attribute in DGA's Description of attributes spreadsheet is accounted for above. SpilTerminalIdentifikation is the one exception — it's a valid alternative for land-based terminals, but Fortuna Compliance only reports online channels (SpilHjemmeside), so it's never sent.

Reference tables

Product categories

Game categories