Home > Sustainable Gambling > Responsible gambling > Dutch self-exclusion system returns to normal after latest glitch

Dutch self-exclusion system returns to normal after latest glitch

| By Robert Fletcher
Dutch gambling regulator de Kansspelautoriteit (KSA) confirmed the country’s Cruks self-exclusion system has returned to normal operation following another glitch that meant it was unable to reliably register new individuals or perform checks.
Cruks

The issue with Cruks was first reported on 11 November and concerned a malfunction with BSN checks, which are used to validate a person who registers with the system.

A BSN, also known as a citizen service number, is a unique identification given to each Dutch resident that the government uses to process personal data.

KSA said the issue meant some consumers were unable to register with Cruks for the past few days, while licensed operators also encountered issues when carrying out checks through the system.

However, KSA said the system is now operating normally again, saying the cause of the issue was with the BSN management facility.

Previous Cruks malfunctions

The latest glitch comes after a problem with Cruks’ use of the DigiD identification system temporarily halted all new registrations at the end of September. This issue was resolved quickly, with KSA saying that the malfunction did not prevent sites signed up to Cruks from checking the details of existing registered users.

In August, KSA announced more than 20,000 people had registered with the self-exclusion system since its launch in October 2021. 

Cruks was set to go live the same day that the country launched its regulated online gambling market. The Dutch Gambling Act requires licensed retail and online gambling organisations to compare a player’s details with Cruks before allowing them to participate in games of chance.

However, when the market launched, a malfunction with the self-exclusion system meant it could not operate. As a result, the launch of online gambling in the Netherlands was delayed until the issue with Cruks was resolved.

Subscribe to the iGaming newsletter