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).
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.
Customers must be able to choose whether to accept price fluctuations that occur after their bet is requested
From the 1 April 2018 the remote technical standards (see RTS 2C) have required that operator’s systems enable customers to choose whether to accept price fluctuations (in either direction) that occur after their bet is requested.
Providing consumers with greater control and consistency
This requirement applies to both fixed odds betting and betting exchanges. It was introduced because we were aware of concerns that bets were sometimes subject to price fluctuations caused by time delays and market movements. Consumers were not always aware that event odds may be subject to price fluctuation and the way in which licensees handled fluctuations differed.
Players should be presented with options to control whether a price change should be accepted or not.
These options must be presented on a per bet basis, except in circumstances where a customer has requested a default account setting to disable price change alerts prior to bet acceptance. Where the functionality is offered at an account level the default option should not be set to accept all fluctuations.
Where a customer chooses not to accept price changes automatically any bet where the price changes must be reoffered before it is accepted.Information sufficient to explain the options to the customers should be provided.
An optimum solution would enable consumers to choose to automatically accept price movements within a particular margin range. Account level options offered to consumer could include accepting all bets with higher price, accepting all bets with shorter price or accepting all bets regardless of price movements.
This requirement does not intend to capture currency fluctuations.
Remote betting operators must ensure that their systems are compliant with the above requirements.
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.