> For the complete documentation index, see [llms.txt](https://developer.aiodds.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.aiodds.com/help-center/settlement/real-time-settlement-logic.md).

# Real-time Settlement Logic

## **Purpose**

Provide fast settlement results during live matches. However**,** due to factors like **VAR reviews**, results may be corrected within \~30 seconds.

## **Recommended Handling Strategies**

Strategy 1: Delayed Settlement

* Delay payout by **3–5 minutes.**
* If no changes occur within that window, proceed with payout.
* Resolves \~98% of such issues.

Strategy 2: Immediate Settlement + Rollback

* Settle bets in real time.
* If the result changes, revoke the previously paid amount and recalculate based on the corrected result.
* Platforms like 365 use this method.

## **Status Change Handling**

* If settlement result changes from <mark style="color:green;">1/2/4 to 0</mark>: Revoke the previous settlement and return the outcome to an unsettled result.
* If settlement result changes within <mark style="color:green;">1/2/4</mark>: Update result and reissue payout.

## **Additional Suggestion**

Implement a **manual override mode** for custom settlement adjustments when needed.


---

# 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://developer.aiodds.com/help-center/settlement/real-time-settlement-logic.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.