> 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/encaisser-un-paiement-crypto/comment-mon-client-paie-t-il-en-crypto-les-etapes-de-sa-page-de-paiement.md).

# How does my customer pay in crypto? The steps of their payment page

Knowing your customer's journey lets you guide them and quickly spot where they're stuck. Everything happens on **their payment page**, which opens in their phone's browser after scanning the QR code.

### The steps on the customer's side

1. **Choice of payment method.**
   * **KuCoin Pay or WhiteBIT**: the customer is redirected to their exchange to complete the payment.
   * **Crypto transfer**: the customer continues on the payment page.
2. **Choice of crypto and network.** Each crypto is displayed with its available networks. The customer chooses, then confirms the selected network.
3. **Sending the funds.**
   * **Stablecoins (EURC, USDC)**: no need to connect a wallet. The customer sends **the exact amount** to the displayed address, by scanning the QR code or by copy-paste, from any wallet that lets you enter a destination address and an amount, **choosing the same crypto and the same network**.
   * **Other cryptos (ETH, WBTC, POL, AVAX)**: the customer must **connect their wallet**, at the top left of the payment page.
4. **Confirmation.** The page displays "Payment successful" and the customer can receive their receipt by email. On your side, wait for "Payment validated" on your device.

### What the customer also sees on their page

* **The amount in euros and the fees**, displayed on the page. The crypto price displayed at first is an estimate; the final price appears at the next step.
* **A countdown** ("Expires in ... minutes"), whose duration depends on the payment method. A payment sent after this time limit can still be validated. See [Time limit exceeded](/en/faq/problemes-de-paiement/delai-depasse-ou-transaction-expiree-le-paiement-est-il-perdu.md).
* **Error messages** and the steps to follow (missing amount, wallet without funds...).
* **Two small arrows at the top of the page** (wallet connected) to exchange one crypto for another. See [Exchange a crypto before paying](/en/faq/cryptomonnaies-wallets-et-exchanges/comment-mon-client-peut-il-echanger-swap-sa-crypto-avant-de-payer.md).
* **Payer assistance**: a **blue button at the bottom right**, to write directly to Lyzi support.

### Logging in: wallet or email?

On the login screen, the customer can log in with Google, Apple, an email, a passkey, as a guest, or **"Connect a wallet"**.

{% hint style="warning" %}
To pay in ETH, WBTC, POL or AVAX, the customer must choose **"Connect a wallet"** and connect the wallet that holds their funds. If they log in by email, they will see a balance of 0. See [Customer logged in by email: balance at 0](/en/faq/problemes-de-paiement/le-wallet-connecte-ne-detient-pas-assez-de-fonds.md).
{% endhint %}

### Questions covered

* "What does my customer need to do to pay?"
* "My customer doesn't know what to choose on the page"
* "Does my customer need to connect their wallet?"
* "What is the countdown on the payment page?"
* "Where can my customer contact support?"
* "Can my customer get a receipt?"


---

# 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/encaisser-un-paiement-crypto/comment-mon-client-paie-t-il-en-crypto-les-etapes-de-sa-page-de-paiement.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.