> 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/problemes-de-paiement/paiement-bloque-ou-en-cours-de-verification-de-securite.md).

# Payment blocked or under security verification

The KYT\_FAILED status means that the wallet the payment came from did not pass Lyzi's due diligence checks. This check protects the merchant from fraudulent crypto transactions. If in doubt, contact <support@lyzi.fr>.

Lyzi's security system automatically analyzes the origin of the funds sent. When it detects an anomaly, **the payment is put under verification** (KYT\_FAILED status) and the Lyzi team reviews it themselves.

{% hint style="danger" %}
**Do not serve the customer** (don't hand over the goods, tokens or service) **until Lyzi has got back to you.** Until the verification is complete, the payment must not be considered received.
{% endhint %}

### What to do

1. **Wait for Lyzi's response.** The decision is never made at the checkout. Lyzi gets back to you quickly during the day, or the next morning if the block happens at night.
2. **Stay neutral with the customer.** Don't make any assumptions about the origin of their funds. You can say:

> "The payment is being verified by the security system. The Lyzi team will get back to us."

3. **Invite the customer to write to Lyzi support** via **payer assistance**: the **blue button at the bottom right** of their payment page.

You have no other action to take while waiting.

### The two possible outcomes

| Outcome                                 | What happens                                                                                            |
| --------------------------------------- | ------------------------------------------------------------------------------------------------------- |
| **Payment accepted** after verification | The payment proceeds normally and your device displays "Payment validated".                             |
| **Payment refused**                     | You don't receive the funds. The customer, who has been debited, is **refunded by Lyzi within 2 days**. |

### Questions covered

* "My payment is blocked, why?"
* "Payment under verification"
* "KYT\_FAILED, what does it mean?"
* "The customer has been debited but the payment is blocked"
* "Can I serve the customer?"
* "Will my customer be refunded?"
* "Suspicious funds"
* "Security anomaly"


---

# 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/problemes-de-paiement/paiement-bloque-ou-en-cours-de-verification-de-securite.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.
