> 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-savoir-si-le-paiement-de-mon-client-est-valide.md).

# How do I know if my customer's payment is validated?

**Only "Payment validated" ("Payment successful" screen) on your device confirms the payment.** As long as your tablet, app or terminal doesn't display it, the payment is not secured.

### What counts, and what isn't enough

| What you see                                 | Value                   | Explanation                                                                                          |
| -------------------------------------------- | ----------------------- | ---------------------------------------------------------------------------------------------------- |
| "Payment validated" on your device           | **Only reference**      | The payment has been received. Allow about 2 minutes after sending.                                  |
| The payment appears in the customer's wallet | Useful to reassure them | It shows the customer has sent funds, but doesn't replace validation on your device.                 |
| The customer's phone screen                  | **Not enough**          | A customer screen, a screenshot or a message don't prove that the payment is validated on your side. |

{% hint style="danger" %}
Do not hand over the goods, tokens or service until your device displays "Payment validated".
{% endhint %}

### If "Payment validated" doesn't appear

1. Look at your customer's payment page: does a message indicate a problem? If so, follow the instructions.
2. If your customer has already sent their funds, **do not recreate a transaction**.
3. After 10 minutes without validation and without a message, [contact Lyzi](https://docs.lyzi.io/en/merchant/faq/support/comment-contacter-le-support-lyzi.md).

See [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).

### Questions covered

* "How do I know the customer has actually paid?"
* "The customer is showing me their phone, is that OK?"
* "The customer says they paid but I don't see anything"
* "The payment appears in their wallet but not on my tablet"
* "Can I give them their tokens?"
* "Is a payment screenshot enough?"


---

# 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-savoir-si-le-paiement-de-mon-client-est-valide.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.
