Skip to content

General overview

A Bet is an object that represents a list of selections confirmed by a bettor with a given stake.
A Selection is an object that represents which match (sport event), market, odd, and odd value a bettor wants to place a bet on. A selection can contain both DATA.BET and non-DATA.BET matches, markets, or odds. A selection with non-DATA.BET elements is called a foreign selection.
A Market is an object that represents an event in the real world (or game, or simulator) with certain outcomes. For example: who will win the game.
An Odd is an object that represents the probability of an event outcome. An odd has a value that represents the probability of the outcome with some margin included.
A Cash-out is an object that represents a bettor's action of getting back (returning money to the balance) part of a bet (it can also be 100% of the bet).

Bet

A bet is a sum of money that a player places on the odds values of sports events. On the technical side, in addition to the amount of money, the bet includes a number of other fields, which are described in detail in the Swagger - Schemas section: Bet.

Types of bets

There are three types of bets. Each bet contains a set of outcomes with fixed odds (selections a player makes):

  • Single is a bet on one sport event.
  • Express (also referred as combo) is a bet on simultaneous forecast of the outcome of two or more independent events.
  • System is a bet which consists of three or more combo bets. It enumerates all the possible combos of equal size from the fixed set of the selected outcomes. The same bet amount is placed on each combo (each system option).
Calculation logic

The logic of calculating winnings depends on the type of bet.

Bet type Calculation logic
Single The amount of winnings for single bets is calculated by multiplying the bet amount by the odds for the given outcome of the event.
Express A combo bet (also called combo) wins if all the selected outcomes of sport events are predicted correctly. An incorrect prediction for at least one event means the combo is lost. The minimum number of events in a combo is two, and the maximum is unlimited, but the winning sum cannot exceed 50,000 euros. Combo winnings are calculated by multiplying the odds of all included outcomes by the bet amount, then the resulting value is rounded to three decimal places. Combo odds are shown for convenience, they are rounded to two decimal places, and they are not the final odds for calculating winnings.
System A system bet type implies that the same bet amount is placed on each combo (each system option) and the number of outcomes is the same in each combo. The system winnings are the sum of the winnings of the combos that make up the system.

Modes of placing bets supported by MTS

  • Risk managed bets - The MTS platform is responsible for both bet validation and risk management. In this mode, the API evaluates each bet request and either accepts it or decline it. If a bet is declined, the API returns a list of specific restrictions detailing the reasons for the rejection. Risk managed bets documentation.
  • An advisory bets is one in which risk management is not applied. The bookmaker assumes responsibility for risk management and the calculation of results for such bets. An advisory bet documentation.

Bet Integration Requirement

One of the above bet integrations (Risk managed bets or Advisory bets) is required to enable bet placement functionality in your MTS implementation.

Can we launch without any of those bet integrations?

Launching without bet integration is not a supported setup as it poses significant risks to your operation. The following considerations should be taken into account:

Integration Testing Limitations Without bet integration, comprehensive integration testing cannot be performed. This results in untested edge cases being deployed to production, creating a high risk of critical issues that could impact your business operations.

Operational Monitoring Challenges The initial days after launch are critical for monitoring operations and responding quickly to any issues. Without bet integration, our support team cannot provide effective assistance as they lack visibility into bet-related operations. MTS includes a dedicated team of approximately 15 risk management experts who provide ongoing support and monitoring capabilities.

Financial Reporting and Invoicing Bet integration enables accurate calculation of bet reports and proper invoicing processes. Without this integration, the system would rely entirely on external reports, which may require additional approval processes and could impact financial accuracy.

Dynamic Line Adjustment Our system leverages bet integration to adjust the line dynamically based on bookmaker load. This real-time adjustment capability is essential for optimal risk management and cannot function without proper bet integration.

Summary It is strongly recommended to ensure bet integration is completed before production launch

Restrictions

Managed trading services have several restrictions that can be applied to bets. Some restrictions are player-specific, and others are not.

Each restriction is characterized by a type and context. The context interface is closely coupled with the restriction type.

Currently, the following bet restriction types are supported:

  • max_bet
  • bet_type
  • bet_interval
  • selection_value
  • sport_event_status
  • sport_event_existence
  • sport_event_bet_stop
  • market_status
  • market_existence
  • market_defective
  • odd_status
  • odd_existence

And the following cash-out restriction types:

  • bet_status
  • bet_selection_existence
  • selection_value
  • selection_value_change
  • sport_event_status
  • sport_event_type
  • sport_event_existence
  • sport_event_bet_stop
  • market_status
  • market_existence
  • market_defective
  • odd_status
  • odd_existence
  • cash_out_bet_type
  • bet_cash_out_selections_mismatch
  • cash_out_unavailable
  • cash_out_amount_limit
  • cash_out_refund_amount
  • cash_out_order_status

For more details, please refer to BetRestriction and CashOutOrderRestriction schemas.