Is RTS 12 Only About Limits or Also About Where They Appear?

The UK Gambling Commission’s Regulatory Technical Standards 12 (RTS 12) has reshaped how operators build and present financial controls in their products. But is RTS 12 purely about setting financial limits, or does it extend to specifying *where and how* these limits surface in the user journey?

To answer this, we need to unpack not just the “limits” in RTS 12, but also the prominence and accessibility requirements it demands. This discussion is especially important as mobile-first UX has become the default approach in iGaming, deeply influencing how deposit and account screens are designed.

What is RTS 12 Financial Limits?

At its core, RTS 12 mandates that operators must offer customers financial controls such as deposit, loss, and stake limits. These are not just optional features but regulatory requirements designed to encourage safer gambling and reduce harm.

The regulation specifies three main elements:

• Financial limits: Minimum pre-set limits that operators must provide (e.g., daily, weekly, monthly deposit caps).
• Clearly available controls: Players must be able to easily find and adjust these limits without hassle.
• Prominence requirements: Limits must be placed “front and center” in user flows so customers can see and interact with them proactively.

Beyond Limits: The “Where” Matters as Much as the “What”

It’s tempting to think RTS 12 is just about the limits themselves — like having a £250 weekly deposit cap — but the standard also weighs heavily on where these controls appear and how visible they are to players.

The UKGC’s guidance is explicit: financial controls should not be buried deep in settings or obscure account menus. Instead, they should be integrated seamlessly into key customer touchpoints such as:

• The registration flow — offering limit-setting options upfront before customers wager real money.
• Deposit screens — the critical moment where players fund their accounts, making it essential the limits are easy to see and adjust.
• Account dashboards — where players can review, update, or remove their limits anytime.

Design teams must consider these placements carefully, not only from a compliance standpoint but also as a player experience issue. A limit that exists but is hard to find or understand is effectively “hidden,” which defeats the objective of empowering customers.

Registration Flow: Setting the Tone Early

The registration phase is often the first time customers engage deeply with an iGaming product. RTS 12 guidance suggests making financial controls visible and straightforward here serves two purposes:

1. Informed start: New players are prompted to think about their gambling behavior before they start depositing, making it less likely they will overspend unknowingly.
2. Legal compliance: Showing deposit limit options here satisfies the requirement of having limits “clearly available” before wagering starts.

In mobile-first design contexts, this means embedding limit controls within the registration screens — not as a separate link, but as part of the main UX flow. For example:

• A step in the signup wizard dedicated to deposit limits, with clear input fields or selectors, accompanied by brief explanatory text.
• Visual prominence that matches other critical fields like email, password, or payment details — no burying in “optional settings.”

Failing to do this risks players skipping these controls, resulting in poor compliance and missed opportunities to encourage responsible play early.

Deposit Screens: The Last Gatekeeper

The deposit screen is where customers actually commit money. Offering financial limits here is not just good practice — RTS 12 expects operators to place these controls in this critical moment, making limits “front and center.”

Key aspects to consider on deposit screens:

• Visibility: Deposit limits should be displayed prominently, either as a suggested default or a clearly accessible option alongside payment amount fields.
• Interaction: Players must be able to easily adjust their limits before confirming deposits without digging through menus.
• Mobile optimization: On small mobile screens, limit options should not be concealed behind confusing toggles or tabs. Instead, a clean, direct, and well-labeled interface is necessary.

Good examples embody placing a concise limit reminder above or below the deposit input box, combined with a short description of what the limits mean in plain language. This reassures players and prevents accidental overspending.

Account Areas: Control and Review Hubs

The account dashboard is a natural home for ongoing control and review of financial limits. RTS 12 requires limits to remain clearly available—not something you set once and forget about.

Best practice here includes:

• Dedicated sections listing current gross deposit limits, loss limits, and stake limits.
• Simple, in-context controls for adjusting or removing limits, along with cooldown periods or warnings per regulatory requirements.
• Clear labels and no ambiguous terminology that might confuse customers about their set limits.

Mobile-first demands mean these controls have to be easy to navigate on a phone or tablet, with tap-friendly buttons and minimal scroll/complexity.

RTS 12 Meets Mobile-First UX

Mobile-first UX is no longer optional for UK-facing operators; it’s standard. This shift brings unique challenges to embedding RTS 12 financial limits and controls.

For example, mobile screens require:

• Concise copy without losing clarity — limit explanations must be short but unambiguous.
• Minimal clicks to find and set limits — fewer screens or steps.
• Visual hierarchy that prioritizes financial controls like deposit limits over less crucial info.

Ignoring the “where” part of RTS 12 in the mobile context risks operators falling foul of compliance by making limits effectively invisible.

Sanity-Checking RTS 12 Against Actual User Interfaces

Real-world audits often reveal that “financial limits” exist in the https://www.offthemrkt.com/lifestyle/the-biggest-changes-shaping-online-gambling-in-2026 system but are tucked away in vaguely labeled settings, or accessible only through multiple taps. This is a compliance risk under RTS 12’s prominence rules.

For example:

Place in Product Common Issue RTS 12 Expectation Registration Flow Limits hidden in links labeled "Responsible Gambling” without context. Limits available inline during signup, no hidden steps. Deposit Screen Limits only in separate “Gambling Settings” pages requiring back-and-forth navigation. Limits shown and adjustable within deposit screen itself. Account Dashboard Controls buried under advanced menus or arcane labeling (“Limits & Restrictions”). Clearly signposted sections with easy adjustment options.

Operators must think like users. If the average player struggles to find or understand limits, then the implementation doesn’t meet the “clearly available controls” clause of RTS 12.

Conclusion: RTS 12 is About Both Limits and Placement

In summary, RTS 12 financial limits are not just numbers or caps — they are part of a wider design mandate that prioritizes transparency, accessibility, and player empowerment.

Operators need to embed limits prominently in:

• Registration flows, to set player expectations before wagering begins.
• Deposit screens, the critical point of financial commitment.
• Account areas, for ongoing control and review.

Mobile-first UX principles amplify the importance of clear, tap-friendly, and well-labeled controls. Simply “having limits” is insufficient — their visibility and usability are equally vital to meet RTS 12 and deliver a truly responsible gambling experience.

From a product design perspective, RTS 12’s influence ensures safer player journeys and means financial controls must be considered fundamental elements, woven directly into the user experience rather than afterthought features.