> 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/overview/nos-produits.md).
# Nos produits
## Lyzi
Lyzi consiste en trois produits principaux:
* Backoffice
* Portail de paiement
* Application d'encaissement
## Backoffice
Le backoffice permet de gérer son compte Lyzi d'encaissement en crypto.
Voir aussi:
{% content-ref url="/pages/VcxywbkbUmZNTbL6O8Ex" %}
[Backoffice](/commercant/backoffice.md)
{% endcontent-ref %}
## Portail de paiement
La web app permettant à tout utilisateur de compléter son paiement avec ses crypto préférées.
## Application d'encaissement - Lyzi Pro App
Une application compatible iOS, Android mais surtout une variété de TPE, qui permet de démarrer un encaissement en crypto.
## Mais aussi...
Un SDK, une API documentée permettant une intégration en marque blanche
Des intégrations chez des partenaires comme Nepting
---
# 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/overview/nos-produits.md?ask=&goal=
```
`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.
