> 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/demarrer-un-paiement/qr-code-statique-dencaissement.md). # Static Collection QR Code {% embed url="" %} Unlike QR codes to scan with the Lyzi ProScan app, this QR code is static and it's up to the customer to scan it. Ideally you can for example print this QR code and display it near your cash register or download it as PDF or PNG. If a customer wants to pay in crypto, show them this QR code so they can scan it with the camera app on their smartphone. It will therefore be up to the customer to enter the amount to pay. They will then need to present you with the QR code that appears on their screen (after manually entering the amount of the item to pay themselves). You'll just need to scan their screen and follow the instructions on your 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 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/merchant/demarrer-un-paiement/qr-code-statique-dencaissement.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.