Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/Rahat-Pagecode/gitbook-competitions/llms.txt

Use this file to discover all available pages before exploring further.

Spending Controls is a responsible gambling feature that puts customers in charge of their own purchasing behaviour. Customers can set personal spending limits or activate a temporary break directly from their account area. Once a limit is in place, the system automatically blocks any purchases that would exceed it — the limit cannot be bypassed or overridden by the customer once set.

How It Works for Customers

Logged-in customers can access Spending Controls from the My Account page. From there they can:
  • Set a spending limit — define a maximum amount they are allowed to spend within a given period
  • Take a break — temporarily suspend their ability to purchase tickets
Once a spending limit is set, customers cannot increase or remove it immediately. This is by design to protect customers from impulsive decisions. If a customer exceeds their limit, they will be blocked from purchasing tickets until the period resets.

Spend Report

The Spend Report in the admin backend gives operators full visibility of customer spending activity. It surfaces:
  • A log of the latest changes made by customers to their spending controls
  • A list of customers who have exceeded their self-imposed spending limits
Use the Spend Report proactively to identify customers who may be experiencing difficulty managing their spend, and to demonstrate compliance with responsible gambling obligations.

Settings & Frequency Rules

The Spending Controls settings page allows you to configure the behaviour of the system to suit your platform’s requirements. From here you can define:
  • Frequency rules — control how spending limits reset (for example, daily, weekly, or monthly periods)
  • Additional platform-level settings that govern how the feature operates across your site
Configuring sensible frequency rules ensures that spending limits are meaningful rather than easily reset, providing genuine protection for customers who use the feature.

Build docs developers (and LLMs) love