eIDAS 2.0 and the EU identity wallet: what it means for hotels

Europe is moving to verified digital identity all at once. eIDAS 2.0 sets the timeline, and the European identity wallet changes how every guest will prove who they are. For hotels, aparthotels and short-stay operators, that shift lands right at the front desk.

What is changing

Today, identifying a guest usually means a photocopied passport, a manual check, and a stack of sensitive data the operator now has to store and protect. Under eIDAS 2.0, a guest can instead present a verified, reusable digital identity from a wallet on their phone, through a simple and secure flow.

The benefit is real on both sides. The guest proves who they are in seconds, without handing over a document. The operator works with confirmed attributes rather than raw paperwork, which means less sensitive data to hold, not more.

The catch: becoming a relying party

There is a step most operators do not see coming. To request identity from a wallet, you have to be a registered relying party under eIDAS 2.0. That is a legal and technical role, not something a hotel sets up on a quiet afternoon.

This is exactly the kind of structural problem we build for. Guest OS is designed to handle the relying-party integration and registration on the operator's behalf, so a property can accept the EU identity wallet at check-in without building any of it themselves.

Why we build for it from the start

Software that bolts compliance on afterwards will have to be rebuilt when the wallet arrives. We are taking the opposite approach: we start with the regulation and design everything else around it. Guest OS is being built for verified digital identity from the first line of code, so that when the shift lands, operators are ready rather than scrambling.

If you run accommodations, build for hospitality, or work in digital identity, we would like to talk.