> For the complete documentation index, see [llms.txt](https://support.trybit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.trybit.com/payments/auto-conversion.md).

# Currency Autoconversion

Learn how to use the autoconversion feature to convert incoming payments into a stablecoin.

**Autoconversion** protects incoming funds from sharp exchange-rate fluctuations: an incoming payment is automatically converted into another chosen currency (for example, a stablecoin) as soon as the transaction is received — the balance amount doesn't "float" along with the market.

Configured separately for each project — one project's autoconversion rules don't affect your other projects, even if they belong to the same account.

### How it works

When creating a currency pair, you choose which incoming currency is automatically converted, and into which currency — for example, to protect against volatility, BTC → USDT (TRC20), ETH → USDC (ERC20). As soon as a payment in the chosen currency arrives on the network, it's automatically converted at the exchange rate at the time of conversion. The exchange is carried out through partner exchange services (FixedFloat, ChangeNow, LetsExchange, Exolix).

### Which currencies autoconversion can be set up for

Autoconversion isn't limited to a single target currency — you can set up a pair from any supported incoming currency to any supported conversion currency (including a stablecoin, if the goal is specifically volatility protection). The only restriction: **only one currency pair can be created per incoming currency**.

### How to enable it

In the [project settings](/getting-started/project-settings.md), under "Autoconversion" — click "Create Currency Pair" and choose the incoming currency and the conversion currency.

<figure><img src="https://1024061290-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FhlibkdeN79Y0EFrnLB1c%2Fuploads%2FDbRMymsrVfxWmT81BnJi%2F%D0%A1%D0%BD%D0%B8%D0%BC%D0%BE%D0%BA%20%D1%8D%D0%BA%D1%80%D0%B0%D0%BD%D0%B0%202026-10-15%20%D0%B2%2014.43.37.png?alt=media&amp;token=a4dc70b9-37e8-499a-8be1-7711c011a260" alt="" width="563"><figcaption></figcaption></figure>

### Limitations

* The minimum amount for conversion is 10 USD per operation; smaller payments aren't converted at all — neither automatically nor via manual exchange;
* A network fee is deducted from the exchange amount — it goes to the exchange service performing the conversion; Trybit itself charges nothing for the autoconversion operation.

{% hint style="success" %}
If you have any questions or need help, you can contact our support via chat on the website and in your personal account, as well as reach us on Telegram. Support contacts are listed [on our website](https://trybit.com/support).
{% 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://support.trybit.com/payments/auto-conversion.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.
