> For the complete documentation index, see [llms.txt](https://docs.sportradar.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sportradar.com/mts/features/payout-cap-t-and-c-payout.md).

# Payout Cap (T\&C Payout)

Maximum payout is the maximum amount that an operator is prepared to pay out on an individual winning ticket. This does not include the stake, because it is purely on liability.

MTS supports various methods in configuring Maximum Payout limits:

* **Customer Maximum Payout** – Tickets with a payout value that exceeds the configured amount will be rejected. MTS aggregates potential winnings of repeated, identical bets coming from the same customer, so it is not possible for the customer to avoid the limit by placing a number of smaller bets.
* **Customer Maximum Payout (Bookmaker T\&C)** – Feature that allows operators to set a Terms and Conditions Maximum Payout limit which would accept bets that exceed the set value but cap the payout if the bet won, and would only be aggregated on a Customer level. 
  * The operator can also cap ticket level payout by sending the `payCap` value directly in the ticket. This allows operators to track daily winnings on customer level across different tickets and adjust maximum ticket payout accordingly.
* **Aggregated Max Payout** – Allows for the aggregation of repeated bets across all business taken. This is to protect against multiple users placing identical bets (commonly seen with "tipster" activity)
* **Sport Level Max Payout** – Applied to all 3 options above allows Clients to set a Maximum Payout on Sport level


---

# 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.sportradar.com/mts/features/payout-cap-t-and-c-payout.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.