> 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/merchant/faq/encaisser-un-paiement-crypto/comment-encaisser-un-paiement-crypto.md).

# How do I accept a crypto payment?

A crypto payment takes **5 steps**. Your customer pays from their own phone: you never have to handle crypto.

### Lyzi Pro Scan app

The 5 steps

1. **Enter the amount in euros** in the Lyzi Pro Scan app, then tap **Continue**.
2. **Generate the QR code** and show the screen to your customer.
3. **Your customer scans the QR code with their phone's camera.** Only the native camera app, never from a wallet or exchange app.
4. **Your customer pays from their payment page.** They choose their crypto and follow the instructions displayed.
5. **Wait for "Payment validated" on your device.** Confirmation takes about 2 minutes.

### Nepting

The 5 steps

1. **Enter the amount in euros** on the TPE, then tap **Continue**.
2. **Generate the QR code** by pressing the + at the bottom right then "QR Code Generation", and show the screen to your customer.
3. **Your customer scans the QR code with their phone's camera.** Only the native camera app, never from a wallet or exchange app.
4. **Your customer pays from their payment page.** They choose their crypto and follow the instructions displayed.
5. **Wait for "Payment validated" on your device.** Confirmation takes about 2 minutes.

### Static QR code

The 5 steps

1. **The customer scans the QR code at the checkout** with their phone's native camera app.
2. They choose the amount they want to pay **in euros**.
3. They continue the payment from their phone and tell you when it's validated.
4. On your side, go to [**https://admin.lyzi.io**](https://admin.lyzi.io) to see if the transaction went through.
5. Go to the payment history and wait for the transaction to switch to **"PAID"**.

{% hint style="warning" %}
**Always:** ask your customer to **keep their payment page open** in their browser until validation. If a problem occurs (insufficient amount, wrong wallet connected...), this is the page where the message and the steps to follow are displayed.
{% endhint %}

### Expected result

Your device displays the **"Payment successful"** screen with:

* the amount in euros;
* the merchant name;
* the date and time;
* the transaction **short code** (useful if you need to contact Lyzi);
* the **Print receipt** button (if TPE).

Your customer can also receive their receipt by email from their payment page.

### While waiting

| Time elapsed         | What to do                                                                                                                                  |
| -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------- |
| 0 to 2 minutes       | Wait, this is the normal delay.                                                                                                             |
| 2 to 10 minutes      | Look at your customer's payment page: if a message is displayed, follow the instructions.                                                   |
| More than 10 minutes | Check your customer's payment page, then [contact Lyzi](https://docs.lyzi.io/en/merchant/faq/support/comment-contacter-le-support-lyzi.md). |

More details: [The payment is slow to confirm](https://docs.lyzi.io/en/merchant/faq/problemes-de-paiement/le-paiement-ne-se-confirme-pas-ou-reste-en-attente.md).

### If it doesn't work

* The app asks to scan a QR code at startup: [App disconnected](https://docs.lyzi.io/en/merchant/faq/application-et-terminaux/lapplication-lyzi-pro-scan-me-demande-de-scanner-un-qr-code-au-demarrage.md).
* The customer can't scan: [The QR code doesn't work](https://docs.lyzi.io/en/merchant/faq/problemes-de-paiement/mon-client-narrive-pas-a-scanner-le-qr-code.md).
* The customer can't find their crypto: [Non-accepted crypto](https://docs.lyzi.io/en/merchant/faq/cryptomonnaies-wallets-et-exchanges/mon-client-veut-payer-en-usdt-en-bitcoin-ou-avec-une-crypto-non-acceptee-que-faire.md).
* The displayed time limit has been exceeded: [Time limit exceeded](https://docs.lyzi.io/en/merchant/faq/problemes-de-paiement/delai-depasse-ou-transaction-expiree-le-paiement-est-il-perdu.md).

### Questions covered

* "How do I accept a crypto payment?"
* "How do I get a customer to pay in crypto in store?"
* "How do I generate a payment QR code?"
* "What should my customer scan with?"
* "How long does a payment take?"
* "Where can I see that the customer has paid?"


---

# 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.lyzi.io/en/merchant/faq/encaisser-un-paiement-crypto/comment-encaisser-un-paiement-crypto.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.
