> 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-annuler-une-transaction-ou-un-qr-code-en-cours.md).

# How do I cancel a transaction or a QR code in progress?

You can cancel a pending transaction **at any time**, using **the arrow at the top left** of the QR code screen in the app.

### When to cancel

* A **test**.
* A **customer who gives up** on paying.
* A customer whose time limit has been exceeded and who **hasn't sent anything**.

In these cases, cancel rather than letting the transaction expire. You can then generate a new QR code.

### When not to cancel

{% hint style="danger" %}
**Do not cancel or recreate a transaction if your customer has already sent their funds.** The payment can still be validated, even after the displayed time limit. Recreating a transaction risks making your customer pay twice or making their payment harder to trace.
{% endhint %}

If in doubt, ask your customer whether they have already sent their funds:

| Customer's answer | What to do                                                          |
| ----------------- | ------------------------------------------------------------------- |
| Yes, they sent it | Wait for validation on your device. Don't recreate anything.        |
| No, nothing sent  | Cancel with the arrow at the top left, then generate a new QR code. |

### Questions covered

* "How do I cancel a payment in progress?"
* "How do I cancel a QR code?"
* "The customer no longer wants to pay"
* "I made a mistake in the amount"
* "Can I generate a new QR code?"


---

# 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-annuler-une-transaction-ou-un-qr-code-en-cours.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.
