Web app or native app: what the rules make a licensee show you
1 of the Gambling Commission's Licence Conditions and Codes of Practice, a remote licensee must obtain and verify a customer's identity before permitting that person to gamble. The data collected is specific: name, address, and date of birth. The condition also specifies that age verification must occur before a customer is permitted to make a deposit.
On this page — contents
These legal demands bind the operating business rather than the software platform hosting the code. The Commission issues licences to corporate entities, not to browser sessions or application packages. Regulators write conditions for the licensee, attaching statutory obligations directly to the gambling transaction rather than the digital wrapper that renders the visual interface.
When an operator develops its technical infrastructure, regulatory duties attach to the central player account. A user authenticating through a standard browser session enters the same verified account register that opens inside an installed mobile package. The underlying ledger does not change. If identity verification under licence condition 17.1.1 is incomplete, the operator cannot permit gambling on either shell.
The technical difference between a web browser view and an installed native app is a distribution detail. The Gambling Commission assesses the transaction, the verified status of the user, and the legal obligations of the licence holder. Every condition enforced on remote gambling applies to both delivery methods equally.
Every screen from which you can gamble
The primary display requirement across all remote platforms rests in licence condition 8.1.1. Amended by the Gambling Commission with an effective date of , this condition governs how a licensee presents its regulatory credentials to the public.
Under licence condition 8.1.1, a remote licensee must display, on every screen from which a customer can access gambling facilities, three distinct items:
- A statement that it is regulated by the Gambling Commission
- Its account number
- A link to its licensed status on the Commission's website
The Commission's technical standards set the format and content for these elements, drawing on the regulator's consultation response on the display of licensed status.
The phrase "every screen from which a customer can access gambling facilities" establishes the visual baseline. An operator cannot omit licensing credentials on the grounds that a mobile screen is small or that an installed app interface uses a clean design. If an interface allows a user to launch a game or place a bet, the mandatory account number, regulatory statement, and register link must appear on that screen.
Once play begins, live session metrics take over the visual interface. Remote technical standard 2E requires the customer's net position to be displayed permanently on screen. Remote technical standard 13C requires that elapsed time must also remain permanently on screen throughout the session.
Both display rules came into force on for online slots sessions. On , the Gambling Commission extended the display of time and spend requirements to other online products. A customer opening a gambling session sees the running timer and the net spend tracker permanently on screen, whether the game engine runs within a web browser or inside a downloaded application.
The controls that must be one link away
Player control tools operate under uniform mandates across all technical shells. The remote technical standard 12 framework establishes requirements for financial limit tools, with updated provisions taking effect on .
Under remote technical standard 12C, financial limit-setting facilities must be provided via a link on the homepage and on deposit pages or screens. An operator cannot place limit options behind customer service queues or hide them inside account directories. The direct link must be visible on the deposit screen where the player commits funds.
The method of input is regulated with equal precision. Standard 12B requires that financial limits must only be offered using free text. Licensees cannot present pre-filled drop-down menus or suggest monetary thresholds. Standard 12B also dictates that financial limits must be applied at the account level. A limit established inside a browser session restricts spending across an installed app immediately, because the rule prohibits separating limits by device or channel.
The presentation of these controls is governed by standard 12E, which mandates that setting a financial limit must be presented as the default option when customers manage their limits. When a player chooses to lower an existing limit, standard 12D states that requests to decrease a financial limit must be actioned immediately.
Exclusions apply across both environments through corporate licensing rules. Social responsibility code provision 3.5.5 states: "Licensees must participate in the national multi-operator self-exclusion scheme." Because this code provision attaches directly to the operating licence, an exclusion registered through the national scheme shuts down account access across every browser session and native application tied to that licensee.
What the App Store adds and what it cannot remove
The structural differences between the two delivery shells stem from store distribution rules rather than the Gambling Commission's rulebook. To distribute software through Apple's platform, an operator must comply with Apple's App Review Guidelines in addition to domestic gambling law.
Apple's App Review Guideline 5.3.4 sets out three distinct distribution requirements: "Apps that offer real money gaming (e.g. sports betting, poker, casino games, horse racing) or lotteries must have necessary licensing and permissions in the locations where the app is used, must be geo-restricted to those locations, and must be free on the App Store."
Alongside geographic restrictions and zero-cost downloads, the platform holder restricts financial processing. Guideline 5.3.3 states: "Apps may not use in-app purchase to purchase credit or currency for use in conjunction with real money gaming of any kind."
Because Guideline 5.3.3 bars the use of Apple's in-app purchase mechanism for real money gaming credit, an installed app cannot route deposits through the store's billing system. Instead, the transaction passes through the licensee's own cashier interface. This restriction explains why the deposit screen on an installed app matches the deposit page on a standard website. The operator's direct cashier mechanism handles the funds in both cases, and remote technical standard 12C applies to that deposit view across both environments.
Store guidelines alter the delivery pipeline, geographic fencing, and payment mechanics for installed apps without overriding domestic regulations. The identity verification under licence condition 17.1.1, the permanent on-screen disclosures under standards 2E and 13C, and the default limit controls under standard 12 apply to the remote licensee across both delivery channels. Whether the interface renders in a web browser or loads from an application package, the display requirements follow the licence.
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.