When travel restrictions vary by nationality, knowing a guest can actually check in matters as much as knowing they have a room. Why rePUSHTI added it as a re-verification parameter.
Different countries handled travel restrictions differently — some opening their borders to foreign tourists, others restricting entry to certain regions or vaccination statuses. For a guest whose nationality falls on the wrong side of a hotel's protocol, the result could be arriving in a foreign country and being turned away at the desk.
Why nationality matters to a booking
A traveller needs to know, before they fly, whether they'll actually be allowed to stay at the hotel they've booked. If a hotel declines to service a guest from a restricted region on arrival, that guest has no time left to make other plans.
How rePUSHTI helps
rePUSHTI already re-verifies 50+ parameters per booking — passenger, hotel and operational details among them. Traveller nationality became one more: shared with hotel staff during re-verification, so the property can confirm upfront whether it can service that passenger, and what's needed (a vaccination record, a test result) if so.
Why the step matters
Every online booking passes through more than one system, and nationality can get lost between them:
- A traveller shares their nationality with the first supplier, who doesn't pass the full detail to the next one — the booking gets confirmed anyway, and the mismatch surfaces only once cancellation fees are already in play
- A traveller booking directly misses the fine print on a restriction themselves, with the same result
Re-verifying nationality closes that gap before it becomes an unnecessary retention charge or a guest turned away at the door.
