> 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/transactions/comment-retrouver-une-transaction-et-son-code-court.md).

# How do I find a transaction and its short code?

Each transaction has a **short code** (for example 95SW40D3), displayed:

* on the QR code screen, under the QR code ("Short code");
* on the "Payment successful" screen of your device;
* on the customer's payment page, in the transaction details.

It's the simplest identifier to find a transaction in your history or to report it to support.

### Where to view your transactions

In the transaction history of your back office. A cashier only sees the transactions of their own cash register; the manager sees the whole account.

### Information to note in case of a problem

Before contacting Lyzi, note:

1. The transaction **short code**.
2. The **amount** in euros.
3. The **time** of the payment.
4. The **cash register** or point of sale concerned.
5. The **crypto** and **network** the customer says they used.
6. The **message displayed** on the customer's payment page, if there is one (a photo of the screen can help).

### Questions covered

* "How do I find a transaction?"
* "What is the short code?"
* "Where can I see my payment history?"
* "What information should I give support?"
* "I can't find a payment"


---

# 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/transactions/comment-retrouver-une-transaction-et-son-code-court.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.