> 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/connectors/hardware.md).

# Hardware

Hardware requirements and compatibility for validating Apple Wallet and Google Wallet passes by barcode, QR code or NFC, with the vendor pages available.

The Wallet Crew passes are designed for real-world usage. A pass becomes useful when on-site hardware can read it reliably, at the right speed, and in the right environment.

In most deployments, hardware is the first constraint. It drives the choice between **barcode/QR** and **NFC**, and it defines the operational experience at checkout or at the gate. Qualifying the hardware early avoids late surprises such as unreadable screen codes, insufficient throughput, or NFC incompatibility.

<details>

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

* Retail loyalty: a 2D barcode scanner reads a QR code displayed in Apple Wallet or Google Wallet.
* Gift card redemption: a POS scanner reads a barcode from a phone screen, then applies a discount.
* Event entry: handheld scanners or fixed gates read QR codes at high throughput.
* Access control: NFC tap-in using readers compatible with Google Smart Tap or Apple VAS.
* Staff-assisted validation: a staff smartphone scans a customer’s QR code using a camera-based app, such as [Pass Scanner](https://docs.thewalletcrew.io/guides-scan/scan/pass-scanner.md).

</details>

## Hardware qualification checklist

{% stepper %}
{% step %}

#### Pick the interaction type

Decide whether the primary interaction is **barcode/QR scanning**, **NFC tap**, or a mix. This choice should match the on-site flow and the existing infrastructure.
{% endstep %}

{% step %}

#### Validate hardware capability

Confirm scanners can read from **phone screens** (not only from paper). For NFC, confirm the exact reader models support **Google Smart Tap** and/or **Apple VAS**.
{% endstep %}

{% step %}

#### Test in real conditions

Test with iOS and Android devices. Include screen brightness variation, protective glass, queue throughput, and staff habits.
{% endstep %}

{% step %}

#### Decide rollout and fallback

Define a fallback when a scan or tap fails (manual entry, alternative code, staff smartphone scan). Keep the fallback consistent across locations.
{% endstep %}
{% endstepper %}

## Barcode and QR code compatibility

The Wallet Crew is compatible with any hardware that can read the configured **barcode** or **QR code**, including when the code is displayed on a smartphone screen.

This typically includes:

* POS and handheld **2D imagers** (retail, hospitality).
* Venue scanning devices (handheld or fixed gates).
* Any camera-based scanner on a smartphone, when operationally acceptable.

{% hint style="warning" %}
Not every barcode scanner can read codes from phone screens: see [Third-party barcode scanners](https://docs.thewalletcrew.io/guides-scan/scan/scanner.md).
{% endhint %}

## NFC compatibility (Google Smart Tap and Apple VAS)

NFC can be used when the reader infrastructure supports the wallet protocols:

* **Google Smart Tap** (Google Wallet)
* **Apple VAS** (Apple Wallet Value Added Services)

This requires hardware that is explicitly compatible with these protocols. When compatible readers are in place, NFC provides a “tap” experience that can be faster than scanning, depending on the operational setup.

## Hardware vendors

No vendor-specific documentation is published. The pages below describe each vendor only. [Contact The Wallet Crew](https://www.thewalletcrew.io/contact) to discuss a vendor.

| Vendor                                                                        | Hardware                                   |
| ----------------------------------------------------------------------------- | ------------------------------------------ |
| [dot tech](https://docs.thewalletcrew.io/connectors/hardware/dot-tech.md)     | Scanning and reader hardware               |
| [Skidata](https://docs.thewalletcrew.io/connectors/hardware/skidata.md)       | Access control gates and scanning hardware |
| [Springcard](https://docs.thewalletcrew.io/connectors/hardware/springcard.md) | Contactless readers                        |
| [Team Axess](https://docs.thewalletcrew.io/connectors/hardware/team-axess.md) | Access control and ticketing hardware      |
| [Zebra](https://docs.thewalletcrew.io/connectors/hardware/zebra.md)           | Barcode scanners and mobile computers      |

## Hardware not listed

Hardware compatibility depends on the exact device model, firmware, wallet protocol, and operational flow. Validate those details before selecting a device. For hardware that is not listed, see [Choose an integration path](https://docs.thewalletcrew.io/connectors/wallet-pass-connectors.md#choose-an-integration-path). Tenant-specific hardware or on-site logic uses a [custom connector](https://docs.thewalletcrew.io/connectors/custom-connector.md) with tenant scripting and APIs.

## FAQ

<details>

<summary><strong>What does “Google Smart Tap / Apple VAS compatible” mean for hardware?</strong></summary>

It means the reader firmware supports the specific wallet NFC protocols used for value-added passes. Standard NFC capability is not always enough.

Reader compatibility should be validated on the exact model and firmware version intended for production.

</details>

<details>

<summary><strong>Can a smartphone be used to validate wallet passes?</strong></summary>

Yes, when the operational context allows camera-based scanning. This is common for pop-ups, low-volume checkpoints, or as a fallback.

For validation workflows built with The Wallet Crew, use [Pass Scanner](https://docs.thewalletcrew.io/guides-scan/scan/pass-scanner.md).

</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/connectors/hardware.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.
