> For the complete documentation index, see [llms.txt](https://docs.sportradar.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sportradar.com/mts/transaction-3.0-api/additional-transaction-details/exchange-rates.md).

# Exchange Rates

MTS has a system currency which is used for defining liability limits, calculating current liabilities, showing amounts in reports, etc.

MTS converts every stake value other than the system currency at the bet acceptance time.

Currently, the MTS system currency is the euro.

As a source of the exchange rates, MTS uses the **OpenExchange service** ([https://openexchangerates.org](https://openexchangerates.org/)). Rates are retrieved from the web resource and updated in MTS every full hour.

**Rates are applied in the following way:**

* Rates are considered up to six decimal places.
* At the ticket level, the rate at the bet acceptance time is used to convert the stake into the system currency.
* Winning amounts are calculated based on the converted stakes at the bet acceptance time.

MTS supports the currencies listed in <https://docs.openexchangerates.org/reference/supported-currencies>.\
In addition to the listed currencies, MTS supports mBTC, where 1 mBTC represents one thousandth of a Bitcoin (0.001 BTC).

{% hint style="danger" %}
**Warning**

The client must always submit stakes in punter's local currency.
{% endhint %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.sportradar.com/mts/transaction-3.0-api/additional-transaction-details/exchange-rates.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.