Summary: Major promoters moved from static PDF barcodes to animated or time-based QR to combat duplicate screenshots circulating on resale markets. The QR on a phone is no longer a fixed image—it may refresh every 30 seconds, embedding a signed token that scanners verify against cloud or edge servers. That shift reduces simple copy fraud but introduces connectivity and clock skew pain at rural festivals.
Secondary markets adapt too: social engineering (“send me your login to transfer”) often beats cryptanalysis.
Technical layers promoters use
- Signed JWTs or proprietary tokens in the encoded string, short TTL.
- Offline allow-lists synced to handheld scanners before doors open.
- Visual anti-tamper (hologram, wristband NFC) paired with QR for high-value tiers.
What static batch QR tools are not
QRBatch-style batch exports generate static graphics suitable for badges, asset tags, and marketing. They are not a substitute for a ticketing PKI. If you run a small conference, use a ticketing SaaS that owns rotation—not a folder of PNGs emailed to attendees.
Industry outlook
Expect tighter integration between wallet passes (Apple/Google) and venue access control, with QR as a fallback bitmap. The long-term trend is authenticated devices, not prettier pixels.