When a guest finishes check-in, Regi offers them a PDF receipt. Until now that PDF carried everything: each traveller’s ID, support number, date of birth, nationality, phone, email and the payment details.
That PDF ends up in a phone’s downloads folder, forwarded on WhatsApp to whoever organised the trip, or printed at the front desk of some other place. And the check-in link kept showing the same data to anyone who opened it later, even after the check-in was finished.
Both have changed. This round on guest check-in also brings several smaller fixes to the form, and a correction to something we wrote a few weeks ago.
The receipt becomes a ticket
What the guest downloads at the end is now a small ticket. It has:
- the reference of the traveller report,
- the check-in and check-out dates,
- the number of guests,
- the property name,
- a QR code, a button and the link to open that check-in in Regi.
It has nobody’s name, no IDs, no dates of birth, no phone numbers, no emails and nothing about how they paid. The footer says what it is: proof that the guest completed their details, not an official registration document.
What this changes for you: if that PDF gets forwarded, printed or left on a shared computer, it no longer exposes anyone. The guest still has proof that they checked in, which is what they wanted it for.
The QR code takes you to the report
The QR code on the ticket opens that stay’s traveller report in Regi. If a guest shows you the ticket at the door, you scan it with your phone and land on the report without looking for it in the list.
If you are not signed in, Regi asks you to sign in and then takes you to that report. Someone without access to your account stays on that sign-in screen, and if they sign in to another account they get a “not found” page. The code does not reveal whether that report exists.
A finished link shows nobody’s data
The check-in link lets the guest fill in their details and come back to the confirmation screen whenever they like. That is why it keeps working after the check-in is done.
What has changed is what it shows. Once the check-in is finished, the link shows the confirmation and the number of guests, and nothing else. The travellers, their relationships and the payment details are no longer visible to whoever opens that link.
On completion, the payment holder and the card expiry date are also deleted from the draft. The traveller report keeps them: what goes to SES.Hospedajes does not change at all.
This matters because links get forwarded very easily. The guest passes it to the people travelling with them, you paste it into a message, it sits in a chat history. Now, whoever opens it later only sees that the check-in is done.
Dates more than a year old no longer go through
A few weeks ago we wrote that stay dates were accepted up to three years back. That is no longer true, and it was not our call: SES.Hospedajes has stopped accepting a check-in more than a year old.
Regi now applies the same limit in three places:
- in the guest’s form,
- in a half-finished draft,
- and when you change the check-in date of a report.
The same day last year is refused too. That leaves a day for the report to reach SES.Hospedajes before the date runs out. The day is counted in Spanish time, including for a guest filling in the form from abroad close to midnight.
If a link arrives with fixed dates that are already past the year, or a draft has grown too old, the form says so when it opens. Before, the guest found a disabled button and no explanation.
On an older report you can still correct everything else. The limit only applies when you change the check-in date. Nothing changes going forward: stays up to three years from today are still accepted.
Form fixes
None of these is a new feature. Each one was a place where a guest could get stuck.
Typing a date quickly no longer swallows digits. Dates are typed into three boxes: day, month and year. When one was filled, the cursor jumped to the next a moment too late. If the guest typed fast, or tapped quickly on a phone, a digit landed in the box they had already left. The card expiry date had the same problem. Now the jump happens with the keystroke.
An extra space no longer breaks a number. If the guest pasted their ID number with a space at the end, the form said it was too long. Now Regi removes spaces at the start and end of every text field before checking and saving it. The same goes for your own property and report forms.
Chrome no longer closes the tab at the contact step. In desktop Chrome, if the browser offered to autofill the phone number and the suggestion went away on its own, the tab crashed and the guest had to start that step again. That no longer happens.
A reservation’s dates no longer leak into another visit. When you copy the link from a reservation, the dates arrive filled in. If the same guest later opened the property’s general link in the same browser, those dates could reappear. Now dates that came from a reservation are no longer kept for the next visit. What the guest typed themselves, their own dates or a number of travellers changed by hand, is still remembered, as before.
Editing a saved traveller is clearer. When a guest goes back to a traveller to correct it, the details show as a list with dividers instead of cards. Only a section with something missing turns red, never a value that is filled in correctly. And the ID number field appears once a document type has been chosen.
The travellers panel keeps its header in view. On phones, the panel that slides up from the bottom to add a traveller could scroll a little and push its title and close button off the screen. Now it stays put.
What it does not do
- It does not delete receipts already downloaded. A PDF a guest saved before this change is still on their phone with all its data. Regi cannot recall it.
- The ticket does not replace the traveller report. It is not an official registration document and means nothing to SES.Hospedajes. You have the full report in Regi, as always.
- The QR code opens nothing without your session. If you scan the ticket on a phone where you are not signed in to Regi, you will need to sign in first. You then land on the report without scanning again.
- In Japanese, Chinese and Arabic the ticket prints in English. The guest’s screen stays in their language, but the PDF cannot draw those scripts, so it prints in English instead of empty boxes.
- It does not accept stays more than a year old. If you have a pending report for a stay older than that limit, SES.Hospedajes no longer accepts it, from Regi or from anywhere else.
How we handle your guests’ data in general, what is kept and for how long, is in your guests’ data and privacy. The previous round of check-in fixes is in fewer places to get stuck, and the latest addition to the form in guests scan their ID.