A wallet ticket launch starts at the entrance. Before choosing artwork or announcing tap-to-enter, decide how staff will validate each admission, which devices they will use, and what happens when a ticket cannot be read. Those decisions determine whether QR scanning or an NFC integration fits your event.
This guide explains platform requirements and a suggested rollout process. It does not certify any ticketing provider, venue or account as ready for NFC entry.
Choose the admission method before the pass design
QR and barcode entry: the attendee displays a code, and your scanning system checks the corresponding ticket. Apple Wallet supports QR barcodes and recommends testing passes with the actual scanning hardware. Apple also notes that optical scanners work better for iPhone screens than laser scanners. A phone camera may suit your workflow if your check-in software supports it. See Apple's Wallet getting-started guide.
NFC entry: the attendee presents the phone to a compatible reader. For Google Wallet event tickets, this uses Smart Tap. Google requires completed pass development and access to Smart Tap capable terminals, with the pass value correctly conveyed to your system. A reader advertised simply as “NFC enabled” is insufficient evidence that the complete workflow will work. See Google's Smart Tap prerequisites.
For Apple Wallet, adding NFC to a pass requires a special entitlement issued by Apple. Confirm the relevant issuer's entitlement and the intended reader integration before promising contactless entry. A signed barcode pass alone does not establish NFC readiness. See Apple's NFC pass documentation.
Confirm who owns issuance and production access
Ask your ticketing provider to identify the issuer, who manages certificates or credentials, and who handles renewals. Apple Wallet passes require an Apple-issued signing certificate. Apple's guide explains that an expired certificate prevents signing new passes and sending updates, even though installed passes continue functioning. Assign a renewal owner before tickets go on sale.
New Google Wallet issuer accounts start in Demo Mode with restricted recipients. Public issuance requires publishing access. Google's documented prerequisites include a completed Business Profile and at least one Passes Class. Check the actual account status rather than treating a successful test ticket as production approval. See Google's publishing-access process.
Match the ticket format to the entrance
Keep essential details readable: event name, venue, date and local time, admission category, seat if relevant, and a support route. Distinguish doors-open time from event-start time.
Apple documents specific poster event ticket requirements, including a warning about QR/barcode-dependent entry. The same documentation also discusses scannable codes, so confirm the target operating-system versions and actual pass presentation with your intended scanners before choosing that format. See Apple's poster event ticket requirements.
Run this checklist before releasing tickets
- Map the journey. Test purchase or registration, ticket delivery, saving to each wallet, retrieving the ticket and arriving at the correct entrance.
- Validate admission rules. Test a valid ticket, a second presentation, a canceled ticket, the wrong event and any permitted re-entry. Record the expected staff response for each.
- Test the venue equipment. Use representative phones and the actual scanners or readers. Include realistic lighting, screen conditions and the network connection available at the gate.
- Exercise changes. Verify what happens after a time, seat or ticket-status change. Confirm that the admission system checks the correct current record.
- Plan exceptions. Assign a staffed recovery process for a dead phone, missing ticket or connectivity interruption. Define any offline procedure and how conflicting check-ins are reconciled.
- Run a small rehearsal. Have staff follow the written instructions, record failures and resolve them before expanding distribution.
Budget for the complete entry workflow
Compare issuance charges alongside reader rental or purchase, scanner software, setup, staffing, support and connectivity. Ask each supplier to price the same attendance level and admission rules. A low pass price does not describe the entire event cost.
Launch when your chosen journey works with your issuer access, ticket format and venue equipment. Preserve the rehearsal results and exception procedures so the next event starts from a documented setup.
NFC Pass field guide