iGaming platform for the Dutch market

The Dutch iGaming market is an openly licensed online gambling market regulated by the Kansspelautoriteit (KSA) under the Remote Gambling Act (Wet Kansspelen op afstand, KOA), which entered into force on 1 April 2021 and opened the licensed market on 1 October 2021. A single remote games of chance licence, extended by game-type annexes, covers online casino and betting. The market pairs a modern, open regime with two hard platform obligations — a CRUKS self-exclusion check before every play session and near-real-time data streaming to the KSA's Controle Databank (CDB) — and one of the steepest GGR tax curves in Europe, reaching approximately 37.8% from 2026 — confirm current rates with the Dutch tax authorities.

Regulatory status

The Netherlands legalised remote gambling later than most of Western Europe, but did so with a fully built-out supervisory architecture. The KOA Act amended the Betting and Gaming Act to create a remote licensing regime; the KSA — the gambling authority since 2012 — opened the application window in April 2021 and admitted the first licensed operators on 1 October 2021.

The model is open licensing: there is no cap on licence numbers and no state monopoly in the remote segment. One remote games of chance licence covers the online offering, with the permitted products defined by annexes per game type — casino games against the house, peer-to-peer games such as poker, and sports and horse-race betting — confirm the current annex structure with the KSA.

Two features distinguish the Dutch regime in practice:

• Enforcement-first posture. The KSA fined unlicensed operators aggressively before and after market opening, and applied a "cooling-off" reliability test that delayed entry for operators with a recent history of illegally serving Dutch players. Reliability screening remains strict.
• Rapid regulatory tightening. Since opening, the Netherlands has banned untargeted advertising (July 2023), introduced net-deposit caps with affordability contact (late 2024 — confirm current rules), and legislated successive tax rises. Operators should treat Dutch compliance as a moving target with short implementation windows.

Operator requirements

Licence types

Licences are granted for five years and are tied to the assessed technical setup: material changes to platform, games or data flows require notification or re-assessment — confirm current terms with the KSA.

Corporate and capital requirements

• EU/EEA seat: the applicant must be established in an EU or EEA member state
• Reliability: beneficial owners, directors and key personnel are screened for integrity, including past conduct toward the Dutch market
• Player funds: player balances must be separated and protected from operator insolvency, via segregated accounts, a foundation structure or equivalent security — confirm current requirements
• AML: full compliance with the Dutch AML act (Wwft) — risk-based customer due diligence, transaction monitoring and unusual-transaction reporting to FIU-Nederland
• Addiction prevention: a documented addiction-prevention policy developed with input from Dutch addiction-care expertise, plus trained staff and intervention procedures
• Fees: a one-off application fee and an ongoing gambling levy funding supervision and addiction care — confirm current amounts with the KSA

Servers, data and local presence

There is no general server-localisation requirement, but the CDB data vault must be hosted and operated to KSA specifications, with the regulator able to access it independently of the operator — confirm current specifications with the KSA. In practice this makes the data architecture, rather than the hosting country, the localisation question that matters. Operators must also appoint contact points for the KSA and maintain records available for inspection.

Review timelines

The KSA quotes roughly six months for a complete application (as of 2026 — confirm current timelines with the regulator). The two long poles are the certification file against the KSA assessment framework and the accepted CDB connection — both platform deliverables. The KSA licensing guide walks through the application dossier section by section.

Taxes

Dutch gambling tax (kansspelbelasting) is levied on gross gaming revenue — stakes minus prizes — and is on one of the steepest upward curves in Europe:

• 30.5% of GGR in 2024 (confirm with the Dutch tax authorities)
• 34.2% of GGR in 2025 (confirm with the Dutch tax authorities)
• 37.8% of GGR from 2026 (confirm with the Dutch tax authorities)

The trajectory matters as much as the level. A business case built on the 2024 rate loses more than seven points of GGR by 2026, before corporate income tax. Practical implications operators model with their platform provider:

• Bonus budgets compress: every euro of bonus-generated GGR is taxed at the marginal rate, so bonus ROI thresholds rise with each step
• Game margin mix shifts toward higher-hold content within the limits of the duty of care
• Cross-market planning: for groups running the Netherlands alongside stake-taxed Germany or 28%-GGR Denmark, consolidated forecasting needs per-market tax engines rather than a blended rate

Technical requirements

The Dutch regime is codified in the KSA's assessment framework and secondary regulations, and much of it binds the platform directly.

RNG and game certification

The platform, games and RNG must be certified by an accredited inspection body against the KSA assessment framework before licensing, covering game fairness, RTP, the integrity of the gaming system and the correctness of data delivered to the CDB. Certification is scoped to the assessed system: significant changes require re-inspection under a controlled change process — consult the current KSA assessment framework for details. Existing certificates from other jurisdictions shorten the work but do not replace the Dutch assessment.

Regulator reporting — the Controle Databank

The CDB (Controle Databank) is the defining Dutch technical requirement. Licensed operators must stream defined game, transaction, account and limit data near-real-time into a data vault the KSA can access directly, structured to the regulator's data model and hosted per KSA requirements. The CDB connection is tested and accepted during licensing; data-quality failures in production are treated as compliance incidents. Alongside the CDB, operators file periodic reports on gaming revenue, addiction-prevention metrics and incidents — confirm current reporting obligations with the KSA.

For a Vuch deployment, the CDB connection is a jurisdiction integration built during the deployment phase: the admin back office provides regulator-reporting tooling with a full audit trail, and mapping platform events to the KSA data model is deployment scope for a Dutch launch.

CRUKS — national self-exclusion registry

CRUKS (Centraal Register Uitsluiting Kansspelen) is the national self-exclusion register, covering online and land-based gambling. The platform obligations are stricter than most European registers:

• A CRUKS check is required before every play session, not only at registration — a returning player must be re-checked each time they start playing
• Lookups are keyed on the BSN (the Dutch citizen service number) via the register's hashed identification scheme — confirm the current identification mechanism with the KSA
• Players with an active exclusion must be refused access immediately, and exclusion can be self-imposed or imposed involuntarily at the request of relatives or the KSA
• Registration flows must present CRUKS information and route players who cannot be verified against the register out of play

Bonus, deposit and limit restrictions

Dutch player-protection rules have tightened every year since opening, and the platform must enforce:

• Player-set limits: mandatory deposit, balance and session limits configured by the player at registration, changeable only with cooling-off on increases — confirm current rules
• Net-deposit caps with affordability contact since late 2024: approximately €700 per month, and €300 for young adults aged 18–24, beyond which deposits are blocked unless an affordability check justifies a higher ceiling — confirm current caps
• Bonus restrictions: no bonuses to 18–24 year olds; bonus offers conditioned on duty-of-care screening; no bonusing of players showing risk indicators — confirm current rules
• Advertising: untargeted gambling advertising banned since July 2023 — no TV, radio or outdoor; online advertising only with targeting controls excluding minors and young adults — confirm current rules
• Duty of care: continuous monitoring of play behaviour with documented, escalating interventions — a supervision focus area where the KSA has already sanctioned licensees

Controls of this kind need to be enforced at platform level through configuration. On the Vuch platform, operational limits and risk-engine thresholds are configuration parameters set per jurisdiction during the mapping phase of a deployment, with limit events and interventions logged with a full audit trail — see the compliance suite.

What a Dutch licence does not cover

The remote games of chance licence covers only the Netherlands and only the game types in the granted annexes. It confers no rights in the Dutch Caribbean territories, which have separate regimes, and no rights in any other EU market. Dutch certification evidence helps in other jurisdictions but does not substitute for their assessments. Operators should also note what the licence cannot protect them from: the tax trajectory and advertising ban are market conditions, not compliance items, and both should be priced into the entry case rather than discovered after launch.

What Vuch provides for the Dutch market

• Modular platform: prediction markets, casino (30,000+ games via provider integrations), or the full stack on a unified wallet with an AMM liquidity core
• Certification roadmap: Vuch holds no KSA assessment or certification today; certification against the KSA assessment framework is scoped as part of deployment, with a certification roadmap and due-diligence pack available on request
• Self-exclusion capability: CRUKS registry integration is implemented and certified per deployment; the platform provides the integration capability with real-time blocking and audit logging
• Regulator-reporting tooling: reports and exports generated from the admin back office with a full audit trail; building the CDB connection to the KSA data model is deployment scope
• Built-in real-time risk engine: transaction velocity control, AML signals, risk scoring and alert escalation with an admin review queue — thresholds configurable for Dutch duty-of-care requirements
• Payments: current rails are USDT deposits and withdrawals; a fiat payment layer is on the roadmap. For a fiat-first market like the Netherlands, local fiat payment integration is a gating item and part of the deployment conversation
• Deployment timeline: white-label deployment typically takes 4–8 weeks depending on integrations and jurisdiction

The Netherlands rewards disciplined operators: the tax curve is steep, but the market is transparent, the rules are enforced evenly, and the technical bar keeps casual competition out. The turnkey casino solution scopes the Dutch requirements — CRUKS and CDB integrations, certification and the jurisdiction configuration — as a single deployment alongside your other markets.