The gate at a 12,000-seat show last month didn't scan a barcode printed on paper. It scanned a QR on a phone, and that QR had already changed twice while the person was walking up. Nobody downloaded anything to get in. They'd bought the pass weeks earlier inside the chat app they open fifty times a day, and the ticket lived in the same place their messages do.

Here's the part the industry keeps missing: a ticket isn't a physical object you protect. It's a deep link with a date. Tap it, and the app you already use opens the right screen at the right moment. The work of ticketing — buying, holding, entering — collapses into a flow that lives inside software people already trust.

Scan to enter, no install required

The biggest tax on live events is the install wall. A dedicated ticketing app means a new icon, a new account, a new password reset at the worst possible moment — the front of a queue. Mini-programs remove that wall. The attendee scans a poster, a story, a forwarded chat, and they're inside the purchase flow in the host app they never left. We've watched completion rates climb just by deleting the step where someone has to decide whether your app is worth a download.

This isn't a UI nicety. For a one-night event, an app install is a commitment the occasion doesn't deserve. A mini-program borrows the host's identity, payment, and notification plumbing, so the organizer ships a ticket booth without building a booth.

A QR that won't sit still

Static barcodes are a photocopier for fraud. Screenshot a PDF ticket and you can forward it to a friend who walks in an hour before you. The fix people in China landed on years ago is a dynamic code — the gate renders a QR that rotates on a timer, bound to the session and the device. A screenshot is stale the moment it's taken. The scanner checks liveness, not just validity.

It sounds like a small trick, but it changes the economics of scalping. When a code is worthless once it leaves the original phone, the resale market can't function on screenshots. You still need real transfer features for legit cases — gifting a ticket, a friend who can't make it — and the good mini-programs build those as explicit, logged actions rather than hoping a screenshot won't happen.

Gate problemWhat a static ticket allowsWhat a mini-program does instead
Pass sharingOne screenshot, many entriesCode rotates and binds to the device
Fake or duplicateHard to verify at the doorScanner checks liveness, not just the image
Late changesReprint and re-send by emailPush the new time straight into the pass
Lost ticketCall support, prove identityRe-open the deep link, it's still there
Walk-up salesSeparate queue and appSame flow, bought on the spot

Controlling who can hand it on

Transfer control is where event organizers get nervous, and rightly. A mini-program gives you the lever a paper ticket never could: you decide whether a pass is movable, how many times, and to whom. That's a policy choice, not a security afterthought. Set it tight for a seated gala, loose for a festival where friends swap plans constantly. The point is the rule lives in code you ship, not in a laminated sign at the entrance.

We'd push back on the cliché that this is 'killing the secondary market.' It isn't. It's moving the secondary market into a place where you can see it, tax it, and stop the worst of it. A creator who resells their own spare seat through a sanctioned flow earns something; a bot farm with ten thousand screenshots earns the organizer nothing but a fraud headache.

The overseas bet

Here's the thesis we actually believe: the event mini-programs that already work at scale in China — concerts, sports, expos, temple fairs — don't need to be reinvented abroad. The playbooks are proven. What's missing overseas is the runtime and the catalog: one universal layer that runs the same mini-program across a messaging app, a wallet, a maps app, wherever the local audience actually is, plus an open catalog so an organizer in São Paulo can drop in a ticketing mini-program the way they'd add a payment plugin.

Without that layer, every market means a rebuild for every host's quirks. With it, the Chinese experience ports. The gate logic, the dynamic QR, the transfer controls — none of that is culturally specific. A queue is a queue.

The honest risks

We won't sell this as free. A dynamic code needs a live connection at the gate, so venues with dead spots need offline fallback or the entry line becomes a spinner. Identity checks differ by country, and a runtime that normalizes them has to respect local rules, not flatten them. And 'no install' still depends on the host app being present — in a market with no dominant super app, you're back to convincing people to open something. The portability thesis only pays off where a runtime already has hosts.

None of that is a reason to wait. Start with the flow that hurts most — the entry line — and make the pass a living thing in the app your attendees already hold. Cross Mini App is building the runtime that lets one ticketing mini-program show up in every host an audience uses. The interesting part isn't the technology. It's that the ticket stopped being a thing you carry and became a link you already have.

Sources