The sportsbook push notification ban is a design brief
Colorado banned sportsbook push notifications, the UKGC now dictates what a "deposit limit" may be called and how prominent it must be, and Massachusetts requires a specific reason in every limit notice. Regulators are writing UI specs – here's how to design a betting product that treats them as the brief.
Three regulators wrote interface specs this year, and none of them called it that. Colorado made it illegal for a sportsbook to send a push notification that solicits a bet. The UK Gambling Commission decided what a deposit-limit control must be called and how prominent it has to be. Massachusetts told operators exactly what a "you've been limited" message must contain. If you design betting products, compliance is no longer the team that reviews your mockup at the end – the regulation is the mockup.
Colorado banned the channel, not the product
Colorado's SB 26-131, titled "Sports Betting Protections", was signed on June 1, 2026 and took effect on August 12, 2026, as BetColorado reported that month. According to the bill text on the Colorado General Assembly's site, operators may no longer initiate "mobile device push notifications or text messages to account holders in the state soliciting bets or deposits." The same law caps a customer at six separate deposits in a gaming day, bans credit card deposits outright, and lets the commission assess up to $25,000 against a violator.
The push ban is the part that touches design. In every sportsbook roadmap I've sat in, push was the retention engine: odds boosts at kickoff, "your parlay is one leg away", a deposit match on a quiet Tuesday. Colorado removed that lever for an entire state, and New Jersey is lining up behind it – Deadspin reported in March 2026 that Sen. Andrew Zwicker's S3401 would ban push and text messages encouraging wagering or depositing while the app is closed, at up to $500 per incident.
The design consequence is simple to state and hard to do: the product has to earn the open. That means bet tracking genuinely better than a scoreboard app, a personal ledger that shows the week honestly, and a home screen that answers "what's happening with my money right now" before it sells anything. Those are product design problems, not marketing problems.
The statute also separates solicitation from information – "your bet settled" is not "bet again" – and your notification taxonomy should already model that: transactional and promotional as separate component variants with separate policy flags, not one "push" bucket a growth manager fills on Friday afternoon.
The UKGC is naming your controls and sizing them
On May 26, 2026 the Gambling Commission pushed the second phase of its deposit-limit rules from June 30 to September 30, 2026, citing "further operator technical development time." From that date, per the Commission's own notice, UK operators must offer gross deposit limits – and in some cases re-introduce them, so some had quietly dropped them – must call them "deposit limits" with no other limit type allowed that name, and must present them "with at least equal prominence as other types of financial limit." Only gross deposit limits may run on both rolling and fixed time frames.
Read that as a designer and it is a component spec. Reserved label. Fixed hierarchy. One control type allowed a feature the others are not. Phase one, live since October 2025, already required prompting new customers to set financial limits and reminding them every six months, as iGaming Business reported in May 2026.
"Equal prominence" is the phrase to sit with. Prominence is exactly what gets negotiated away in design review: the safer control ends up two screens deep in settings while the deposit button glows on every surface. When I designed the responsible-gaming layer for a mobile casino, I put the deposit limit one tap from the wallet, made lowering it apply instantly, and made raising it wait 24 hours. Nobody made me. The UK is now making everyone do a version of it, and I'd bet the operators who needed a three-month extension are the ones whose limit was a label on a settings page rather than a component in a system.
Massachusetts turned a rejection letter into a content spec
On February 26, 2026 the Massachusetts Gaming Commission voted 5–0 to require sportsbooks to notify a customer within 48 hours of limiting their account, effective June 1, 2026. Sports Betting Dime reported that the notice must include "a specific explanation for the attachment of the limit(s), and identification as to which market(s) are so limited." Boilerplate "business decision" language is out. Customers limited before June 1 get a notice retroactively, and a limit that follows a customer in from another state triggers one too.
Commissioner Eileen O'Brien put the test plainly: "Does the patron understand what act or omission on their part triggered the limiting? If it doesn't answer that, you have a problem." That is a usability heuristic, spoken by a regulator, with the force of law.
So the limit notice is a designed artifact with required fields: trigger, scope by market, date, what remains available. Build it as a limits page inside the account that shows the current state per market, with the notice as a pointer to it. If the state has to be explained, it has to live somewhere the customer can find it a week later.
Read the rulebook as the brief
Put the rules where the design lives:
- A jurisdiction policy on the notification component – channel, category, state – so Colorado's rule is a config value, not a memo.
- A reserved-terms registry per market, so "deposit limit" means gross deposits in the UK and nothing else can borrow the word.
- Prominence as a token: every financial limit shares one component and one slot in the wallet.
- Notice templates with mandatory fields, versioned per regulator, rendered in-app as well as by email.
This is the operating layer of iGaming design now. Colorado, the UK and Massachusetts reached the same conclusion from three directions: the interface is where the harm happens, so the interface is what gets regulated.
A push notification was always a confession that the product couldn't get the open on its own. Colorado just made the confession illegal.
Sources
- Colorado General Assembly – SB26-131: Sports Betting Protections (June 2026)
- BetColorado – Colorado's New Sports Betting Protections Take Effect (August 2026)
- Deadspin – New Jersey Advances Bid To Ban Mobile Gambling Notifications (March 2026)
- Gambling Commission – Implementation extension for new deposit limit requirements (May 2026)
- iGaming Business – Gambling Commission extends deadline for deposit-limit rule changes (May 2026)
- Sports Betting Dime – Massachusetts To Require Detailed Sports Betting Limitation Notices by June 1 (February 2026)