The Netherlands opened its regulated online gambling framework in October 2021. Five years in, the market is mature and the channelisation picture is mixed. Operators that have been through the process know the requirements well. The Kansspelautoriteit (KSA) runs a structured framework. Clean applications get predictable timelines. Applications that miss specific requirements get predictably rejected. This guide covers what operators actually need to bring to the application file.
KSA licence types: what is covered
The Dutch online gambling licence covers remote gambling under the Remote Gambling Act (Wet op de kansspelen, 2021 amendment). One licence type covers casino and sportsbook. Lottery and bingo run under separate frameworks. Live betting and poker are included. Some product types carry specific operational restrictions.
Most applicants run multi-product platforms (casino plus sportsbook). That is the standard licence shape. Single-product applications go through the same framework with a matching, smaller scope.
Application capital and corporate structure
KSA requires:
Corporate substance in the Netherlands. This is the requirement most offshore operators underestimate. KSA expects a genuine Dutch presence. That means directors with real Dutch tax residency or Dutch-based responsibility, a registered office, and operational decisions made in the Netherlands.
Minimum capital and financial position. The operator must show it has enough money to run the business sustainably. The published minimum is functional rather than a headline number. Realistic operators plan €1m to €3m in working capital. On top of that comes €5m to €15m of operating, marketing, and platform spend over the first 18 months.
Beneficial ownership disclosure. You must fully disclose ultimate beneficial owners, directors, and key persons. KSA runs deep background checks on them. Weak or evasive disclosure leads to rejection, every time.
The Dutch cooling-off rule and historical-activity disclosure
For offshore operators, this is the single most important issue. The cooling-off rule applies to operators that previously served the Dutch market from offshore or without a licence.
How cooling-off works in practice. KSA reviews the operator's past activity toward Dutch players. Operators that clearly stopped Dutch-market activity by a set date are eligible. In the early licence rounds that date was 2018 to 2019; it has shifted in later rounds. Operators with ongoing or recent Dutch exposure face a cooling-off period first. It typically runs 18 to 30 months from the moment the activity stopped.
What "Dutch-market activity" means. KSA reads it broadly. Any material acquisition or retention activity aimed at Dutch players counts. It does not matter whether your licence allowed that activity elsewhere. Affiliate-driven Dutch traffic counts. So do Dutch-language site content, Dutch-targeted promotions, and Dutch payment integrations.
Why this surprises operators. Many offshore operators served Dutch players by accident, not by strategy. They do not think of incidental traffic as material activity. KSA does. Applications that fail to address past Dutch exposure honestly fail, consistently.
The honest preparation. Operators with past Dutch exposure should document clearly when the activity stopped. Accept what cooling-off means for the timeline. Then address the history openly in the application instead of working around it.
RA (Responsible Gambling) framework
The KSA responsible gambling framework differs from the MGA, UKGC, and other Tier-1 European frameworks. Operators need to build for these specific requirements:
CRUKS integration. The Dutch self-exclusion register is mandatory. Every registration must check CRUKS in real time before account approval. Every deposit must validate against current CRUKS status. The technical integration is simple. The operational impact is not: CRUKS-excluded players drop out of your addressable population, which shapes the unit economics.
Deposit limit framework. Players set deposit limits at registration. KSA requires specific operator actions when players near their limits or try to raise them. Limit increases carry mandatory cooling-off periods. Rapid spending escalation triggers structured interventions.
Player monitoring and intervention. Operators must watch player behaviour for problem gambling signs and run structured interventions. KSA examines intervention records during licensing and reviews. Operators with weak records face real regulatory pressure.
Bonus and promotional restrictions. Bonuses are restricted in structure and in audience. No untargeted high-value offers. No bonuses tied to deposit thresholds in specific setups. No promotion to vulnerable players. No promotion to players with specific behaviour patterns.
Timeline: application to first deposit
Realistic KSA timelines:
Pre-application preparation: 3 to 6 months. Build the application file. Set up corporate substance. Finish technical readiness work. Build compliance infrastructure to KSA standards. Complete legal due diligence on directors and beneficial owners.
Application review: 6 to 10 months. The KSA cycle covers initial review, query rounds, technical assurance, and final approval. Cooling-off issues can stretch this a lot.
Post-grant launch preparation: 1 to 3 months. Final technical integration. Payment partner activation. Marketing and brand launch preparation. A soft-launch validation period.
Realistic end-to-end: 10 to 19 months from the decision to apply to first deposit. Operators that expect six months, or treat KSA as paperwork, miss launch targets. They then burn capital through a long pre-revenue period.
Compliance infrastructure required pre-launch
KSA expects specific compliance infrastructure to be in place before licence grant:
Dutch-resident MLRO and compliance officer. The framework prefers, and in practice requires, senior compliance staff based in the Netherlands or Dutch tax resident. A part-time or remote money laundering reporting officer (MLRO) may work under the MGA. It does not survive KSA scrutiny.
Dutch-language player support. You need real-time Dutch-language support during the hours you advertise. English-only outsourced support fails KSA expectations, every time.
Local banking and payment partner relationships. KSA does not formally require a Dutch bank. In practice you need Dutch-market payment service provider (PSP) relationships, iDEAL integration, and local payment processing to be viable. KSA reviews these during the application.
Player fund segregation. Player funds must be kept separate, with the specific compliance overhead the Dutch framework adds.
Channelisation: how the Dutch market actually splits
Channelisation has worried the Dutch market since the framework opened. Recent KSA estimates put regulated channelisation at about 50 to 70 percent, depending on how you measure it. Offshore competition keeps taking meaningful share. The reasons covered in the channelisation piece apply directly to the Dutch market.
For strategy, this means a licence is not a market-share grant. Licensed operators compete with each other and with persistent offshore sites. The winners in the Dutch market invested heavily in brand, lifecycle, and partnership channels. Those investments compound over time.
Why some applicants get rejected on grounds the application form does not surface
Five rejection patterns seen in recent application rounds:
Not enough corporate substance. Operators that apply with a shell Dutch entity and no real Dutch presence get rejected, consistently. KSA checks substance in practice, not just on paper.
Unresolved past Dutch-market exposure. Operators that hide past activity, or understate it, get rejected. Honest disclosure is the better strategy.
Weak compliance infrastructure. Operators that apply with compliance plans instead of working compliance operations get rejected. KSA expects a functioning compliance team at application, not a promise for later.
Beneficial ownership concerns. Owners that fail the KSA background review sink the application. That includes regulatory issues elsewhere, financial integrity questions, and undisclosed relationships.
Technical assurance gaps. Platforms that miss KSA technical standards get rejected. Or they face long extra rounds of technical queries.
Total cost of KSA application and operations
Year-one realistic operator cost:
Application and pre-launch: €250,000 to €500,000. That covers legal work, technical readiness, the compliance build, and corporate structuring.
First-year compliance overhead: €400,000 to €800,000. That covers the compliance team, legal counsel, audit, and day-to-day compliance work.
Gaming tax. The Dutch gaming tax on gross gaming revenue (GGR) is 30.5 percent, rising to 34 percent in stages. The tax shapes the unit economics of the Dutch market. It is why many successful Dutch licensees run lean compliance and technology stacks to protect margin.
Total realistic year-one operator cost beyond gaming tax: €650,000 to €1,300,000.
Starting the KSA application conversation
Considering Dutch entry? You need an honest read on three questions. Past Dutch exposure. Willingness to build real corporate substance. A capital plan that covers the long timeline. WhatsApp the situation; same-day reply on whether your profile fits and what realistic next steps look like. Through the Netherlands base and the Dutch Gambling Association founding-partner role, the practice sees directly how KSA reviews applications in current rounds.