Five Logins After GAMSTOP: Where the Block Held and Where It Slipped

Registering with GAMSTOP is one of the few genuinely quick things in gambling admin. Name, date of birth, address, email, a few clicks, and you are on the scheme. The bit that takes longer is working out whether every casino you have ever opened actually respects it.

The scheme is only as good as the operators applying it, and operators apply it in wildly different ways. So I spent a fortnight doing something slightly awkward: signing up to GAMSTOP, then testing five UK-licensed brands I had previously used or could easily register with, recording exactly what happened at login, at deposit, and in my inbox.

What the block is supposed to do

GAMSTOP is a free, single self-exclusion service for people living in Great Britain. Once your registration is active and verified, every operator holding a Gambling Commission licence is expected to check the register before letting you gamble. That includes before you open a new account, before you make a deposit, and in many cases at the point of login.

The exclusion lasts a minimum of six months. Taking it off is not instant — you have to request removal and confirm it, and there is a delay before it clears. That delay is a feature, not a bug.

What GAMSTOP does not do is wipe your accounts, cancel your saved cards or magically stop emails from a brand you signed up to years ago. It also does not cover operators licensed outside Great Britain, unlicensed sites, or anything you find through a link that does not end in a UK-licensed domain. Those are the edges where people get caught out.

The setup: five brands, one weekend

I picked five: two big-name sportsbooks with casino tabs, two slots-heavy casinos, and one smaller brand I had not used before. Before registering, I wrote down what existed already — three active accounts, one app installed on my phone, two saved debit cards, and one throwaway email address I had used for a sign-up roughly three years earlier.

Then I registered with GAMSTOP on a wet Tuesday evening with a cup of tea going cold next to the laptop, and waited for the confirmation email to land. It arrived in about four minutes. That email is worth keeping — it is your proof of the date the block started.

Login one through five

Brand A — the block landed immediately. A message on the login screen, and the deposit button turned grey. No drama, no ambiguity.

Brand B — I could log in to my existing account, but the deposit page showed a clear self-exclusion notice and refused the transaction. This is the correct behaviour: you can still see your balance and request a withdrawal, but you cannot put more money in.

Brand C — this is the one that made me sit up. No message at login. I got all the way to the deposit page and entered an amount, and only at the final confirmation step did it fail with a generic error. Nothing told me why. Anyone less determined might have assumed a card problem and tried again with a different method.

Brand D — a new registration was blocked at the form itself, before I could even set a password. Clean and obvious.

Brand E — nothing visible at login at all, and the deposit failed silently. Support later confirmed a GAMSTOP match had been applied. Good outcome, poor communication.

Gap one: the app you forgot about

An app already installed on your phone does not always refresh its status the moment the block goes live. Two of the five brands still showed me a logged-in home screen in their apps for a short period, though deposits were refused when I actually tried. If you want a clean slate, log out and back in, or reinstall the app. A stale cached session can look like a working account when it is not.

Gap two: the inbox that keeps filling

Marketing emails from two brands carried on for several days after the block was confirmed. Not a huge surprise — mailing lists are slow machines — but it matters if your reason for excluding was to stop the nudges. Use the unsubscribe link, and note the date you did it. If the emails keep coming after that, you have something concrete to complain about.

Gap three: the other email address

This was the real hole. GAMSTOP matches you on personal details, not on a list of every email address you have ever used. My throwaway-email account at one brand was caught at deposit stage only because the postcode matched. Had the address, surname spelling or date format differed slightly, the match could easily have failed.

If you have signed up to casinos over the years with different email addresses, nicknames or old addresses, do not assume one registration covers all of them. Log in to each old account you can remember and check for yourself.

Gap four: saved cards and one-click deposits

Stored payment details are convenient right up until they are not. Every brand I tested blocked the deposit itself, even where the card was saved. But I would still check it yourself rather than trusting a lobby screen: go as far as the deposit confirmation page, without completing a transaction, and see what happens.

How to verify without leaning on one support chat

A single chat agent can only tell you what their screen says. Build your own picture instead:

• Keep the GAMSTOP confirmation email and note the exact date the block began.
• Test each known account with a login, and look at the deposit page, not just the homepage.
• Check any installed apps as well as the browser.
• Search your inbox for each brand name and log what still arrives.
• If a site acts strangely, screenshot it with the date visible.
• Report operators that appear to ignore the block to GAMSTOP and, if needed, to the Gambling Commission.

What to take from all this

GAMSTOP does the job it advertises, most of the time, at most brands. But the experience is uneven: some sites tell you clearly what is happening, and some let you walk to the edge of a deposit before pulling the rug. Treat your first fortnight after registering as a test, not a formality. One registration is a solid start — it is not a fence around everything you have ever signed up to.