> 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/alternative-stake.md).

# Alternative Stake

| Ticket version | Delta offer | Activation      |
| -------------- | ----------- | --------------- |
| v2.1 and above | Optional    | Bookmaker level |

If a bet is rejected due to exceeded liability limits or maximum payout breach, MTS gives the end customer a chance of requesting the bet again with the maximum acceptable stake at the time of the ticket placement. After the first rejection, MTS sends the alternative stake value as a part of the ticket response. The bookmaker can then offer the end customer a chance of requesting the same bet with the alternative stake.

{% hint style="info" %}
**Note**

Alternative stake is available for live and pre-match betting. MTS can offer:

* alternative stake functionality for both live and pre-match,
* [bet re-offer ](/mts/features/bet-re-offer.md)for pre-match only, or
* a combination of alternative stake for live and bet re-offer for pre-match.
  {% endhint %}

There is no liability reserved for the repeated bet with the alternative stake. Therefore, if any of the usual conditions for ticket acceptance change before the end customer accepts the alternative stake and resends the bet (market suspension, aggregated liability increase, event deactivation…), the ticket might be rejected again.

High level flow:

1. Ticket is sent from operator to MTS
2. Ticket gets rejected due to liability/payout issues
3. A rejection message is sent to the bookmaker, along with the alternative stake in the currency of the initial bet.
4. The new ticket placed with the alternative stake must contain the ID of the initial ticket in the *altStakeRefId* field.

   .

Alternative stake works in the following cases:&#x20;

* Alternative stake is triggered for the following [rejection codes](broken://pages/3yqVqGJjNxDlgmQeBlpl): -308, -511, -512, -513, -701, -702, -703, -711, -712, -713, -721, -722, -723.
* Bet types: singles, accumulators, system bets.&#x20;
* For the time being, MTS is not offering alternative stake on the tickets which contain more than one bet (multi-bet tickets).

**See also:**

* [Bet re-offer](/mts/features/bet-re-offer.md)

<br>


---

# 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/alternative-stake.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.
