> 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

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-cover data-type="image">Cover image</th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><h3>Scan &#x26; validate</h3></td><td>Read barcodes, QR codes, and NFC passes at checkout, entry, or redemption points — choose the right hardware and validate passes reliably.</td><td><a href="/files/TCHU1oWbxpjyjUmCLPEs">/files/TCHU1oWbxpjyjUmCLPEs</a></td><td><a href="/pages/crYH3jSoyROCwO8Q3DX6">/pages/crYH3jSoyROCwO8Q3DX6</a></td></tr><tr><td><h3>Scanner</h3></td><td>Pick the right scanner for wallet passes: 2D imagers vs laser scanners, 1D vs 2D codes, and a practical checklist for production readiness.</td><td><a href="/files/4hoFYyiVviFKuomf6haU">/files/4hoFYyiVviFKuomf6haU</a></td><td><a href="/pages/O6gdiZOJngTZUNmeOJ4p">/pages/O6gdiZOJngTZUNmeOJ4p</a></td></tr></tbody></table>

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 you're validating a loyalty scan at POS, checking tickets at an event entrance, or redeeming a gift card, getting the hardware and scanning logic right from day one avoids costly read-rate issues once you're live.


---

# 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.thewalletcrew.io/guides-scan/guides-scan.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.