UK iGaming · RTS 12B readiness

Deposit-limit changes take effect 30 September 2026.

A source-linked implementation checklist for UK Gambling Commission RTS 12B. Use it to turn the upcoming requirements into product QA evidence without treating automated observations as legal certification.

Effective: 30 September 2026Official wording last updated: 22 May 2026Applies broadly to remote gambling; check licence scope

What changes in RTS 12B

Gross deposit limits must be offered.
As a minimum, the gambling system must offer a limit on the gross amount a customer deposits over a defined duration.
Only gross deposit limits can be called “deposit limits”.
If a limit meets that definition, it must be described to the customer as a deposit limit.
Gross deposit limits need at least equal prominence.
Where several financial-limit types are offered, the gross deposit limit must not be hidden or presented less prominently.
Required durations include 24 hours, 7 days and one month.
UKGC clarified that gross deposit limits must use fixed time frames; other limit types may use fixed or rolling periods.
The most restrictive simultaneous limit must apply.
For example, overlapping daily and weekly deposit limits must constrain deposits according to whichever applicable limit is tighter.
Further depositing must stop once a deposit limit is reached.
The block remains until the defined period restarts or the customer increases the limit, subject to the standard 24-hour cooling-off requirement.

30 September evidence checklist: what can be proved where

For the six controls in this rule pack that take effect on 30 September 2026, Lexsentra currently has 2 validated partial browser observations. RTS12-004 / 005 / 006 / 007 stay explicitly bounded to controlled journeys and/or human review rather than being marketed as automated compliance checks.

Controlled journey + human reviewRTS12-004 · Gross terminology and reached-limit enforcement.
Capture the customer-facing “deposit limit” terminology, then use an explicitly authorized account state to verify that the underlying limit is gross and that further deposits are blocked at the threshold. A visible label alone is not proof of calculation or enforcement.
Semantic / journey evidenceRTS12-005 · Fixed timeframe mechanics.
Evidence must establish that the gross deposit limit itself operates on a fixed timeframe. Merely seeing a duration label does not establish how the period resets or is calculated.
Human comparison requiredRTS12-006 · At least equal prominence.
Preserve the full limit-selection state so a reviewer can compare placement, visibility and presentation of gross deposit limits against other financial-limit types. Lexsentra does not reduce prominence to a single automated legal score.
Authorized stateful journeyRTS12-007 · Most restrictive simultaneous limit.
Requires a controlled account with overlapping limits and safe stateful testing. Public-page browser evidence cannot prove which limit the gambling system ultimately enforces.
Validated partial browser observationRTS12-013 · Required durations.
When the limit-setting interface is actually reached, Lexsentra can observe whether selectable controls for 24 hours, 7 days and one month are present. This does not prove downstream enforcement after selection.
Validated partial browser observationRTS12-014 · Deposit-limit option offered.
Lexsentra can preserve evidence that a selectable deposit-limit option is visible. The observation remains partial because the browser label does not prove that the underlying calculation is genuinely gross.

How to use this checklist: treat each row as an evidence question for release QA. Record what was observed, what required an authorized journey, what remained inconclusive, and who reviewed the result. “Validated” describes a tested evidence observation, not a legal conclusion.

Final pre-effective-date release QA sequence

Use the remaining pre-30 September window to close evidence gaps in a controlled order rather than treating one public scan as a compliance verdict.

1 · Freeze source/versionConfirm the current RTS 12 wording your release is being tested against.
Use the UKGC version updated 22 May 2026 and record the source/version with the release evidence so an older saved annex cannot silently drive QA.
2 · Public / reachable UICapture what can be observed without changing customer state.
Check that financial-limit facilities are reachable from the relevant surface and preserve visible evidence for deposit-limit availability plus selectable 24-hour, 7-day and one-month durations where the limit-setting interface is reached.
3 · Authorized test accountUse a dedicated controlled journey for semantics and enforcement.
Verify gross-limit terminology/calculation, fixed-timeframe mechanics, simultaneous-limit behavior and threshold enforcement only with explicit authorization and a safe test state. Do not infer these from labels alone.
4 · Reviewer sign-offSeparate observed, partial, inconclusive and reviewed conclusions.
Preserve screenshots/technical evidence, record what remained unobservable, and attach a human review decision rather than converting uncertainty into a pass/fail claim.
5 · Post-release baselineKeep the verified surface under monitoring after deployment.
Use the approved release evidence as a baseline so later UI or behavior changes become regression questions instead of a fresh one-off audit.

Fastest bounded pilot: one UK surface + one RTS 12B control family + one access boundary + one release/regression question. No real-money action is required for the public first step.

What Lexsentra can evidence now

Available nowVersioned regulatory context

Lexsentra has a UK RTS 12 rule pack and readiness countdown so teams can trace product observations back to versioned controls and official sources.

Available nowObservable digital-surface evidence

Browser QA can preserve timestamped screenshots, redacted network evidence and visible product-state observations on public or authorized surfaces, then compare later runs for regressions.

Available nowHuman review trail

Material changes can be reviewed as confirmed, false positive, accepted risk or needs review, with reviewer notes and timestamps.

What still needs controlled access

Authorized journey requiredLimit calculation and enforcement

Proving that deposits are blocked at the correct threshold, that gross calculations remain correct, and that simultaneous limits enforce the most restrictive result requires a controlled authenticated account and transaction state.

Human/legal review remainsCompliance determination

Lexsentra can automate QA observations and preserve evidence, but it does not certify an operator as compliant, replace legal advice or replace an accredited test house where one is required.

Paid-beta design targetRTS 12 journey pack

The high-value next step is an authorized test-account workflow for registration, financial-limit setup, cooling-off and boundary testing. It should be enabled only where the operator explicitly authorizes those journeys.

Two implementation questions teams keep asking

Can an operator still offer a net deposit limit?

Yes. UKGC implementation guidance allows net deposit limits as an additional financial-limit type. The important naming boundary is that only a limit meeting the gross-deposit definition can be called a “deposit limit”; gross deposit limits must still be offered as the required minimum. Official UKGC wording ↗

Must every existing customer be moved back to a gross deposit limit on 30 September?

No blanket forced migration is stated. UKGC says it does not expect existing customers to be changed back to using gross deposit limits on the implementation date. Gross deposit limits and any other offered financial-limit types must be available from 30 September 2026, including at the relevant prompted review points. Official UKGC implementation context ↗

Turn the deadline into repeatable evidence.

Start with a free public-page check, move into workspace evidence and monitoring, or book a 30-minute Regulatory QA Pilot for a bounded RTS 12 review on your own surface.

Run free public-page check Create workspace Book 30-minute pilot