Remote gambling and software technical standards
Gambling software and remote operating licence holders (including ancillary remote betting) are required to comply with our remote technical standards (RTS) and requirements relating to the timing and procedures for testing.
LCCP: Licence condition 2.3.1
Remote gambling and software technical standards details the specific technical standards and the security requirements that licensed remote gambling operators and gambling software operators need to meet. It comprises:
- Technical standards
- Security requirements (which are a subset of the ISO/IEC 27001: 2013 standards).
We recently consulted on changes to the Remote gambling and software technical standards (RTS).
RTS amendment (October 2017)
RTS requirement 2C
- The published RTS required that gambling system must enable customers to choose whether to automatically accept price fluctuations (in either direction) that occur after their bet is requested.
- We recognise that the use of the word automatically could be interpreted to mean that we would expect licensees to put in place an account-wide solution that enables consumers to turn on/off notifications for price fluctuations. However, the aim of the requirement is to ensure that consumers are, by default, offered notifications that enable them to accept price fluctuations on a per bet basis, regardless of whether notifications can be controlled at an account level. We have therefore removed the word automatically from requirement 2C.
- Implementation guidance 2C(b) sets out how the requirement should be applied in the event that the functionality to accept notifications is offered at an account level.
Ancillary lottery licence holders
- We have corrected a typo in paragraph 1.11 to make it clear that the technical standards do not apply to holders of an ancillary lotteries licence.
RTS amendment (July 2017)
We have made the following minor amendments to implementation guidance in the Remote Technical Standards:
RTS requirement 1B
- The published RTS contained a formatting error in which information that was intended as guidance was published under RTS requirement 1B. This information, detailing what account and gambling history should include, has now been moved to RTS Implementation Guidance 1B.
- Under RTS implementation guidance 1B we have clarified that where transaction history spans over multiple pages, a summary total should be displayed at least on the first screen or page. This minor amendment reflects the original guidance detailed in the consultation response.
Linked progressive jackpots
- We have been asked to clarify whether RTS 9 applies to both linked and stand-alone progressive jackpots. We are unaware of circumstances in which a stand-alone online jackpot would offer a progressive feature without linking player contributions. To remove any further uncertainty, we have removed reference to ‘linked progressives’ and renamed RTS 9 progressive jackpot system.
The updated RTS includes a number of requirements that are due to come into effect on 1 October 2017 and 1 April 2018.
Requirements to come into force with immediate effect
We have also updated the RTS to reflect changes in the testing strategy and to formalise interim measures and guidance previously provided on the temporary blog regarding the introduction of the Gambling (Licensing & Advertising ) Act 2014. These updates will come into force with immediate effect and concern the following sections:
- Restricted display device (not a new requirement)
- Display of Commission licence status (formalising our interim position)
- Live RTP monitoring (came into force 1 September 2016 as part of testing strategy updates)
- Play-for-free games (requirement not altered, scope clarified)
- Reality checks (incorporating existing guidance already published).
Requirements that come into force 1 October 2017
The following sections contain new requirements that are due to come into effect 1 October 2017. The new provisions are highlighted in green text in the updated RTS:
- Live dealer studios (based on existing standards/practice and new requirement makes our position clear)
- Peer-to-peer poker
- Use of third party software
- Linked progressive jackpots
- Virtual sports odds
- Information security standards (security audits submitted after the implementation date will need to include the new requirements).
Requirements that come into force 1 April 2018
The following sections contain new requirements that are due to come into effect 1 April 2018. The new provisions are highlighted in blue text in the updated RTS.
- Display of transactions
- Gambling account history
- Display of net deposits
- Financial limits.
We have updated the supporting testing strategy to incorporate any new standards and changes made to the numbering of existing requirements as a result of this consultation. Other supporting documents will be updated in due course.
A copy of the updated RTS and testing strategy with changes tracked are available on request. Please email email@example.com to request a copy.