> 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/application-et-terminaux/un-caissier-ne-voit-pas-toutes-les-transactions.md).

# A cashier can't see all transactions

**This is normal.** A cashier only sees the transactions of **their own cash register** (their "collector"). Payments accepted by a colleague on another cash register don't appear for them.

### To see all transactions

The **manager** sees all of the account's transactions. A **supervisor** can also view the account, without being able to take action.

### If a cashier can't see their own transactions

Check that they scanned **their own QR code** and not a colleague's: the payment is recorded on the cash register of the scanned QR code.

### Questions covered

* "My cashier doesn't see any transactions"
* "I can't see my colleague's payment"
* "Why is the history empty?"
* "The payment is recorded on the wrong cash register"


---

# 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/application-et-terminaux/un-caissier-ne-voit-pas-toutes-les-transactions.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.
