Published May 22, 2026 · By Editorial Team · 8 min read

Russia's National Self-Exclusion Register Launches 1 September 2026: What Crypto Players Should Know

The Russian government's national self-exclusion register for gambling services, originally enacted under Federal Law 358-FZ in November 2024, goes live on 1 September 2026 after eighteen months of technical buildout by the Federal Tax Service and the Federal Bookmakers' Self-Regulatory Organization. Russian-licensed operators must integrate the register's API into their identity-verification workflows from the launch date; foreign-licensed operators (including all major crypto casinos) are not directly bound but face indirect enforcement pressure through payment processors and ISP blocking. Here is what is changing, who it affects, and what crypto-casino players in Russia should expect.

What happened

Federal Law 358-FZ was signed by President Putin on 28 November 2024 as part of a broader package of gambling-sector reforms. The law authorised a national self-exclusion register administered by the Federal Tax Service (FNS) in coordination with the Bookmakers' Self-Regulatory Organisation. Eighteen months were allocated to the FNS to build the API infrastructure and to operators to integrate. The launch date of 1 September 2026 was confirmed in the FNS's June 2025 implementation order.

The register operates on a simple structure. Russian citizens age 18 and over can self-exclude through a Gosuslugi portal application or in-person at any FNS office. Exclusion durations are 6 months, 1 year, 3 years, or 5 years, with no early-exit provision. The exclusion is enforced at the operator level: any Russian-licensed bookmaker or casino must query the register at account opening and at deposit, with deposits blocked for excluded users. The register's API is documented in the FNS's technical specification published July 2025.

The enforcement architecture is the more interesting part. Russian-licensed bookmakers (TsUPIS-regulated entities including Liga Stavok, Fonbet, BetBoom and Olimp.bet) face direct supervisory enforcement. Foreign-licensed crypto casinos are not directly within scope, but the Federal Service for Supervision of Communications (Roskomnadzor) has been given expanded authority to block payment routes serving foreign-licensed operators whose users are in the self-exclusion register. The enforcement mechanism is therefore indirect for crypto casinos: Russian players' card and bank transfers to foreign-licensed operators can be blocked if those players have self-excluded, even without the operator's cooperation.

Why it matters

Russia is the third-largest gambling market in Europe by gross gaming revenue, with a 2025 GGR estimated at EUR 2.8 billion by H2 Gambling Capital. Crypto-casino penetration is particularly high in Russia relative to other large markets, driven by capital controls and limited fiat on-ramps to foreign-licensed operators. SimilarWeb data for Q1 2026 indicates that approximately 11% of crypto-casino global traffic originates from Russian IPs, making it one of the segment's largest source markets.

The introduction of a national self-exclusion register is a meaningful structural change because it shifts enforcement leverage from operator-side cooperation (which foreign-licensed operators do not provide) to payment-rail enforcement (which the Russian state can apply unilaterally). The Bank of Russia has been preparing the payment-blocking infrastructure since mid-2025, with banks required to maintain a synchronised local copy of the register and to block outbound payments to known gambling-related merchant codes for excluded users.

The model parallels enforcement architectures in Sweden (Spelpaus), the Netherlands (CRUKS), and Germany (OASIS). The Russian implementation is structurally most similar to the Dutch CRUKS — a centralised register with operator-side enforcement for licensed entities and payment-rail enforcement for the foreign-licensed market. The Dutch CRUKS experience has shown payment-rail enforcement to be partially effective: total deposits to foreign-licensed operators from excluded users dropped approximately 60% post-launch in 2021, though full elimination of the channel proved impossible due to cryptocurrency rails.

Who is affected

The clearest direct effects fall on Russian-licensed bookmakers. Liga Stavok, Fonbet, BetBoom, Olimp.bet and the smaller TsUPIS-regulated operators must integrate the register's API by 1 September 2026 or face license suspension. Industry estimates suggest the integration cost per operator is in the range of RUB 12 to 25 million (USD 130,000 to USD 270,000), with the cost concentrated in identity-verification system upgrades. The largest operators have completed integration testing as of Q1 2026; smaller operators are scheduled for completion in Q2.

Foreign-licensed crypto casinos serving Russian players face indirect pressure. The four operators with the highest Russian traffic share — Stake, BC.Game, 1xBet (under various brands) and FortuneJack — have all responded differently. Stake stopped accepting new Russian-document KYC registrations in March 2026, ahead of the law's enforcement date. BC.Game maintains Russian-language support but has begun routing Russian deposits through an additional verification layer that includes register lookup as a voluntary cooperation. 1xBet and FortuneJack have not publicly responded.

Russian players themselves face a more complex environment. Players who self-exclude through the Gosuslugi application will be blocked from Russian-licensed bookmakers immediately and will face increasing friction at foreign-licensed operators as payment-rail enforcement matures. Players who do not self-exclude are not directly affected, but the broader regulatory tightening may reduce payment-rail availability across the segment over time.

What players should do

For Russian players who want self-exclusion to function effectively, the recommended path is to use the Gosuslugi register at launch on 1 September 2026, with the longest exclusion duration that the player believes is appropriate. The 5-year option provides the strongest enforcement leverage. Players should also independently request exclusion at any foreign-licensed operators they have accounts with, by contacting customer support; while operator cooperation is voluntary, most major crypto casinos honour customer-initiated exclusion requests.

Russian players who do not intend to self-exclude should be aware that the payment-rail enforcement infrastructure exists and may, over time, be applied more broadly than just to self-excluded users. Cryptocurrency deposits — particularly via P2P channels rather than bank-routed exchanges — remain the most resistant deposit method to enforcement. Russian players using Bitcoin, USDT or other crypto deposits via P2P exchange routes (Binance P2P, Garantex prior to its sanctioning) face less direct enforcement risk than card-deposit users.

For players who do not self-exclude but who recognise problem-gambling risk, the operator-side tools at major crypto casinos remain available. Stake, BC.Game, Cloudbet and Roobet all offer self-imposed deposit limits, time limits, and self-exclusion at the operator level. These tools do not have the legal weight of the national register, but they are immediately effective and require no government interaction.

Conclusion

The 1 September 2026 launch of Russia's national self-exclusion register is the most significant gambling-regulatory change in the Russian market since the 2014 restriction of online gambling to designated zones. The direct effects on Russian-licensed bookmakers are clear and bounded. The indirect effects on foreign-licensed crypto casinos are the more interesting question: payment-rail enforcement architectures have proven partially effective elsewhere (Netherlands, Sweden) but never completely effective due to cryptocurrency rails. The likely outcome is a measurable but partial reduction in deposit volume from Russian users to foreign-licensed operators, concentrated among self-excluded users initially and potentially broadening over time. For players, the rational response is to use the new register if they want exclusion to work, and to maintain awareness that the enforcement infrastructure may eventually apply more broadly.