GLI-33 - Gaming Laboratories International Event Wagering Systems
Chapter 2: System requirements (clock, control program, wagering and player account management, wagering instruments, location, information to be maintained, reporting) – GLI-33 - Gaming Laboratories International Event Wagering Systems

GLI-33 - Gaming Laboratories International Event Wagering Systems 2.5.5: Limitations and Exclusions

What does 2.5.5 require?

The system correctly implements every limitation and exclusion set by the player or the operator as the regulatory body requires: where limitations and exclusions are managed directly, the Limitations and Exclusions sections of Appendix A are evaluated; a player's self-imposed limitations never override more restrictive operator limits, the more restrictive taking priority; and internal status events, for example self-exclusion orders and their revocation, do not weaken the limitations.

Maintained by Gerard BlokdykControl text last updated

What else in your programme already covers this

This control maps to 1 controls across 1 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

  • RTS 12 Offer financial limits by default and apply increases only after 24 hours

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

Other controls in Chapter 2: System requirements (clock, control program, wagering and player account management, wagering instruments, location, information to be maintained, reporting) – GLI-33 - Gaming Laboratories International Event Wagering Systems

Query this from an agent

The graph holds this control, the 1 it maps to, and the evidence behind each claim, over MCP and REST.