GAMSTOP EXPLAINED
What is GAMSTOP and how the UK self-exclusion register works
The National Online Self-Exclusion Scheme, run by the National Online Self-Exclusion Scheme Ltd, sits behind every UKGC-licensed operator and blocks new accounts by name once you enrol. Here is what the register actually is, the periods it locks you into, what it does not cover, and where UK players go while it runs.
Written by
Tim Mirroman
Last updated
What GAMSTOP is and who actually runs it
GAMSTOP is the National Online Self-Exclusion Scheme for UK online gambling. It is a centralised, name-based blocking register: when you enrol, your personal details are added to a database that every UK Gambling Commission licensee is required to check against before opening a new account or allowing an existing account to be used. The moment your name is on the register, UKGC operators are legally required to close your accounts and refuse new signups until the exclusion lifts.
The scheme is operated by the National Online Self-Exclusion Scheme Ltd, a company limited by guarantee based in London. It is a nonprofit body funded by the gambling industry itself (each UKGC licensee contributes) but sits at arm’s length from the UKGC as regulator. The Gambling Commission does not run GAMSTOP directly; it mandates that its licensees participate.
The regulatory background behind GAMSTOP
GAMSTOP was launched in April 2018 as a voluntary scheme. UKGC-licensed operators could sign up but were not required to. Coverage was uneven for the first two years: some of the larger brands joined immediately, but many smaller sites did not, and a determined registrant could still open accounts at half the market.
When it became mandatory: 31 March 2020
The Gambling Commission amended its Licence Conditions and Codes of Practice (LCCP) to require every remote-gambling licensee to integrate with GAMSTOP from 31 March 2020. From that date, a UKGC licence is contingent on live participation in the register. An operator that opens an account for a GAMSTOP-registered player breaches its licence conditions and faces regulatory sanction.
Why the scheme exists
Before GAMSTOP, UK self-exclusion was operator-level only. If a player self-excluded at Bet365, that block did not carry to William Hill, and each brand had its own enrolment form. GAMSTOP provided a single point of enrolment that propagates to every UKGC-licensed operator simultaneously.
How LCCP enforces it
Under LCCP paragraph 3.5.5, remote licensees must reference the GAMSTOP database in real time at account opening and at each login attempt. The check is API-driven: the operator submits the applicant’s name, date of birth and postcode, and receives back an accept or reject response. A reject blocks the account creation and closes any linked open accounts within 24 hours.
The three exclusion windows compared
You pick one at signup. The window cannot be shortened later. All three periods share the same procedural fingerprint: no early exit, no automatic lift at expiry, and active removal required to end.
| Feature | Trial 6 months | Most common 1 year | Longest 5 years |
|---|---|---|---|
| Minimum lock-in | 6 months | 12 months | 60 months |
| Early exit available | No No, absolute | No No, absolute | No No, absolute |
| Automatic lift at expiry | No No, must request removal | No No, must request removal | No No, must request removal |
| Action required to end | Yes Sign in and request | Yes Sign in and request | Yes Sign in and request |
| Approximate share of registrants | roughly 25 percent | roughly 40 percent | roughly 35 percent |
How UKGC operators actually enforce GAMSTOP at signup
The technical chain from your name landing in the register to a UKGC operator's account-open form refusing to submit. This is what happens at the operator side, not the user side.
-
You submit account details at a UKGC operator
Any account-open form on a UKGC-licensed site collects the LCCP-required data package: full legal name, date of birth, address including postcode, and email. The operator will not proceed to the deposit step until this data passes an internal validation layer.
-
The operator submits a GAMSTOP query in real time
Behind the scenes, the operator’s account system pings the GAMSTOP API with the applicant’s name plus DOB plus postcode. This is a match-only query: it does not transmit any other data, and does not return details about the exclusion period or duration.
-
GAMSTOP returns accept, reject, or exception
The API returns one of three states. Accept means the applicant is not on the register and the operator proceeds. Reject means there is a match on the register. Exception is a data-quality issue (partial match, ambiguous DOB, or system unavailability) that triggers a manual review.
-
Reject blocks the account creation immediately
On a reject the account creation is aborted. The applicant sees a generic block message: something along the lines of we cannot open your account, please contact GamCare. The message intentionally does not disclose the specific reason, so a would-be circumventor cannot tell whether the block came from GAMSTOP, sanctions screening, or another AML check.
-
Existing accounts are closed within 24 hours
If the applicant has any pre-existing accounts at the operator, the reject also triggers a batch closure across those accounts. Balances are held pending withdrawal (using the last verified payment method), and any bonus balances are typically forfeited under standard bonus T&Cs. The closure runs on a nightly batch, so the practical window is usually 12 to 24 hours from the initial GAMSTOP flag.
-
The block persists at every UKGC operator simultaneously
Because the GAMSTOP API is queried at every UKGC operator’s account-open flow, the same reject fires everywhere at once. There is no need to close accounts operator-by-operator: the single GAMSTOP enrolment propagates across the licence base within the operator’s next database sync (usually minutes).
What GAMSTOP covers, and what it does not
The blocking scope is precise. Anything within it is walled off; anything outside it is untouched.
What GAMSTOP covers
Every UK Gambling Commission remote-gambling licensee, without exception. That includes online casinos, sportsbook operators, poker rooms, bingo sites, and online-lottery operators licensed under the Commission’s remote gambling code. Land-based betting shops and casinos are a separate register (SENSE for casinos, betting-shop self-exclusion is operator-level); GAMSTOP does not touch land-based play.
What GAMSTOP does not cover
Everything outside the UKGC licence base. Offshore-licensed casinos (Curacao, Anjouan, MGA, Kahnawake, Isle of Man, Gibraltar) sit outside the register entirely, do not query it, and are not required to. Non-gambling apps that touch money (Steam skins trading, in-game gambling mechanics, gray-market prediction markets) are also outside the scheme.
What GAMSTOP cannot block regardless
The register is name-based. It blocks by legal identity, not device or IP or payment method. If a registrant has legitimate access to another person’s account (a family member’s, a business partner’s), GAMSTOP has no view of that. This is the largest structural limitation of the scheme and one it explicitly acknowledges.
GAMSTOP vs operator SE, device blockers, and bank blocks
GAMSTOP is one layer among several the UK self-exclusion landscape offers. Operator-side self-exclusion at individual brands, third-party device-level blockers, browser plugins, and bank-issuer gambling blocks all exist as independent tools. Each has its own scope, enrolment path, and lift mechanism.
Operator-side self-exclusion pre-dates GAMSTOP and still runs alongside it. A permanent self-exclusion set at a single UKGC brand persists at that brand regardless of GAMSTOP status. Device blockers (Gamban, Betfilter, BlockerX) work at the device or browser level: they intercept traffic to a hardcoded list of gambling domains and are lifted through the software itself, not through GAMSTOP. Bank-issuer blocks operate at the payment layer: your bank refuses to process any card charge from a merchant classified as gambling, regardless of whether you are on GAMSTOP or which operator is doing the charge.
Layered use is the pattern most self-excluding UK players end up with: GAMSTOP plus a device blocker plus a bank block. The three cover different attack surfaces and cannot easily substitute for each other.
Blocking tools compared: scope, lift path, cross-effect
| GAMSTOP | Name-based register across every UKGC licensee. Enrolled online, minimum 6mo/1yr/5yr, no early exit. Lift path: active request after minimum period + 24h cooling-off. |
|---|---|
| Operator-side self-exclusion | Per-brand block, set inside the operator’s own account settings. Duration operator-defined (often permanent). Lift path: contact operator support, some brands refuse to lift permanent SE ever. |
| Gamban (device blocker) | Software installed per device, blocks a hardcoded gambling-domain list at the OS level. Subscription-based, monthly or annual. Lift path: cancel the subscription and remove the software. |
| Betfilter / BlockerX (browser blockers) | Browser-level extensions blocking gambling domains on request. Free at basic tier, paid options for network-wide coverage. Lift path: uninstall the extension. |
| Bank-issuer gambling block | Merchant-category-code filter at the card issuer. Blocks any transaction to a gambling-classified merchant regardless of GAMSTOP status. Set in the banking app. Lift path: toggle in-app, some issuers apply a 48h cooling-off before the toggle takes effect. |
How the register actually blocks in real time
The technical detail behind the register is worth understanding, because it explains why circumvention attempts at UKGC operators do not work. The GAMSTOP integration is not a batch overnight process. It runs in real time on every account-open attempt, every login, and every session resume, and the API is under LCCP audit.
The database sync
Each UKGC licensee integrates a GAMSTOP API client on its account server. Every account-open form call, every login validation, and every reactivation attempt runs a query against the shared database. The database itself is refreshed within minutes of a new registration, so a same-day GAMSTOP signup blocks new account openings at every licensee before the day is out.
What operators see and what they do not
The operator receives a binary accept or reject plus an optional exception state. They do not see the exclusion period, the enrolment date, or any other identifying data. This is deliberate under UK data-protection law: only the minimum data required to enforce the block is shared.
Audit and licence exposure
UKGC licensees are periodically audited on GAMSTOP compliance. Regulatory reviews sample account-open logs to verify the API is queried at every account creation and that reject responses lead to a completed block within the 24-hour window. Non-compliance is a licence-conditions breach and has resulted in six-figure regulatory fines against UK operators.
How effective the register is in practice
GAMSTOP publishes registration and coverage figures in its annual reports. The trajectory is upward and the demographics tell a specific story about where the scheme lands and where it does not.
Registrations over time
By the end of 2025, more than 562,000 individuals had enrolled in the register since the 2018 launch. Enrolment volume trended sharply upward after the March 2020 mandatory-participation date, and again after affordability-check mandates in 2024. New enrolments now run at approximately 100,000 per year and rising.
Demographic profile
Enrolment skews male (roughly 75 percent) and slots between ages 25 and 44 in the majority of cases. The most common exclusion window chosen is 1 year, followed by 5 years, with 6 months trailing. These proportions are stable across the last three annual reports.
Where the scheme lands and where it does not
Where it lands: it is a hard block against opening any new UKGC account by name. Registrants who commit to the register at UKGC operators find that route effectively closed for the duration of their exclusion. Where it does not land: it has no effect on offshore access, no effect on friend-account use, and no view of device or IP-based circumvention attempts. It blocks by identity at the licence layer, and does nothing outside that layer.
Where UK players go while GAMSTOP still runs
The register was scoped to UKGC-licensed remote gambling, which is a smaller universe than the gambling market a UK resident can actually reach. Offshore operators licensed outside the UK operate independently of the register and are the route UK players most commonly take while GAMSTOP still runs their block.
The most active offshore licensing bodies for UK-facing play are Curacao GCB (which underwent a major regulatory framework overhaul in 2024), Anjouan (the newer entrant, growing quickly since 2023), the Malta Gaming Authority (higher-tier but rarer for pure UK-facing operations), Kahnawake (older, established framework), and Isle of Man GSC (top-tier but often dual-licensed with UKGC). Each has its own dispute-resolution mechanism, KYC requirements at cashout, and player-protection standards.
For a curated shortlist of offshore casinos accepting UK players right now, see our ranked non-GamStop casino list, which is the site’s ongoing tracking.
What happens after your minimum period expires
The register does not lift by itself when your minimum period ends. It is opt-out at expiry: you sign in, request removal, verify identity, wait through a 24-hour cooling-off, and the block then lifts across every UKGC operator on the same day. If you never request removal, the exclusion persists indefinitely.
The removal procedure end to end is 24 hours cooling-off plus roughly 48 hours for UK operators to process the notification. During that window your old UKGC accounts move back into a reactivatable state, though you have to sign back in and complete any operator-specific KYC refresh. Legal position for UK players and tax on winnings both remain unchanged whether you cancel GAMSTOP or not (see our take on whether non-GamStop casinos are legal for UK residents).
GAMSTOP FAQ
The National Online Self-Exclusion Scheme Ltd, a nonprofit company limited by guarantee based in London. It is funded by the gambling industry itself (UKGC licensees pay into it) but operates at arm’s length from the Gambling Commission as regulator.
31 March 2020. Before that date, participation was voluntary and coverage across UKGC licensees was uneven. From 31 March 2020 onward, every remote-gambling licensee has been required to integrate with the register as a condition of holding its UKGC licence.
No. GAMSTOP covers UKGC-licensed remote gambling only. Land-based casinos use SENSE, a separate industry self-exclusion register. Land-based betting shops still run operator-level self-exclusion tools individually.
No. Enrolment is all-or-nothing. Once you register, every UKGC-licensed remote-gambling operator receives the block. There is no way to allow specific brands while blocking others.
No. GAMSTOP only holds the personal details you registered with (name, DOB, address, email). Operators query the register with a match check and receive a binary accept or reject response. Play history and balances stay with each individual operator.
No. GAMSTOP is not a credit reference agency. Registration, enrolment, cancellation and any other interaction with the register are not shared with Experian, Equifax, TransUnion, or any UK credit bureau. There is no credit-file effect from being on the register.
No. Enrolment requires the account holder to verify their own identity. Third-party enrolment is not accepted, and any attempt to register another person is void. For household-level protection UK players commonly layer a device blocker or bank block on top of GAMSTOP.
GamCare is a support charity offering counselling, treatment referrals and self-help resources for problem gambling. GAMSTOP is a technical blocking register. GamCare provides guidance and helps people access support; GAMSTOP enforces the account-opening block itself. They work together but are separate organisations with separate remits.
No. GAMSTOP covers UKGC-licensed operators only. Cryptocurrency casinos overwhelmingly operate under offshore licences (Curacao, Anjouan, MGA, Kahnawake) and sit entirely outside the register. See our crypto non-GamStop guide for how the offshore crypto route works.
That is a licence breach for the operator, not for you. You are entitled to a full refund of any deposits made while the account was open in breach of the register, and the operator faces regulatory sanction from the UK Gambling Commission. Report the incident to GAMSTOP directly and to the Commission.
Yes. Offshore operators are not part of the register and are not required to query it. UK players commonly use offshore casinos while their GAMSTOP exclusion runs. Neither the offshore operator nor the player faces any UK legal exposure for this: the UK Gambling Act 2005 licenses operators, not players.
24 hours for the mandatory cooling-off, plus roughly 48 hours for UK operators to process GAMSTOP’s notification. Total from removal request to full unlock at UKGC operators is typically 24 to 72 hours.
Yes for UKGC-licensed remote operators, which cover players across all four nations of the UK. Northern Ireland’s separate land-based gambling regulatory framework does not touch remote gambling; that stays under the UK Gambling Commission and GAMSTOP applies uniformly.