> For the complete documentation index, see [llms.txt](https://docs.thewalletcrew.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.thewalletcrew.io/guides-scan/guides-scan.md). # Scan Guides Entry point to the scan and validate guides: how wallet passes are read and acted on at checkout, entry gates, and redemption counters.

		Cover image
Scan & validate	Read barcodes, QR codes, and NFC passes at checkout, entry, or redemption points — choose the right hardware and validate passes reliably.	scan-and-validate.svg	Pass Scanner
Scanner	Pick the right scanner for wallet passes: 2D imagers vs laser scanners, 1D vs 2D codes, and a practical checklist for production readiness.	scanner.svg	Scanner

The core challenge is simple: wallet passes are displayed on a phone screen, and not every scanner reads screens well. **Scanner** walks through the practical side of this — why 2D imagers are typically the right choice over laser scanners, the difference between 1D barcodes (fast, compact identifiers) and 2D codes like QR (more data, better at short range and odd angles), and a selection checklist covering symbology support, screen brightness, cracked screens, and real-world throughput testing. Whether the moment is a loyalty scan at POS, a ticket check at an event entrance, or a gift card redemption, getting the hardware and scanning logic right from day one avoids costly read-rate issues in production. --- # 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.thewalletcrew.io/guides-scan/guides-scan.md?ask=&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.

Scan & validate

Scanner