Standards

Remote gambling and software technical standards (RTS)

Remote gambling and software technical standards under section 89 and section 97 of the Gambling Act 2005.

---

Published
2 February 2021

Last updated
1 February 2021 - Changes

Document actions
Print or save

Contents

• Remote gambling and software technical standards (RTS)

---

• 1 - Introduction
• 2 - Definition of terms
• 3 - Remote gambling and software technical standards
• - RTS 1 – Customer account information
• - RTS 2 – Displaying transactions
• - RTS 3 – Rules, game descriptions and the likelihood of winning
• - RTS 4 – Time-critical events
• - RTS 5 – Result determination
• - RTS 6 – Result determination for play-for-free games
• - RTS 7 – Generation of random outcomes
• - RTS 8 – Auto-play functionality
• - RTS 9 – Progressive jackpot systems
• - RTS 10 – Interrupted gambling
• - RTS 11 – Limiting collusion and cheating
• - RTS 12 – Financial limits
• - RTS 13 – Time requirements and reality checks
• - RTS 14 – Responsible product design
• - RTS 15 – In-play betting
• - RTS 16 – Use of third party software
• - RTS 17 – Live dealer studios
• 4 - Remote gambling and software technical standards (RTS) security requirements
• 5 - Annex

RTS 4 – Time-critical events

Applies to:

Gaming (including bingo), lotteries and betting on virtual events

RTS aim 4

To reduce the risk that customers are unfairly disadvantaged by technical factors that may affect speed of response, and to ensure customers are made aware of the risk.

RTS requirement 4A

Where speed of interaction has a significant effect on the customer’s chance of winning, operators must assess the level of risk and demonstrate to the Commission that they are taking reasonable steps to reduce the risk to customers.

RTS implementation guidance 4A

Examples of possible approaches include:

1. estimating the degree of network latency (delay) a customer is experiencing and displaying regularly updated information to the customer about any disadvantage that they may be operating under (for example high, medium, low)
2. applying a handicapping system based on estimated performance and/or system latency
3. treating winning responses that arrive within a period of time as simultaneous and implementing a policy on how simultaneous wins are to be dealt with.

RTS requirement 4B

For time-critical events, the customer should be informed that they might be at a disadvantage because of technical issues such as slower network speeds, or slower end user device performance.

RTS implementation guidance 4B

1. Information should be included in game descriptions, rules, ‘help’ or ‘how to play’ pages.

Previous section
RTS 3 – Rules, game descriptions and the likelihood of winning Next section
RTS 5 – Result determination

---

Last updated: 1 February 2021

Show updates to this content

No changes to show.