SIFS 2026:3, finalised 23 April and published 29 April 2026, mandates that all licensed operators integrate a new API for real-time verification of Spelpaus.se self-exclusion status, using regulator-issued credentials, entering force 1 August 2026. This is a fixed-date, mandatory technical-integration obligation rather than guidance, though as a standing regulator instrument it remains fragile in durability terms -- revisable by Spelinspektionen without legislative process. It represents the clearest, most concretely dated technical-compliance development in this cycle's reform bundle.
Jurisdictions › Sweden › Technical compliance
Sweden · Question 08 of 11
Sweden Gambling — Technical compliance: What must the platform meet?
Favourable · Probable · Not reviewed · 1 post-review update · Not reviewed · Back to full Sweden report →
Key section parameters
| Jurisdiction | Sweden (SE) |
|---|---|
| Regulator | Spelinspektionen |
| Favourability | Favourable |
| Confidence | Probable |
| Review status | Not reviewed · 1 post-review update · Not reviewed |
| Last collected | 25 Oct 2026 |
Summary answer
SIFS 2026:3, finalised 23 April and published 29 April 2026, mandates that all licensed operators integrate a new API for real-time verification of Spelpaus.se self-exclusion status, using regulator-issued credentials, entering force 1 August 2026. This is a fixed-date, mandatory technical-integrati…
Not reviewed Information added after the 12 Aug 2026 expert review — published for currency and labelled not reviewed.
Not reviewed Read update
SIFS 2026:3 converts Spelpaus self-exclusion from operator-designed checks into a mandatory, API-based real-time verification model, requiring regulator-issued Actor IDs and API keys, effective 1 August 2026. This is a fragile instrument in evidentiary terms: the primary regulatory text was not directly retrieved this cycle, and the finding rests on secondary trade-press reporting corroborated across two lower-tier outlets, so it carries only probable confidence despite its material effect on operators' technical build requirements. Operators should anticipate integration work against a regulator-issued API specification rather than continuing to rely on internally designed self-exclusion checks once the effective date passes.