QR Code Tickets vs. Apple Wallet and Google Wallet Passes

It's not really QR code versus wallet pass

A wallet pass and a QR code ticket aren't opposites. Apple and Google both let a pass carry a QR code, so a wallet ticket is often a QR code with extras around it. The real question is whether those extras are worth the setup for your event.

A plain QR ticket is a code in an email, a PDF, or a printout. It never changes after you send it. A wallet pass lives in the Wallet app on the phone, and it can be updated after it's issued.

A wallet pass is a container

Apple describes event tickets as passes for concerts, movies, plays, and sporting events. Usually there is one pass per event, though a single pass can cover several, like a season ticket. Wallet can show passes based on location, and developers build them with Apple's PassKit framework.

Apple's older Wallet guide lists four barcode formats for passes: QR, PDF417, Aztec, and Code 128. Google's Wallet API has static barcodes as well, and its sample payloads use QR_CODE as the type.

So the QR code is still there. What the pass adds is a home for it. Attendees don't dig through email, and organizers can change details later. Ticketing providers use that for pre-event messages such as parking details, arrival reminders, and gate changes, sent through pass updates and, where supported, Wallet notifications.

A QR code in an email can't do any of that. If the venue moves, you send another email and hope people read it.

Screenshots, sharing, and fraud

This is where the formats split. A static QR code is a visible identifier, and as CodeREADr puts it, "a barcode or QR code is a visible identifier that any camera can capture and share." Putting that same static code inside a wallet pass doesn't change this. A screenshot of it works just as well as the original, so protection depends on your backend checking each code, for example flagging a ticket that's already been scanned.

Wallets offer two stronger options:

• Rotating barcodes (Google). The code is generated with a time-based one-time password, and the reader accepts only the most recent one. Google's documentation says this reduces theft and resale from screenshots, because a screenshot goes stale once the code rotates. It says the code typically changes about every minute, and the interval is configurable. For a closer look, see why some ticket barcodes keep changing.
• NFC tap (Apple VAS, Google Smart Tap). The handshake is encrypted and tied to the device, so there's no visible code to screenshot or forward. The catch is hardware: it needs certified readers and extra certification.

Google's fallback order matters too. If a pass has several methods, Smart Tap comes first, then the rotating barcode, then the static barcode. A static fallback weakens the protection.

What organizers need to set up

Barcode and QR passes are mostly self-service. According to CodeREADr:

• Apple needs a standard Developer Program account with no special review, plus a Pass Type ID certificate that you renew every year.
• Google needs an issuer account and a completed business profile, and it reviews the account before granting production access.
• Approval for barcode passes takes days.
• Any camera or optical imager that can read a phone screen can scan them.

NFC passes take longer because of reader certification and key setup. Passes also follow Apple and Google templates, so you can't design them freely, and attendees have to add them to Wallet themselves. The upside is that nobody has to download an app.

A plain QR ticket needs none of this. Make one in a few minutes and send it anywhere. One scanning note from Apple's guide: most laser scanners can't reliably read a barcode on a phone's LCD screen, so use a camera-based or optical scanner either way.

Which should you use?

Pick by the stakes of the event:

• Small, free, or one-off events (a school night, a meetup, a workshop): a plain QR ticket with a unique code per person. Check each code against a list at the door.
• Paid events where resale or sharing is a worry: a wallet pass with a rotating barcode or NFC, through a pass provider that handles credentials and updates.
• Events where details change: a wallet pass, because you can update it instead of re-sending.

Whatever you choose, give every ticket its own code and validate it on a server. Phone-based credentials work the same way elsewhere: mobile driver's licenses also put a QR code on a phone. If you need a plain QR code quickly, QRDock makes them for free, without ads or tracking.

Frequently Asked Questions

Is a wallet pass safer than a plain QR code ticket?

Not automatically. A pass that carries a static QR code can be screenshotted like any other. The extra safety comes from rotating barcodes or NFC, combined with backend validation.

Can an Apple Wallet or Google Wallet pass contain a QR code?

Yes. Both platforms support QR as a barcode format, so many passes are a QR code with updates and Wallet features around it.

Do wallet passes need special scanners?

Barcode and QR passes work with any camera or optical scanner that can read a phone screen. NFC tap passes need certified readers.