> For the complete documentation index, see [llms.txt](https://docs.lsports.eu/u/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lsports.eu/u/defend/risk-controls.md).

# Risk Controls

Configure platform-wide and tier-based risk limits

Risk Controls allow you to define and manage betting limits across your entire platform. Set global thresholds that apply to all players, then customize limits by competition tier and market.

***

## Overview

<figure><img src="https://2846470291-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Ftv77Uhe1UsyYNAhnfDk8%2Fuploads%2Fgit-blob-326a80cf97f5cc1dfd1162039e5208a05f23bedc%2Fdefend-risk-controls-platform.png?alt=media" alt="Risk Controls"><figcaption><p>Platform Limits — global thresholds across your sportsbook</p></figcaption></figure>

<figure><img src="https://2846470291-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Ftv77Uhe1UsyYNAhnfDk8%2Fuploads%2Fgit-blob-77be3f3cede95cd237da4cd6222984b20c0d89ea%2Fdefend-risk-controls-tiers.png?alt=media" alt="Risk Controls"><figcaption><p>Tiers — set exposure limits by competition tier and market</p></figcaption></figure>

The Risk Controls section provides two levels of limit configuration:

| Level               | Description                                                                                                 |
| ------------------- | ----------------------------------------------------------------------------------------------------------- |
| **Platform Limits** | Global limits that apply across your entire sportsbook                                                      |
| **Tiers**           | A layer between Sport and Competition that groups similar competitions, with limits per tier and per market |

***

## Available Controls

### Platform Limits

Set the foundation of your risk management strategy:

* Maximum stake per bet
* Maximum payout per bet
* Maximum exposure per fixture
* Maximum daily/weekly/monthly limits

[Configure Platform Limits →](/u/defend/risk-controls/platform-limits.md)

### Tiers

A new layer between Sport and Competition that groups competitions sharing similar risk, so you manage them together instead of one at a time:

* Every competition is classified into a quality tier automatically
* Set a default limit per tier, with market-level limits for InPlay and PreMatch where you need more precision
* New competitions and markets get a safe default tier and limit automatically

[Configure Tiers →](/u/defend/risk-controls/tiers.md)

***

## How Limits Work Together

Tiers and Platform Limits are independent controls. For a bet's competition and market, DEFEND resolves the Tiers limit to enforce in this order:

1. The **market-level limit** for the bet's phase (InPlay or PreMatch)
2. The competition's **tier limit**, if no market-level limit is set
3. The **sport's Tier 4 limit**, as the final fallback

The first value found is the one enforced, not the most restrictive of all applicable limits. A market's custom limit always wins, even when it's higher than its tier's default.

New competitions default to **Tier 4** of their sport, except esports equivalents of a conventional sport (eSoccer, eBasketball, and similar), which default to **Tier E**, and E-Games titles, which default to **Tier 4 of E-Games**. New markets initially take their parent tier's default. Both are locked and shown as **New** until LTS publishes the value.

Player-specific limits from Player Intelligence sit outside this hierarchy for now; combining them with tier and market limits is planned for a later phase.

See [Tiers](/u/defend/risk-controls/tiers.md) for the full resolution logic.

***

## Related

* [Bet Monitor](/u/defend/bet-monitor.md) — Monitor betting activity in real-time
* [Player Intelligence](/u/defend/step-4-player-management.md) — Set player-specific limits


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.lsports.eu/u/defend/risk-controls.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.