Hardware
Hardware requirements and compatibility for barcode/QR and NFC wallet pass validation.
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.
Real-world examples
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 Crew Check.
Why hardware matters for wallet projects
Wallet passes are made for the physical world. Every pass is meant to be presented at a counter, a gate, or a checkpoint. That interaction only works if the “reading side” is solved.
This is why hardware qualification should happen early. It reduces project risk. It avoids late surprises such as unreadable screen codes, insufficient throughput, or NFC incompatibility.
Hardware qualification checklist
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.
Not every barcode scanner can read codes from phone screens. Older laser / 1D scanners often fail on displays. More detail on scanner selection is available in the scanner guide.
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.
The Wallet Crew has been successfully configured with NFC-capable hardware from: SpringCard, Zebra, Team Axess, ...
FAQ
Is any barcode scanner compatible with passes displayed in Apple Wallet or Google Wallet?
Compatibility depends on the scanner type. Most deployments use 2D imagers because they reliably read QR codes and barcodes from phone screens.
Older laser / 1D scanners often work on printed barcodes but fail on screens. More detail on scanner selection is available in the scanner guide.
Is NFC required to run a wallet project?
No. Barcode and QR code scanning is the most universal path. It usually works with existing scanners and is easier to roll out.
NFC becomes relevant when a “tap” experience is required and compatible readers are already available or planned.
What does “Google Smart Tap / Apple VAS compatible” mean for hardware?
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.
Can a smartphone be used to validate wallet passes?
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, see Crew Check.
Last updated