Sweden Spelpaus Self-Exclusion — Technical Integration Guide for 2026

Why Spelpaus matters for Swedish iGaming operations

Sweden’s January 2019 re-regulation of the online gambling market under the Spellag established Spelinspektionen as the supervisory authority and introduced Spelpaus as the mandatory central self-exclusion register. Spelpaus is the most operationally-substantive consumer-protection infrastructure in EU iGaming — substantively distinguishing the Swedish framework from operator-level self-exclusion arrangements in other jurisdictions.

The defining feature: centralised cross-operator scope. A customer self-exclusion at any single Spelinspektionen-licensed operator applies simultaneously across all Spelinspektionen-licensed operators. The customer doesn’t need to self-exclude at each operator individually — registration on Spelpaus triggers automatic exclusion across the Swedish licensed market.

For operators, the integration is non-negotiable. Spelpaus integration is a precondition for Spelinspektionen Commercial Online Gambling Licence operations. Inadequate integration produces immediate supervisory engagement and potential licence-conditional restrictions. Active enforcement on integration quality through Spelinspektionen audit programme.

How Spelpaus actually works

The Spelpaus register is a real-time customer-status database administered by Spelinspektionen. Customers register through the public-facing Spelpaus.se service using Swedish BankID identification, specifying their self-exclusion period (1, 3, 6, 12 months, or permanent). Spelinspektionen maintains the central register and operates the API infrastructure that operators query.

The operator-side integration requires:

Real-time customer-status API queries at three trigger points:

• At customer login (verify the logging-in customer is not Spelpaus-registered)
• At deposit attempt (verify before processing any payment)
• At bet placement (verify before processing any gambling activity)

Synchronous response handling — queries must return within sub-second response times to avoid customer-experience disruption. Operators build query caching strategies that respect real-time requirements while minimising query volume.

Default-denial fallback — if API query cannot be completed (Spelpaus outage, integration error, timeout), operator must default to denial of customer activity. Spelinspektionen guidance is explicit on this — incomplete check cannot permit activity to proceed.

Customer-status integration with operator systems — Spelpaus status integrated into customer management, deposit processing, bet processing, marketing systems. Status changes (customer adds to Spelpaus mid-relationship) propagate through operator infrastructure to suppress all subsequent gambling activity and marketing.

Marketing suppression — the often-missed dimension

Spelpaus integration extends beyond gambling-activity blocking. Operators must suppress all marketing communications to self-excluded customers:

Email marketing — Spelpaus-registered customers must be excluded from all email campaigns. Operator email infrastructure must integrate Spelpaus status as a suppression criterion. The suppression must persist throughout the self-exclusion period.

Push notifications — mobile-app push notifications similarly suppressed for Spelpaus-registered customers throughout exclusion period.

SMS marketing — text-message marketing suppressed.

Retargeting and paid social — digital advertising platforms (Google Ads, Meta Ads, programmatic) must exclude Spelpaus-registered customers from targeting. This typically requires audience-management infrastructure that segments Spelpaus-registered customers out of all targeting audiences.

Affiliate marketing — affiliate partners cannot direct Spelpaus-registered customers to operator services. Operators must communicate Spelpaus suppression requirements to affiliate networks and integrate suppression into affiliate-tracking infrastructure.

The marketing-suppression requirement is one of the more operationally-complex aspects of Spelpaus integration because it requires coordination across multiple marketing infrastructure components. Many operators built robust gambling-activity Spelpaus integration but lighter marketing-suppression infrastructure, leading to compliance gaps when self-excluded customers continued receiving marketing through poorly-integrated channels.

Technical integration mechanics

The Spelpaus API integration is technically straightforward but operationally substantive.

Spelinspektionen-provided API specification — REST API with well-documented endpoints for customer-status queries, status-change webhooks, batch queries (for marketing-suppression infrastructure), and audit-trail queries.

Authentication — operator API credentials issued by Spelinspektionen as part of licence-grant process. Credential management and rotation follows standard API-security practices.

Customer identification — Spelpaus identifies customers by Swedish personal identity number (personnummer). Operators must verify customer identity through Swedish BankID or equivalent at onboarding to enable accurate Spelpaus query.

Caching strategies — operators implement caching to minimise API query volume while respecting real-time requirements. Common pattern: in-memory cache with 60-second TTL plus real-time invalidation on status-change webhook. Substantive customer-status updates trigger immediate cache invalidation.

Resilience patterns — operators implement retry logic, circuit breakers, and fallback handling for Spelpaus API issues. Default-denial behaviour on integration failures protects compliance posture while creating customer-experience disruption when integration is unstable.

Audit-trail infrastructure — operators must maintain audit trail of Spelpaus queries, query results, and operator actions taken based on results. The audit infrastructure supports Spelinspektionen supervisory reviews and operator-internal compliance reporting.

Integration certification process

Spelinspektionen operates a formal Spelpaus integration certification process for operators before live operations. The process:

Integration design review — Spelinspektionen reviews operator integration architecture, API client implementation, caching strategy, fallback handling, marketing-suppression infrastructure.

Test-environment integration — operator integrates with Spelinspektionen test environment, runs test scenarios for normal operations, status-change events, API outages, edge cases.

Live-environment certification — Spelinspektionen approves operator integration for live customer operations. Integration must demonstrate compliance with response-time, fallback-handling, and marketing-suppression requirements.

Ongoing supervisory monitoring — Spelinspektionen continues monitoring integration quality post-certification through periodic audit, customer complaint investigation, and supervisory engagement.

Typical integration certification timeline: 3-6 months from initial development to live-environment certification. The substantive timeline is in the certification process and marketing-suppression infrastructure integration, not the core API client implementation.

Customer-experience workflow

Spelpaus integration creates specific customer-experience patterns that operators must support:

At Spelpaus self-exclusion — customer registers on Spelpaus.se, triggers status update via webhook to operator. Operator immediately blocks customer’s ongoing session, closes any open bets at customer’s request, processes outstanding withdrawals, suspends customer’s account. Marketing infrastructure flags customer for suppression.

During self-exclusion period — customer cannot log in, deposit, or place bets at any Spelinspektionen-licensed operator. Operator customer-service teams have read-only visibility for customer-service queries but cannot reactivate account.

At self-exclusion expiry — for time-limited self-exclusions (1, 3, 6, 12 months), customer status reverts automatically at expiry. Operator can resume normal customer relationship. For permanent self-exclusions, no automatic reactivation — customer must contact Spelinspektionen to request removal from Spelpaus.

Customer-service handling — operator customer-service teams need training on Spelpaus implications, cannot circumvent self-exclusion, must direct customers to Spelpaus.se for self-exclusion management.

Cross-jurisdictional implications

Spelpaus applies only to Spelinspektionen-licensed operations. Customers self-excluded on Spelpaus can still access non-Swedish-licensed operators (Curaçao-licensed, Anjouan-licensed, other-jurisdiction-licensed). This is the intentional regulatory boundary — Sweden’s framework operates within the scope of Swedish-licensed operations.

For Swedish customers genuinely seeking complete self-exclusion across all gambling activity, Spelpaus is necessary but not sufficient. Customers need to combine Spelpaus registration with operator-level self-exclusion at any non-Swedish-licensed operators they have used, plus payment-blocking arrangements with their banks where available.

Operators with operations in multiple jurisdictions face the question of cross-jurisdictional self-exclusion coordination. Sweden’s Spelpaus, Denmark’s ROFUS, Germany’s OASIS register, UK’s GAMSTOP — each operates within its own jurisdiction’s scope. Operators with customers across multiple jurisdictions integrate with each relevant self-exclusion register separately. No EU-wide centralised self-exclusion register exists; the substantive consumer-protection coordination happens at member-state level.

Operational cost

Spelpaus integration cost varies by operator size and existing infrastructure:

Initial integration build — EUR 100,000-400,000 covering API integration, caching infrastructure, fallback handling, marketing-suppression integration, customer-experience workflow integration, audit-trail infrastructure, Spelinspektionen certification engagement.

Ongoing operational cost — minimal direct cost (API queries are typically free for licensed operators) but substantive indirect cost through marketing-suppression overhead, customer-service training and workflow, ongoing compliance monitoring and reporting.

Comparison with non-Spelpaus jurisdictions — Spelpaus integration represents Spelinspektionen-specific operational overhead. Operators expanding to Swedish operations from non-Spelpaus jurisdictions should budget the integration cost into Swedish market-entry economics.

When the Spelinspektionen licence works despite Spelpaus overhead

Spelpaus integration represents substantive operational overhead but Sweden’s iGaming market remains commercially attractive for operators with capacity to absorb it:

Operators with substantial Swedish customer base — established operations where Spelpaus integration is amortised across substantial revenue.

Operators with mature consumer-protection infrastructure — operators that have already built sophisticated self-exclusion, marketing-suppression, and customer-protection infrastructure for other jurisdictions face proportionately-lighter incremental cost for Spelpaus integration.

Operators with technical depth — operators with strong technical teams can build Spelpaus integration efficiently as part of broader consumer-protection infrastructure.

The Spelinspektionen licence is the wrong choice for operators where Spelpaus integration cost cannot be amortised across substantial Swedish revenue, operators with limited technical infrastructure capacity, or operators whose business model is incompatible with the Bonus Once Rule and other Swedish-specific commercial restrictions that combine with Spelpaus integration to define the Swedish operational environment.