How the EU Digital Identity Wallet changes hotel check-in: replacing passport scanning with PID credential presentations, GDPR-compliant record-keeping, and age verification.
Passport scanning is a friction point that hotels have accepted for decades because there was no better alternative. From 2026, EU member states are required to issue wallets to citizens, and hotels can request verified identity credentials directly from a guest's phone.
The core credential is the PID (Person Identification Data), issued by each member state's national identity authority. It contains: full name, date of birth, nationality, place of birth, and residential address. The critical feature for hotel operations is selective disclosure. For a standard check-in, you might request only name and age_over_18. The guest's wallet shows them exactly which fields you are requesting, and they must actively consent. You never see the passport number, full date of birth, or address unless you explicitly request them. This matters for GDPR data minimisation: if all you need is that the person is an adult and their name matches the booking, requesting more creates unnecessary compliance exposure.
Your backend sends an OpenID4VP authorization request. The guest reviews and approves the disclosure, and the wallet responds over the internet with a verified, cryptographically signed response. Identity verification is complete before the guest arrives. The front desk confirms the person matches the name on the reservation and hands over the key.
The desk terminal displays a QR code or initiates a connection via NFC or Bluetooth Low Energy. The guest scans or taps, approves consent, and the credential is shared directly to the terminal. This proximity flow works offline — the credential is verified locally using the issuer's public keys, which the wallet carries. Automated check-in kiosks are a natural fit here.
Most EU member states require hotels to record guest identity for police registers. For EU citizens, the PID carries the same legal weight as the underlying identity document. The credential presentation creates a verifiable audit record: proof that a credential was presented, which fields were disclosed, and when the check occurred. With passport scanning you store an image that must later be deleted. With wallet presentations, you record only the minimum necessary for the police register, with no residual document image to manage. Check with legal counsel on specific requirements per jurisdiction.
Bar and restaurant access: a staff member initiates a wallet check from a tablet, the terminal requests age_over_18 (or age_over_21), and receives a yes/no response — no date of birth revealed. Minibar activation: a wallet check at check-in sets a verified-adult flag on the reservation without storing the actual date of birth. The mDL is usable for age-only checks such as bar entry. For the police register requirement, PID is the appropriate credential.
The wallet check replaces the passport scan. It does not replace the visual check that the person matches the identity. Counter staff should understand three things: (1) the wallet credential is verified by the system — if the terminal confirms it, the credential is genuine; (2) they still need to confirm the guest's face matches the name; (3) if a guest does not have an EUDI Wallet, the existing passport or ID card process continues as normal. Training does not need to be lengthy — the interaction is simpler for staff because verification is automated.
Hotels cannot request EUDI Wallet credentials without registering as a relying party. Registration defines which credential types and attributes your organisation is authorised to request. The registered scope is enforced by the wallet — a hotel registered to receive name and age_over_18 cannot silently expand that to include address. Once registered, a Spanish guest's EUDI Wallet will work at a Finnish property and vice versa. For hotel groups operating across multiple countries, this is one registration process, not one per country.
Authbound provides the API and SDK layer connecting your property management system or check-in application to the EUDI Wallet infrastructure. We handle OpenID4VP session management, credential verification, and relying party integration. Contact us at [email protected] or visit authbound.io/book-a-meeting.
Waiting for the 2026 deadline might be a strategic mistake. Learn why integrating EUDI Wallet support early drives trust and conversion.
Spain now legally recognizes digital IDs as equal to physical ID cards. Here’s what it means for travelers, businesses, and the future of digital identity in Europe.
Selective disclosure is the privacy superpower of the EUDI Wallet. Learn how it works and why it builds user trust.
