> 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-1.md).
# Alternative Stake
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.
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.
Alternative stake is invoked in the following cases:
* After [rejection codes](/transaction30api/api-description/validation-codes.md): -308, -511, -512, -513, -701, -702, -703, -711, -712, -713, -721, -722, -723.
* Bet types: singles, accumulators, system bets.
The new stake amount should be the same or lower as the suggested stake amount
### Ticket Acceptance Flow
In cases when the Alternative stake functionality has been activated, the information about the new suggested stake is included in the Ticket placement response, namely in the Suggestion object. It specifies the kind of the invoked functionality (Alternative stake) and the new suggested stake amount. More information can be found [here](/transaction30api/api-description/ticket-json-format-description/ticket-placement-response.md).
If the client (based on its end customer's confirmation) accepts the suggested offer, they will need to include the reference to the ticket ID of the initial ticket request (by including the ticketId value into the Ref object of the [Ticket Placement Request)](/transaction30api/api-description/ticket-json-format-description/ticket-placement-request.md).
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.sportradar.com/mts/features/alternative-stake-1.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.