Introduction

Key terminology

This documentation consistently uses specific terms to maintain clarity. Below is a list of some terms with their definitions:

Client	MTS's customer, usually a bookmaker offering betting services
End customer	A person placing bets, a bettor or punter, the client's customer
Ticket	A message in client-MTS communication, including bet and bet-related data
MTS	Sportradar's risk management service provided to their clients

---

Generally, clients are subscribed to the betting risk management service provided by MTS. Clients receive bets from their end customers, send them over to MTS, and expect a concrete and timely suggestion on whether a particular bet should be accepted. MTS maintains current liability per client and particular sporting event, betting market, etc. and returns a suggestion promptly. A suggestion in this context means a decision on whether the end customer's bet should be accepted or rejected. The majority of responses are sent back within 25ms after the start of ticket validation, which means almost instantly for prematch bets and after the LTD (Live Time Delay) for live bets.

A client communicates with MTS by exchanging tickets. This exchange is called the Ticket Transfer Protocol.

To receive a suggestion, the client sends over betting data received from its end customer in a Ticket placement request. MTS answers with a Ticket placement response. There are more ticket types besides Ticket placements requests and responses (many times just called ticket requests and responses).

List of available ticket types:

• Ticket placement - sending over a standard ticket from the client to MTS, including the end customer's bets

• Cancellation - request to cancel a previously placed ticket

• Cash-out - request to pay out a particular placed and accepted ticket even before it has been settled

• External settlement - request to settle a bet containing at least one event which is under the client's control (and not related to the content provided by Sportradar or supported by MTS)

Note

MTS responds to every request made by the client.

Furthermore, every MTS response can be answered by an Acknowledgement message from the client to MTS. Please see Ticket acceptance flow description for situations when the acknowledgement messages are mandatory. Acknowledgement messages allow the client to inform MTS about its decision regarding the MTS's suggestion, i.e. whether the client accepts the suggestion (or MTS response in general). MTS responds to every Acknowledgement message with an Acknowledgement reply message.

Note

A response can be followed by an Acknowledgement message from the client. MTS responds to every Acknowledgement message with an Acknowledgement reply message. Positive Cancellation responses should always be followed by an Acknowledgement message from the client.

Ticket Transfer Protocol - top-level diagram

Ticket acceptance flow diagram is available here.