Business case · Events & festivals
Ticket in wallet, scan at the gate.
Festivals and large events are moving to digital tickets. The citizen receives the ticket directly in the European Wallet and presents it at the gate via NFC tap (2 seconds, no paper, no e-mail in spam). The organiser sees aggregates per event, never the individual participant's identity.
How it works
The flow, step by step
The citizen buys a ticket on the organiser's site and scans a QR — the ticket lands as a coloured coupon in the wallet.
On event day, at the gate, they open the wallet and NFC-tap the organiser team's validator tablet.
The validator checks the ticket signature, status (unused / used) and event date offline — in 2 seconds, no network, no queues.
What the European Commission says
“The European digital identity and the associated electronic attestations may be used to access private services online and offline, including in areas such as event tickets, transport or accommodation, with enhanced privacy through selective disclosure.”Regulation (EU) 2024/1183, recital 14 + Commission Recommendation C(2024) 1432 on the ARF 2.x — proximity flows.
The legal obligation
Legal status
VoluntaryFor event organisers, a wallet-held ticket isn't legally mandated yet, but Regulation (EU) 2024/1183 establishes the legal framework for any electronic attestation (including tickets, subscriptions, access passes) to have the same legal value as a paper document. The commercial advantage is immediate: 2-second gate verification (vs. 15-30 seconds for paper-ticket scans), GDPR-by-default compliance (no participant e-mail / phone list to keep), reduced fraud on duplicated tickets.
Demo: issue yourself an event ticket into the wallet
The exact flow described above, running live on this server. You generate a QR, scan it with the EUDI wallet, and the pass lands in your wallet within seconds — no registration, no personal data.
- The ticket is an EAA the organiser issues; admitted once, at the gate, no account
- Offline at the gate: the reader decides from the bundle; a ticket used twice is refused on sync
- ARF: non-qualified EAA (§6.3.2), revocation by status list
Other business cases