Reality Checks, Session Limits and Time-Outs: UKGC, MGA and AGCO Rules

As of October 2026, the UKGC Remote Gambling and Software Technical Standards (RTS 13), LCCP social responsibility code provision 3.3.4, the MGA Player Protection Directive (Directive 2 of 2018, version 3, January 2023) and the AGCO Registrar’s Standards for Internet Gaming each regulate session controls differently. The UKGC prescribes the reality check mechanics and a time-out facility. The MGA mandates a pop-up alert for repetitive random-generator games but treats session limits as optional in the Directive itself. The AGCO text reviewed for this article sets no reality-check interval and instead constrains game design and limit mechanics. This annotation reads each provision in order, quotes the operative text, and says what a build team has to ship.

UKGC RTS 13: time display and the reality check

RTS 13 is the only technical standard of the three that specifies the reality check as a screen event. Its stated aim is short.

To provide customers with facilities to assist them to keep track of the time they spend gambling.

(UKGC, RTS aim 13)

The standard splits into three requirements with different scopes. RTS 13A applies to all remote gambling except telephone gambling. RTS 13B applies to remote gaming (including bingo but excluding peer to peer gaming), remote instant win lotteries and high frequency lotteries. RTS 13C applies to casino, excluding peer to peer poker. Remote betting licensees therefore carry only the 13A clock obligation, which applies where the gambling system uses full screen client applications that obscure the clock on the customer’s device, in which case the client application itself must display the time of day or the elapsed time.

RTS 13B contains the acknowledgement mechanic.

The customer must acknowledge the reality check for it to be removed from the screen.

(UKGC, RTS requirement 13B)

A timed overlay that dismisses itself fails this requirement, and the acknowledgement is a natural logging point. RTS 13C provides that “The elapsed time should be displayed for the duration of the gaming session”, which is drafted as “should”, not “must”. RTS 2E separately requires casino gaming sessions (excluding peer to peer poker) to display the customer’s net position since the session started.

Implementation guidance on frequency and defaults

The guidance to 13B governs how the customer sets the interval, and one sentence causes most design disputes.

Customers can be presented with a pre-set list time periods but these must have a reasonable and appropriate range from which to select and where a default time period is offered it must be set at the minimum

(UKGC, RTS implementation guidance 13B, paragraph 1)

The sentence does not define “the minimum”. The safer reading, which is analysis and not text, sets any pre-selected default at the shortest interval in the presented list. The guidance also says the reality check should continue to appear until the gaming session ends or the customer exits the account, and that where a customer plays several products at once the session began with the first product.

The guidance then addresses the two situations where a pop-up collides with a game round.

The reality check can be presented at the end of a game but a player cannot be permitted to commit further funds to a new game until they have acknowledged the reality check, unless it occurs mid-way through a multi-state game such as blackjack where a player would need to commit additional funds if they wanted to split or double down.

(UKGC, RTS implementation guidance 13B, paragraph 5)

The reality check must prevent a new game within an auto-play sequence from commencing until the player has acknowledged the reality check.

(UKGC, RTS implementation guidance 13B, paragraph 6)

Both sentences sit in guidance, and the second uses “must”. Licensees should build both as hard gates, since an unacknowledged check that still lets stakes through is the failure mode the text describes. The guidance also says the reality check should offer an exit from the session or account and a link to account history. The UKGC RTS page carries the note “RTS updates effective 30 October 2026 added” and was last updated on 30 September 2026, so builds should be checked against the current published annex.

LCCP SR code 3.3.4: the remote time-out facility

Time-outs sit in the LCCP social responsibility code, not the RTS, so they map to a different assurance workstream.

Licensees must offer a ‘time out’ facility for customers for the following durations: 1. 24 hours 2. one week 3. one month or 4. such other period as the customer may reasonably request, up to a maximum of 6 weeks.

(UKGC, LCCP social responsibility code provision 3.3.4, Remote time-out facility)

The provision applies to all remote licences except those the LCCP lists, among them ancillary remote betting, gaming machine technical, gambling software and host licences. Three fixed durations plus a customer-requested duration capped at six weeks means the interface needs a custom-duration input, not only a dropdown. The text retrieved says nothing about what a customer may do during a time-out, so the lock scope (wagering, deposits, marketing) is a policy decision the licensee must document and apply consistently.

Session controls sit alongside SR code 3.4.3, which requires remote customer interaction systems that embed the three elements of customer interaction: identify, act and evaluate. A reality check acknowledgement or a time-out request is behavioural data a licensee can feed into that process.

MGA Directive 2 of 2018: article 18A and the limits provision

The Player Protection Directive came into force on 1 August 2018 under article 7(2) of the Gaming Act (Cap. 583). Article 18A sets the alert obligation.

B2C licensees that offer their gaming service by remote means shall, with respect to repetitive games of chance played against the house, the outcome of which is determined by a random generator, offer players the ability to set an alert at certain intervals of time by means of a pop-up message.

(MGA, Player Protection Directive, article 18A(1), V3 January 2023)

On its wording the trigger is a game type (repetitive, house-banked, RNG-determined), not a licence category, which is narrower than the UKGC’s scope. The same article lets the licensee offer the player a way to exclude auto-play time from the interval calculation, and that exclusion must be actively opted into by the player. The Directive’s transitional provisions list article 18A(2) among the V3 obligations to be implemented within twelve months of 12 January 2023.

The MGA’s player-facing description of the tool gives the content of the pop-up.

Such alert will suspend play and acts as a reminder to stay in control. Information about the time spent playing, wagered amounts, and winnings/losses during the session are also provided and the player must confirm that the message has been read, before proceeding with gameplay.

(MGA, Safer Gambling player information page)

The MGA Compliance Audit Manual (August 2018, v1) converts that into test steps. Item 6.12.1 checks that the message shows the time spent so far and winnings and losses for the period, requires confirmation that the message has been read, and gives an option to end the session or return to the game. For auto-play exclusion the auditor must confirm the following.

check that such option is disabled by default and that the player is required to actively choose to enable it.

(MGA, Compliance Audit Manual, item 6.12.2)

Item 6.12.3 directs the auditor to test whether the reality check is shared between games of the same and different platforms, so separate timers for web and app are an audit finding risk. The manual predates version 3 of the Directive, and its test steps should be cross-checked against the current Directive text.

Session limits: optional in the Directive, tested in the audit

Sub-article (2) of the Directive’s limits provision says licensees “may” offer additional limits, including “Time or session limits, by means of which, the amount of time which a player spends playing is limited.” The mandatory limits are deposit or wagering limits, which licensees must ask players about after registration and before the first deposit. The audit manual nonetheless instructs the auditor to determine whether the licensee offers a “Gaming session limit” (item 6.11.1). The MGA’s FAQ lists time outs or short breaks of more than 24 hours and not more than 30 days among tools operators are strongly encouraged, not required, to offer. Omitting session limits is within the Directive text but invites an audit finding. Our guide to MGA system audit requirements covers how the evidence pack is assembled.

AGCO Registrar’s Standards: design controls, not a reality-check clock

The Registrar’s Standards for Internet Gaming came into force on 4 April 2022. As of October 2026, the standards text reviewed contains no reality-check interval or acknowledgement rule comparable to RTS 13B. iGaming Ontario’s player-facing guidance lists reality checks among the tools Ontario operators provide, so counsel should confirm with the AGCO whether any instrument outside the Standards, such as a registrant requirement or operator agreement term, sets a specification. What the Standards do regulate is the game behaviour that reality checks exist to interrupt.

Games shall not provide auto-play features for slots.

(AGCO, Registrar’s Standards for Internet Gaming, Standard 2.16, Requirement 2)

Standard 2.16 opens with the principle that game designs and features “shall help to prevent extended, continuous and impulsive play and facilitate low risk play behaviours”. Standard 2.18 sets a minimum of 2.5 seconds from game start until the next game cycle can commence and requires the player to release and depress the start button or take equivalent action. Standard 2.21 requires slots sessions to display net position in Canadian dollars. iGamingBusiness reported in August 2026 that the AGCO fined Booming Games (Malta) Limited CA$70,000 for auto-play in several slot titles, finding that it “failed to properly configure, test and monitor certain games before and after they launched in Ontario”. The AGCO said it detected the breach through proactive and targeted compliance efforts.

The limit mechanics are where the Standards are most specific.

Financial and time limit functions must be easy to find, reach and initiate or change at any time after the player has registered and opened an account.

(AGCO, Registrar’s Standards for Internet Gaming, limits standard preceding 2.24)

Where a gaming limit has been previously established by a player, a request by the player to relax or eliminate that limit shall only be implemented after a cooling-off period of at least 24 hours.

(AGCO, Registrar’s Standards for Internet Gaming, Standard 2.24)

The limits standard requires the durations offered to include 24 hours, 7 days and one month, and requires the lowest limit to apply where a player sets simultaneous periods. Standard 2.24 adds that gaming limits must be enforced by the gaming system, so a front-end-only check does not satisfy it. Requirement 1 of the same standard bars the operator from relaxing a limit without a player request, so a retention team lifting a limit after a complaint is in breach even once 24 hours has elapsed. Our comparison of AGCO and AGLC standards and the Ontario year three review cover the wider enforcement pattern.

Side-by-side specification

The table summarises the provisions quoted above as of October 2026. Cells marked “not specified” reflect the text reviewed, not a statement that no other instrument applies.

Control	UKGC	MGA	AGCO
Reality check mandate	RTS 13B: remote gaming, instant win and high frequency lotteries, excluding peer to peer	Directive 2, article 18A: repetitive RNG games against the house	Not specified in the Standards text reviewed
Customer acknowledgement	Required before the check leaves the screen	Player must confirm the message has been read	Not specified
Auto-play	Check must stop a new game in an auto-play sequence until acknowledged	Auto-play time exclusion only by active player opt-in, off by default	Banned for slots (Standard 2.16)
Time-out or break	Mandatory: 24 hours, one week, one month, or customer-requested up to 6 weeks (LCCP 3.3.4)	Encouraged: more than 24 hours up to 30 days (MGA FAQ)	Not specified in the Standards text reviewed
Session or time limit	Time displayed during session (RTS 13A, 13C)	Optional under the Directive, checked in audit manual 6.11.1	Time-based limit durations offered must include 24 hours, 7 days, one month
Limit relaxation	24-hour cooling-off on financial limit increases (RTS 12B)	Not specified in the text reviewed	24-hour cooling-off (Standard 2.24)

Build and evidence implications

This annotation rests on a clause-by-clause reading of the RTS, LCCP, Directive 2 of 2018, the MGA Compliance Audit Manual and the Registrar’s Standards, with enforcement context from trade press. The conclusions below are analysis and go beyond the quoted text.

A multi-jurisdiction platform should hold a single session start timestamp across products, because the RTS guidance anchors the session to the first product played and the MGA manual tests cross-platform sharing. The reality check should be a blocking state in the game-round state machine, not a front-end overlay, so that stake commitment and auto-play progression both depend on the acknowledgement flag. Auto-play should be a per-jurisdiction capability flag, off for Ontario slots, gated by the reality check for UK licensees, and opt-in for any MGA time exclusion.

The text reviewed prescribes no log schema for reality-check events in any of the three regimes. Spillemyndigheden’s inspection standard SCP.02.03 (version 2.0) shows what a prescriptive regulator asks for, since it requires session records covering start and end times, amounts staked, won, deposited and withdrawn, the time of last confirmation of the session and the reason the session ended. Records of the interval chosen, time displayed, time acknowledged and the player’s next action would answer UKGC, MGA and AGCO evidence requests alike. Licensees should take qualified legal advice on how each regulator applies these provisions to their licence, product mix and platform architecture.

Key Resources

The UKGC Remote gambling and software technical standards page on gamblingcommission.gov.uk carries RTS 13 and the implementation guidance, and the LCCP carries social responsibility code provisions 3.3.4 and 3.4.3. The MGA publishes Directive 2 of 2018 (Player Protection Directive, V3 January 2023), the Compliance Audit Manual (MGA/G/001) and its Safer Gambling player pages on mga.org.mt. The AGCO publishes the Registrar’s Standards for Internet Gaming at agco.ca/registrars-standards-internet-gaming, last updated 14 May 2026 on the page reviewed.