Collect statutory guest registration before arrival, without a passport photocopy.
Today
With the EUDI Wallet
The wallet changes how the evidence is collected. The step at the end stays yours.
Why the wallet helps
The guest sends the registration attributes from their wallet before they arrive. You get name, date of birth and nationality signed by the issuing state, file the statutory record, and release the room key. The desk becomes optional.
01
You request specific attributes
02
The user gets the request by QR or deep link
03
The wallet shows exactly what is asked
04
The user approves on their device
05
The wallet presents the signed credential
06
Authbound verifies the presentation
07
Your backend receives a structured result
08
Your existing workflow continues
Step 01
Your pre-stay email or app links straight into the flow, so registration finishes before the guest reaches the property.
Step 02
Usually name, date of birth and nationality. We request only what your jurisdiction requires.
Step 03
A verified result unlocks the mobile key and files a signed registration record.
Technical flow
const verification = await authbound.verifications.create({
policyId: 'pol_…', // the claims this flow requests
customerUserRef: user.id,
});
// Your webhook then receives verification.completed
// with the verified result and its audit record.Wallet presents
Terms to know
Regulatory context
National guest registration statutes, GDPR, eIDAS 2.0
Guest registration is set by national law, which defines the fields, the retention period and how records reach the authorities. Wallet attributes are signed by the issuing state and can fill the same fields. Submitting registrations to the authorities and deleting them on time remain your responsibility.
Hotel express check-in that satisfies guest-registration rules in one scan.
What it asks the wallet for
What the business gets back
Northstay is a fictional company built by Authbound. The wallet integration in it uses the real Authbound SDK.
You get the same attributes a photocopy would give you, signed by the issuing authority, with a verification record attached. Registration rules are national, so check the required fields and retention period per market.
They go through your existing desk process. Wallet check-in is an express lane for holders, not a replacement for the fallback.
The verified attributes come back over a normal API call and webhook, so they land in a guest profile the same way any other check-in source does.
Yes. The wallet adds an express lane in front of it and the desk stays as the fallback.
The registration attributes your jurisdiction requires, such as name, date of birth and nationality, plus a verification ID you can store with the stay record.
No. Guests without one use the desk. The more guests use the wallet, the shorter the queue gets for everyone else.
Each adult guest presents from their own wallet. Rules for children and accompanied guests are national, so check what your market requires.
Yes. Every EU wallet is verified the same way, which is most of the point for hotels that host cross-border travellers.
Every member state has to offer a wallet by 24 December 2026. Private services that are legally or contractually required to use strong user authentication have to accept it from December 2027 when the user asks. Expect early adopters first and broad use later.
As long as your national statute requires and no longer. You keep the verified fields and the verification record rather than a passport copy.
Banking & fintech
The same verify integration, applied to KYC.
iGaming
The same verify integration, applied to age verification.
E-commerce
The same verify integration, applied to age verification.
Built on Authbound Identity Verification. One API key covers every flow you add later.
Tell us what you are trying to build. We will map the user journey, the credentials and the wallet interaction to an implementation.