Does self-exclusion cover prediction markets?
Short answer: mostly no — and the reason is structural rather than an oversight anyone is about to fix. This page sets out which protections reach these platforms, which don't, and what that leaves you.
Why the gap exists
Gambling protections in the US are built on licensing. A state gaming regulator issues a licence, and the conditions of that licence are how obligations get imposed — honouring the self-exclusion register, offering deposit limits, displaying responsible gambling messaging. The register works because a regulator can take a licence away.
Prediction markets are structured differently. They list event contracts and are overseen federally as derivatives markets, not licensed by state gaming boards. No state licence means no state licence conditions, and the enforcement mechanism that makes self-exclusion function simply isn't attached to them.
This is contested rather than settled. Several state gaming regulators have argued that sports event contracts are gambling in substance and should be regulated as such, and the disagreement is moving through the federal courts. Whichever way that resolves, it does not change what is available to someone who needs a control today.
What reaches them, and what doesn't
| Protection | Covers it? | Why |
|---|---|---|
| State self-exclusion programs | No | Administered by state gaming regulators; bind the casinos and sportsbooks that state licenses. A federally regulated derivatives venue isn't among them. |
| GamStop (UK) | No | Covers operators licensed by the Great Britain Gambling Commission. Different regulator, different jurisdiction, no reach. |
| Bank gambling blocks | Usually not | Decline card authorisations coded 7995. Prediction market funding often codes as brokerage or quasi-cash instead, so the block never triggers. |
| Device blocking software | Partly | Depends entirely on whether the tool's blocklist includes these platforms, and on it being installed everywhere. Coverage of newer venues tends to lag. |
| Platform account controls | Varies | Whatever limits or closure the venue chooses to offer. A commercial feature rather than a statutory protection, and it can be reversed by the same person who set it. |
| A commitment device | Yes, for the money | Doesn't restrict any platform. Makes the balance itself unavailable for a period fixed in advance. |
Why the bank block usually misses
A bank-level gambling block is, mechanically, an instruction to decline card authorisations carrying merchant category code 7995 — betting and casino gambling. It is a good control where it applies, operating at the payment rail rather than the device, and banks that offer it often impose a deliberate delay before it can be switched back off.
It only ever sees what is coded 7995. Funding a prediction market account commonly routes as a brokerage transaction, or as a crypto or quasi-cash transfer, none of which carry that code. The block isn't failing — the transaction was never in its scope. That is also why asking your bank about “gambling blocks” in general tends to produce a misleadingly reassuring answer: the useful question is what it can decline for the specific funding route you actually used.
What that leaves
Three things, none sufficient alone, and the order matters:
- Support. A counsellor, a peer group, or the National Problem Gambling Helpline. No software below this line is a substitute for it.
- Access controls where they exist. Platform limits and account closure, plus device-level blocking with the password held by someone else. Both are reversible by you, which is their limitation.
- Control of the money. The layer that survives every workaround, because it doesn't depend on identifying a venue or a merchant code. If the balance isn't reachable, it doesn't matter which platform is.
The traditional version of that last layer is handing the surplus to someone you trust. It works, and its costs are that it makes another person the gatekeeper who has to refuse you, it earns nothing while it sits there, and it lasts only as long as the relationship does. Apsis does the same job with a contract that has no early-release function — and no capacity to be talked around at a bad moment.
Related questions
Does GamStop cover prediction markets?
No. GamStop applies to online gambling operators licensed by the Great Britain Gambling Commission. A platform offering event contracts under a different regulator, in a different country, is outside that scheme entirely — registering with GamStop has no effect on it.
Does a state self-exclusion list cover them?
Generally no. State programs are administered by state gaming regulators and bind the casinos and sportsbooks licensed by that state. A platform regulated federally as a derivatives market is not one of those licensees, so the list has no mechanism to reach it.
Will my bank's gambling block stop deposits?
Often not. Those blocks work by declining card authorisations carrying the gambling merchant category code, 7995. Funding a prediction market account frequently codes as brokerage or as a crypto or quasi-cash transaction instead, so a gambling block never sees it. Coding also varies by platform, funding method and processor, so the only reliable answer is the one your own bank gives you about your own recent transactions.
So what actually works?
Layers, none of which is sufficient alone: whatever limits or account closure the platform itself offers, device-level blocking with someone else holding the password, a conversation with your bank about the specific funding route rather than about gambling in general, real support through a counsellor or peer group, and putting the money you're not spending somewhere you can't reach on impulse.
The layer that doesn't depend on a merchant code.
Apsis is opening access soon. Join the waitlist and we'll email you when it's live.