> For the complete documentation index, see [llms.txt](https://docs.lsports.eu/u/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lsports.eu/u/trade/concepts/settlements.md).

# Settlements

In the following article, we will explain LSports settlement logic, how it works, what can trigger a settlement, and what can differ from an original settlement.

LSports settlements logic is based on a live feed input, therefore, it can be triggered only in case an event has a live feed coverage or a manual Full-Time result input. When there is an incident during an event (fixture) that is related to one market or more, it triggers a settlement for all the relevant markets.

For example - if there was a corner kick during a football event, all the related “Corner” markets that can be decided for a winner or a loser, will be decided accordingly after 1 minute (depending on the market type and the incident).

Under/ over – for every score incident, all lines that are related to the score in question will result accordingly in a minute's time.

### **How will a VAR affect the above-explained resulting flow?** <a href="#how-will-a-var-affect-the-above-explained-resulting-flow" id="how-will-a-var-affect-the-above-explained-resulting-flow"></a>

What does VAR stand for? The initials are Video Assistant Referee. Meaning: an assistant video referee who examines decisions made by the main referee with the help of the television cameras.

Within current LSports logic, if a VAR flag is raised within **1 minute's time**, the resulting system will be **delayed for 10 minutes**, after which the resulting will calculate the latest score and determine the outcome of the VAR.

In the case where the VAR flag is raised after a minute’s time of a disallowed goal report, the initial result that came after a minute will be canceled.

### **Manual Settlements**

Some markets do not have a predefined automatic settlement logic. To guarantee full coverage we have expanded our manual settlement service to all market types across all fixtures.

* **When is it used?** Whenever a market cannot be closed automatically by the data feed or by a full-time result.
* **How does it work?** Contact the LSports support team with the fixture ID and market name. Our trading team will review the request and manually apply the correct settlement.
* **Delivery of the result.** Once processed, the settled result is distributed through the regular API and data feeds so your systems receive it in the same way as any other settlement.

### Settlement Refund & Cancellation

Q: When will I get a refund?

A: In cases where the bet in question couldn’t be settled I.e.:

* Market ‘Player to score anytime’ - If the player in question never played during the match, the bet on his name will be refunded at the end of the match
* The event gets abandoned – Full-time results markets will be refunded
* The event got canceled before it got kicked off.
* Market "12" - If the match ends in a draw, the bets will be refunded at the end of the match.

Q: When will I get bet cancellations?

A: In cases where the initial score/incident was reverted.

* i.e. - 'Next Point Winner – If the point is getting canceled after it's been confirmed, the sent rustling upon confirmation will be canceled.


---

# 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.lsports.eu/u/trade/concepts/settlements.md?ask=<question>&goal=<endgoal>
```

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