Barcodes on Tickets & Credentials

Ticket and credential barcodes encode boarding passes, transit fares, and access badges for gate validators—not casual phone scanning. PDF417 and Aztec are common on airline and event media; width and quiet zones must match airline or venue specs. Build test symbols in the PDF417 and Aztec generators, then proof on official verifier hardware.

Why teams use this

Gate throughput collapses when barcodes fail under lamination glare or truncated quiet zones. Credential layouts are spec-driven—creative resizing invalidates otherwise correct data.

How to implement it

Allow full PDF417 width on boarding passes, keep Aztec bullseyes clear of holo patches, and test under gate LED lighting.

• Obtain symbology and payload specs from the issuing authority.
• Never overlay foil security features on finder or start patterns.
• Print pilots through the same lamination stack as production.
• Validate timezone and passenger name fields separately from bars.
• Keep backup magnetic or NFC paths if specs require multimodal tickets.

Common mistakes

Assuming phone camera success equals gate scanner success causes launch-day incidents. Another mistake is reusing PDF417 dimensions from one carrier on another’s stock. Do not shrink Aztec on wristbands without arm-length tests.

Tools to get started

Use PDF417 and Aztec with travel document layouts and quiet zone rules.