One wallet tap. Age proven, ticket presented, WiFi on.
Festivals, conferences, stadiums, night-clubs and venues stitch identity together from paper tickets, wristbands, door lists, plastic-cup deposits and captive-portal WiFi. The EU Digital Identity Wallet collapses all of that into one tap at the door: age proven cryptographically, ticket verified against a signed issuer, entry-list membership confirmed, guest WiFi profile signed and provisioned — before the punter has taken their phone out of their pocket. This page is what our platform ships for the events sector, and what’s on the near-term roadmap.
Use cases
Age gate at the door
Wallet proves 18+ (or 16+, 21+) with a single boolean claim. No date-of-birth disclosed. See the age-verify page.
Signed ticket
Issued as an OpenID4VCI credential; presented at gate via OID4VP. Non-transferable via holder binding (KB-JWT) — kills the resale-scalper problem cryptographically.
VIP + press allowlist
Named-list membership proved without disclosing the list. Guest picks credential, gate verifier does a boolean query.
Guest WiFi
Same wallet tap that opens the gate provisions a signed WPA2-EAP profile scoped to the event dates. See network access.
Cashless cup deposit
Wallet holds the deposit attestation as a credential; return the cup, credential revokes, deposit refunds automatically. Roadmap.
Conference badge
Attendee credential replaces the printed lanyard. Session-attendance signed into the audit log for CPE credits.
Compliance angles
- DSA (Digital Services Act) — age-verification obligations for platforms serving minors; EU Wallet age attestation is the reference implementation.
- eIDAS 2.0 Article 5f — large-platform and regulated-sector acceptance mandate binding Dec 2027; ticketing platforms above the DSA threshold are in scope.
- GDPR — DCQL query returns only the claim(s) needed. No date-of-birth harvest for door-list retention.
- National ID-check requirements — German JuSchG, French loi sur les jeux d’argent, etc. — satisfied by a cryptographic age attestation instead of a photo of a physical ID.
Why Aloaha for events
Every EUDI-protocol layer is written in-house by the Aloaha Limited team on Malta. Deployment is as a self-hosted or Aloaha-managed multi-tenant service — the ticketing platform, the venue, or the promoter can each run their own tenant with isolated keys, audit trails and configuration. No eudi-lib-* SDK in the dependency tree; generic infrastructure libs (JWT/JWS, HTTP, .NET BCL crypto primitives) are widely-used open-source components while the EUDI-protocol layer itself is 100% Aloaha-written. Everything is auditable line by line.