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: -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.

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).