Another check-in form
- Built for a single property and a single stay.
- Asks the guest to start over next time.
- Ends when that arrival ends.
For hotels
The hotel arrival,
reimagined.
One reusable identity for the traveler. A calmer arrival for the hotel.
In validation with hotels. Not a launched product.
The arrival, as it is
Every stay still starts from zero.
The guest repeats themselves. The desk repeats the work. The welcome waits.
Passports, at every property
The same identity document is requested, checked, and set aside — then requested again at the next hotel.
Data, entered again
Contact details, payment, and preferences are rebuilt from scratch for a stay the guest has already lived once.
A queue where the welcome should be
Registration piles up at the moment a guest most expects to be received, not processed.
Arrival, still unclear
Who is actually on the way, and when, is often settled only after they reach the desk.
The vision
One traveler. One identity. Many hotels.
IDTravelBox is exploring a universal digital identity and arrival layer for hospitality.
The long-term vision is a reusable traveler identity — verified ID, passport or identity data, contact details, payment credentials, and preferences — carried from one hotel to the next.
Imagine that identity established once. Each hotel the guest chooses could receive a secure arrival prepared for that stay, without asking either side to begin again.
Traveler
One person
The same guest, across however many hotels they choose.
Identity
Held once
Verified ID, contact, payment credentials, and preferences — designed to be reused, not retyped.
Stays
Many hotels
A city hotel, a second property, a group. Each keeps its own arrival.
The identity belongs to the traveler. The stay belongs to the hotel.
How it could work
An arrival, designed as a sequence.
A journey we are exploring with hotels. Not a flow you can switch on today.
- 01
Booking
A reservation already lives in the hotel’s own systems. The arrival is designed to begin from that booking, not from a blank form.
- 02
Secure hotel link
The guest could receive a link meant only for that stay — a private path from the booking to the hotel.
- 03
Verify identity
Identity could be confirmed against the reusable profile the guest holds, rather than reconstructed at the desk.
- 04
Registration
Digital registration could be prepared before the guest reaches the front office.
- 05
Payment or deposit
A deposit or payment could be taken the way the hotel requires, as part of preparing the arrival.
- 06Optional
Arrival and ETA
The property could see that a guest is on the way. Useful where the hotel wants that view — not assumed for every operation.
- 07Optional
Room ready
The guest could be told when the room is ready to receive them, so the arrival is a welcome rather than a wait.
- 08Where supported
Access
Where a hotel’s locks support it, digital access is a later possibility we are exploring. It is not a promise, and the arrival does not depend on it.
For hotels
Less administration. More of the welcome.
What a well-designed arrival layer could return to the property. No invented savings, and no claimed results.
Less front-desk administration
Fewer repeated document checks and retyped details at the moment of arrival.
Smoother arrivals
Registration designed to be ready before the guest is standing at the desk.
Clearer arrival visibility
A better sense of who is coming, before the door, where the hotel wants that view.
More time for hospitality
Minutes returned from processing, available for hosting.
A foundation for the guest journey
Groundwork for a digital arrival that can respect the systems a hotel already runs.
Why this is different
One identity. Many stays.
An online check-in form serves one property, once. The guest meets a new form at the next hotel.
A reusable identity
- Designed so the guest carries identity across hotels.
- Each hotel still owns the stay and the welcome.
- Meant for one property, and for a group.
IDTravelBox is being designed around that difference. It is not another form with a new logo.
Built to connect
Between the traveler and the hotel.
Our vision is an arrival layer that can sit between a guest’s reusable identity and the systems a hotel already uses.
Traveler
- Verified identity
- Contact
- Payment credentials
- Preferences
IDTravelBox
An identity and arrival layer, in design.
Hotel stack
- Property management
- Identity verification
- Payments
- Room management
- Digital locks
Conceptual only. No vendor is named, because no live integration is claimed.
Pilot
We are speaking with hotels before we build the wrong thing.
IDTravelBox is in validation. We are talking with owners, general managers, and operations leaders about how arrival actually works — the workflows, the friction, and what a pilot would need to respect.
We are inviting a limited number of hotels into that conversation. This is not a public launch, and it is not a finished product.
- How arrival works in your properties today
- Where identity, registration, and payment create work
- What a useful pilot would need to leave untouched