> 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/scan/scanner.md).

# Third-party barcode scanners

Choose third-party barcode scanner hardware that reliably reads 1D barcodes and 2D QR codes from Apple Wallet and Google Wallet passes on phone screens.

Barcode and QR code passes are made to be presented on a phone screen. The scan experience depends on the scanner hardware, its configuration, and on-site conditions.

This page is about separate barcode scanner hardware that a brand buys. To scan with a staff phone instead, use [Pass Scanner](https://docs.thewalletcrew.io/guides-scan/scan/pass-scanner.md), The Wallet Crew's app. Pass Scanner also reads from the trigger of Zebra Android devices and, on compatible devices, NFC.

Hardware constraints often drive the decision between barcode/QR scanning and NFC. A broader compatibility overview is available in [Hardware](https://docs.thewalletcrew.io/connectors/hardware.md).

<details>

<summary><strong>Real-world examples</strong></summary>

* Retail loyalty: a 2D scanner reads a QR code from a phone at checkout.
* Event entry: handheld scanners read QR codes at the gate, in bursts.
* Gift card redemption: a counter scanner reads a barcode, then applies value.

</details>

## Recommended scanner type for phone screens

2D imaging scanners (2D imagers) are typically the right choice for wallet projects. They capture the code as an image, which makes reading from screens reliable.

Laser scanners can work well on printed 1D barcodes. They often underperform on phone screens because reading depends on reflected light. Modern screens and protective glass tend to reduce that reflection.

A rotating barcode (Google Wallet) is always a QR code or a PDF417: plan for a 2D imager where rotating barcodes are used.

{% hint style="info" %}
Most 2D imagers support many 1D and 2D symbologies. Support varies by model and license. Hardware specs should be checked against the barcode formats used in pass templates.
{% endhint %}

## 1D and 2D codes

<figure><img src="https://2365162339-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiqBD4M0nHFMaFeKR75p9%2Fuploads%2Feha7CGEjKQHKZp6c1Fbl%2Fscan-scanner-differences-between-1d-2d-barcodes.png?alt=media&amp;token=c36b0b5e-c52e-4ff1-b4d8-26403c43f21a" alt="Comparison between a 1D barcode (linear bars) and a 2D barcode (matrix code such as QR)."><figcaption><p>1D codes are linear. 2D codes are matrix-based.</p></figcaption></figure>

|            | 1D (linear)                                                                     | 2D (matrix)                                                                                            |
| ---------- | ------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------ |
| Looks like | Parallel bars, often with a human-readable number below                         | Data stored in a grid; QR code and Data Matrix are common examples                                     |
| Data       | Usually short identifiers                                                       | Can store more data, and widely used for tickets                                                       |
| Scanning   | Can be fast to scan at distance, and tends to be cheaper to support in hardware | Scans well at short range and in multiple orientations, which helps throughput in crowded environments |

## Practical selection checklist

Validate the scanner early, with these checks:

* Confirm “reads from **mobile screens**” is explicitly supported.
* Prefer **2D imagers** for mixed 1D/2D needs and screen reliability.
* Confirm supported symbologies match what is used (QR, Data Matrix, Code 128, PDF417, etc.).
* Test with iOS and Android devices, across low and high brightness.
* Test with common phone conditions: screen protector, cracked glass, and low-battery dimming.
* Validate throughput in realistic conditions (queue, scan distance, staff habits).

## FAQ

<details>

<summary><strong>Does barcode scanning require NFC-capable hardware?</strong></summary>

No. Barcode and QR code scanning uses optical reading (scanner or camera).

</details>

<details>

<summary><strong>Can a phone screen be scanned with a 1D laser scanner?</strong></summary>

Sometimes, but it is not a reliable baseline for production.

</details>


---

# 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/scan/scanner.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.
