Cancellation - Description and Flow

Within the betting industry, it is sometimes necessary for an operator or a bettor to cancel a bet. This can happen due to various scenarios, but in all cases, MTS must receive a cancellation request to align records between the bookmaker and MTS. MTS has a pre-defined list of supported and acceptable reasons for bet cancellations.

During the integration, the OAM team will identify and activate the required cancellation types for the client (including setting various configuration options). For any cancellation scenarios not listed, please get in touch with the OAM, as these may be added and require agreement between Sportradar and the client.

Each supported cancellation reason has a specific code and a corresponding reason message (please see table and description below).

Cancellation reason codes

Code	Reason message	Note
101	Customer-triggered Pre-match bet cancellation. It should be used to request a bet cancellation when a punter has cancelled a pre-match bet.	Time-limited cancellation, Supports cancellation of part of a ticket or bet
103	Bookmaker Backoffice triggered bet cancellation. It should be used if a ticket was sent with incorrect information (manual error, for example - wrong selection/odds/stake/account number etc.) and the bet must be cancelled and re-sent with correct information.	Mandatory implementation for bookmakers, Supports cancellation of part of a ticket or bet
104	Bookmaker Technical issue triggered bet cancellation. It should be used if a client encounters technical difficulties and needs to cancel bets after resolving the technical issue.
105	Exceptional bookmaker triggered bet cancellation. There can be other unforeseen occasions where cancellations may need to be requested (other than the above for mentioned cancellations). In these instances, this cancellation code should be used.
301	Bet cancellation triggered by SOGEI (applicable for Italian jurisdictions). It should be used to inform MTS of cancellations triggered by SOGEI.
302	Bet cancellation triggered by SCCS (applicable for Belorussian jurisdictions). It should be used to inform MTS of cancellations triggered by SCCS.

Partial cancellation

With the partial cancellation feature, it is possible to cancel:

• an entire ticket

• a portion of a ticket

• an entire bet of a multi-bet ticket

• a subset of bets of a multi-bet ticket

• a portion of a bet of a multi-bet ticket

• custom portions of different bets of a multi-bet ticket

Clients can send as many partial cancellation requests as they want, provided that each cancellation request's ratio includes all previous cancellation requests' values. MTS does not aggregate cancellation ratio values of individual requests and considers the last request the final one.

Cancellation flow

Before processing the ticket/bet cancellation internally, the client has to send a Cancellation request to MTS. Only after MTS has accepted the Cancellation request, the client can finalise the cancellation transaction on their side.

By default, we expect that the client follows MTS recommendations about ticket acceptance. In other words, if MTS accepts the bet, the client should accept the same bet. If there is a need to reject a bet which MTS has accepted, then:

1. A Cancellation request should be sent to MTS.

Note

There are different cancellation types for various business and technical flows. See Cancellation reason codes table above.

1. If MTS has accepted a Cancellation request, then:

   1. The client cancels the bet.

   2. After the bet is canceled on the client's side, an appropriate Acknowledgement message should be sent to MTS to confirm that the bet has been cancelled. MTS will respond with an appropriate Acknowledgement Reply message.

2. If MTS has rejected a Cancellation request, the client should retain the bet in accepted status and flag it in the database (as such bets need to be identifiable and the reason for the rejected cancellation could be discussed, i.e. code not active, cancelation of a settled bet, cancelation after the cut off time, etc.).

   1. If the bet still has to be cancelled, the client should contact the MTS Operational Account Manager (OAM): [email protected] The client should keep the bet in accepted status until the OAM manually cancels the bet. After that, to maintain the same ticket status on both sides, the client should change the bet status to cancelled as well.

\

Note

Already rejected or settled tickets cannot be cancelled.

Note

Cancellation acknowledgement is mandatory for every cancellation reason.