> For the complete documentation index, see [llms.txt](https://docs.lyzi.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lyzi.io/en/faq/cryptomonnaies-wallets-et-exchanges/mon-client-veut-payer-en-usdt-en-bitcoin-ou-avec-une-crypto-non-acceptee-que-faire.md).

# My customer wants to pay in USDT, Bitcoin or a non-accepted crypto: what should I do?

**Your customer cannot pay directly in USDT, in Bitcoin (Bitcoin network), in Solana, on BNB Chain, or with a crypto that doesn't appear on their payment page.** However, they can **exchange their crypto for an accepted crypto** (EURC, USDC, ETH, WBTC, POL or AVAX), then pay normally.

### Why it isn't possible directly

Lyzi only accepts the cryptos and networks displayed on the payment page. See [Accepted cryptocurrencies and networks](/en/faq/cryptomonnaies-wallets-et-exchanges/quelles-cryptomonnaies-et-quels-reseaux-sont-acceptes.md).

### What your customer needs to do

#### Solution 1: exchange from their wallet or exchange (the most common)

Most customers who are used to crypto know how to do an exchange ("swap") in their wallet or exchange.

1. In their wallet or exchange, the customer exchanges their crypto (for example their USDT) for an accepted crypto. **The simplest: a stablecoin, USDC or EURC**, which doesn't require connecting a wallet.
2. They return to their payment page and pay with the crypto obtained, **on the same network** as the one where they hold their funds.

#### Solution 2: exchange with the Lyzi exchange tool

The customer can do the exchange themselves with the Lyzi exchange tool:

* either **from their payment page**, with **the two small arrows at the top of the page** (wallet connected);
* or **directly on** [**pay.lyzi.io/otc**](https://pay.lyzi.io/otc).

The procedure is detailed in [Exchange a crypto before paying](/en/faq/cryptomonnaies-wallets-et-exchanges/comment-mon-client-peut-il-echanger-swap-sa-crypto-avant-de-payer.md).

### What you can tell your customer

> "This crypto isn't accepted directly. You can exchange it for USDC or EURC in your wallet or exchange, or with the two small arrows at the top of your payment page, then pay."

{% hint style="danger" %}
If your customer has **already sent** a non-accepted crypto to the payment address, the payment remains pending. Don't recreate a transaction and follow [Wrong network or wrong crypto](/en/faq/problemes-de-paiement/mon-client-sest-trompe-de-reseau-ou-de-crypto.md).
{% endhint %}

### What if the payment hasn't been started yet?

If the customer needs time to do their exchange and hasn't sent anything, you can cancel the transaction (arrow at the top left) and generate a new QR code once they're ready. See [Cancel a transaction](/en/faq/encaisser-un-paiement-crypto/comment-annuler-une-transaction-ou-un-qr-code-en-cours.md).

### Questions covered

* "My customer wants to pay in USDT, what do I do?"
* "Does Lyzi accept USDT?"
* "Can I accept USDT?"
* "Does payment in USDT work?"
* "Why can't my customer pay in USDT?"
* "My customer has Tether"
* "My customer wants to pay in Bitcoin"
* "My customer has BTC, what do they do?"
* "My customer has Solana / SOL"
* "My customer has BNB"
* "My crypto isn't on the list"
* "What is pay.lyzi.io/otc?"
* "Which crypto should my customer use?"


---

# 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.lyzi.io/en/faq/cryptomonnaies-wallets-et-exchanges/mon-client-veut-payer-en-usdt-en-bitcoin-ou-avec-une-crypto-non-acceptee-que-faire.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.