Deposit limits that follow you across devices
Remote technical standard 12B, enacted by the Gambling Commission, mandates that financial limits must be applied at the account level and offered exclusively through free text. If a customer opens a betting app on an iPhone, enters a restriction, and later logs into the same brand from a desktop browser, the restriction remains unchanged.
On this page — contents
The cap belongs to the remote customer account, not the software installed on a specific piece of hardware.
The rules took effect on . They resolve years of operational discrepancy where separate user interfaces could expose players to differing friction points. Under the remote technical standards, the central customer record holds the limit rule. A native mobile client on Android, an iPad app, a mobile browser, and a home workstation all communicate with the same core player ledger. Switching from an app to a laptop will never grant a fresh funding allowance.
The limit lives on the account, not on the app
Standard 12B settled the technical architecture required for all remote operating licence holders in Great Britain. Applying a limit at account level means an operator cannot isolate it to a single session, a single channel or a single device.
When a user logs in, the platform queries the player profile on the operator database. If that profile contains a restriction, the cashier module enforces it regardless of how the user reached the payment gateway. Installing the operator application onto a second phone will not clear the ledger. Deleting and reinstalling the app does not wipe the stored value.
Local device storage plays no role in calculating whether a payment clears. The operator server checks every incoming card transaction, bank transfer, or voucher against the active limit assigned to the account.
If a player attempts to fund an account via a mobile web browser after hitting a cap inside the operator iOS app, the cashier rejects the transaction instantly. The central database simply registers that the account-level ceiling has been reached for that window.
Free text, and what a list of preset amounts was hiding
Standard 12B also dictates how operators present limits during the input stage: financial limits must only be offered using free text.
Historically, drop-down menus and clickable tiles suggested arbitrary numbers to depositors. Regulators identified that preset choices anchored user expectations, steering people toward figures higher than they intended to set. A blank text field requires the user to type a deliberate number without numerical nudges from the interface.
This input standard works in tandem with two onboarding mandates introduced under standards 12A and 12E:
- Early intervention under Standard 12A: Operators must prompt all customers to set a financial limit as early as possible during the customer journey.
- Default-on positioning under Standard 12E: Setting a financial limit must be presented as the default option, requiring the customer to take positive action to opt out.
Opting out requires an explicit manual click. The registration architecture must present the tool active and open, rather than tucked behind a collapsed settings accordion.
By forcing free-text entry onto a screen that defaults to active, standard 12E prevents operators from pre-filling suggested deposit bands or defaulting the customer into an unconstrained state.
Down now, up later
Speed of enforcement depends entirely on the direction of the adjustment.
Under standard 12D, all customer requests to decrease a financial limit must be actioned immediately. If an account holder decides to lower an allowance, the platform cashier must write that lower threshold to the database instantly. The new ceiling binds the very next deposit attempt, even if that attempt occurs thirty seconds later on a different device.
Requests to increase a limit follow an entirely different path. Upward adjustments do not apply instantly, forcing a delay before additional funds can reach the player balance.
Accessibility of the controls is governed by standard 12C. Operators must provide financial limit-setting facilities via a link on the homepage and directly on deposit pages or deposit screens. A user preparing to add funds must see the pathway to the limit tools without navigating away from the cashier interface.
The updates to the remote technical standards also introduced a regular maintenance rhythm for customers. Operators must prompt customers to review their limits every six months. The interface re-engages the user with their chosen ceilings, forcing an active check on whether the previous restrictions remain appropriate.
What changes on
The Commission published a consultation response on the definition of deposit limits on , outlining rules that take effect on . The implementation period for this second phase was extended to give operators time to reconfigure cashier terminology and calculation engines.
The forthcoming framework introduces strict statutory definitions for player-facing tools.
From , only a limit meeting the definition set out in standard 12B may be described to a customer as a deposit limit. Conversely, any limit meeting that exact standard 12B definition must be described as a deposit limit.
Ambiguous marketing terms will be banned from the cashier.
The regulator introduced the term "net deposit limit" for any control calculated as the amount deposited into the account minus any withdrawals made for the period or duration of the limit applied.
If a player deposits funds, withdraws winnings, and deposits again, that calculation represents a net deposit limit, not a standard deposit limit.
Time frames face distinct operational parameters under the new rules. From , only gross deposit limits must be offered over fixed time frames.
Other limit types may use fixed or rolling time frames. A gross limit looks strictly at incoming cash without crediting any withdrawals back to the allowance, and it must reset on a fixed calendar schedule rather than a shifting rolling window.
Operators must present gross deposit limits with at least equal prominence to other financial limits. If a site displays net options or stake controls, the gross limit cannot be hidden beneath alternative links.
The same October 2025 response also eliminated the phrase "spend limits" from technical standards, replacing it formally with "stake limits" to ensure descriptions reflect actual wager volume rather than cash inflow.
The limit one operator cannot set for another
The account-level mandate under standard 12B stops at the boundary of the individual operating licence.
A limit set on one website does not transfer to a competing platform. If a player sets a cap at Operator A, logs out, and registers at Operator B, Operator B has no record of the first ceiling.
In its consultation response on customer-led tools, the Gambling Commission decided not to implement cross-operator deposit limits at this time.
The regulator said that cross-operator mechanisms would instead be kept under review.
Because no cross-operator system exists, each brand maintains an isolated data silo for standards 12A through 12E. Account-level protections govern every handset, laptop, and browser connected to that specific operator, but the ceiling remains entirely non-transferable across the wider market.
Written and maintained by the i-phonecasino.co.uk desk. Licence status comes from the UK Gambling Commission public register; bonus figures, wagering and withdrawal rules come from the operator’s own published terms on the day shown below. Where a number is not published, this site leaves the field out rather than estimating it.
Last checked . Spotted something out of date? Tell the desk.