Hospitality

Guest registration and express check-in for hotels

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.

The problem

What teams do today

Most European jurisdictions make hotels register guest identity on arrival, which in practice means photocopying a passport at the front desk. It queues people at the busiest hour, it blocks mobile check-in, and it makes a hotel the custodian of travel documents it is not equipped to protect.

01
Registration finished before arrival, so check-in queues shrink
02
No passport photocopies in a drawer or a shared drive
03
A signed, timestamped record per stay for inspection
How it works

Three steps with Authbound

  1. Step 01

    Invite before arrival

    Your pre-stay email or app links straight into the flow, so registration finishes before the guest reaches the property.

  2. Step 02

    Collect what the statute names

    Usually name, date of birth and nationality. We request only what your jurisdiction requires.

  3. Step 03

    Release the key

    A verified result unlocks the mobile key and files a signed registration record.

Rules in play

National guest registration statutes, GDPR, eIDAS 2.0

Live demo

We built Northstay, a company that does not exist, to show this running inside a finished product. The wallet flow in it is the real SDK.

Open the Northstay demo
Questions

What people ask

Does this meet statutory registration requirements?
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.
What about guests from outside the EU?
They go through your existing desk process. Wallet check-in is an express lane for holders, not a replacement for the fallback.
Can this write into our PMS?
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.

Built on Authbound Identity Verification. One API key covers every flow you add later.