The most legitimate check-in request is the one that looks like a scam

A legitimate request can still look suspicious when it arrives without context.

Registering guests is a serious requirement in many destinations. The problem is that, from the guest's side, it often arrives in the exact shape they have learned to distrust: a link, a form, personal data, a document upload, sometimes a chat message from a number they have never seen before.

The host thinks: this is required.

The guest thinks: is this safe?

That is where the friction begins.

A legitimate request can still look suspicious

A guest books an apartment in Rome. A few days before arrival, they receive an online check-in form: name, surname, date of birth, nationality, document details. So far, the procedure makes sense.

Then the form asks for a document image. The guest hesitates. Then it asks for a photo of the guest holding the open passport.

At that point, the guest is not being difficult. They are asking a reasonable question: is this a real procedure, or is someone trying to obtain my identity document?

The goal is not to force guests to trust blindly. The goal is to stop making them guess.

The law may require data. Context makes the request credible

In Italy, accommodation providers must communicate guest identification data to the local public security authority through Alloggiati Web within the required deadlines. But that does not make every document request automatically clear, and it does not turn the identity document into an ordinary attachment.

For the host, this is an administrative step. For the guest, it involves one of the most sensitive documents they own.

Remove the context, and only the shape remains: a link asking for a document. That shape looks very close to phishing.

A document and a selfie with a document are not the same thing

It is important to separate what is legally required from what is an additional procedure chosen by the property or by a technology provider.

For official guest registration, identification data and document details are required. If an image of the document is collected, it should be limited to what is strictly necessary for the process and must not become long-term storage.

A photo of the guest holding the document is different. It is an additional identity or presence check. It may have a logic in some flows, but it should not be presented as if it were automatically the same legal requirement as guest registration.

If a property asks for more than the law strictly requires, it needs to explain it even more clearly: why it is asking, where the data goes, how long it is kept, who processes it, and what happens after that.

The channel speaks before the text

For document requests, the channel is part of the message.

A form opened inside a recognizable stay space, with the property name, the guest's language, the reason for the request and a visible privacy notice, says: this is a procedure.

The same form sent as a bare WhatsApp link from an unknown number says: be careful.

Guests are not auditing the technical security of the system. They cannot. They are reading surface signals: where the request comes from, how it looks, whether the reason is explained, whether the space matches the property they booked.

The line that is almost always missing

Many online check-in forms do not fail because they are long. They fail because they do not explain the reason at the point of the request.

One line can change the tone:

Local rules require us to submit guest identification data to the public security authority. The data is used only for this purpose, and any document images are not kept beyond the time necessary to complete the communication.

This is not a full legal notice. It is the bridge between obligation and trust.

The guest does not need to become an expert in Italian regulation. They need to understand why the request exists and why it comes from a legitimate context.

What happens when the guest hesitates

A guest who does not trust the request often does not refuse. They delay.

Then the host sends a reminder. Then another. The form is completed late, sometimes at arrival, when the guest just wants to get inside and put the luggage down. The first real interaction of the stay becomes a discussion about an identity document.

The request was legitimate. The way it arrived made it look suspicious.

How StayFast works

In StayFast Flow, document collection should be part of the guest's stay space, not an isolated link.

The request appears inside a recognizable digital path: the same environment where the guest finds arrival information, instructions, hours and useful content. The reason for the request is written next to the field, in the guest's language. Documents should not travel through personal chats, photo galleries or disorganized forwarding.

This does not replace Alloggiati Web, the public authority, a privacy advisor or local regulation. It makes the step more readable, more orderly and less suspicious for the person receiving it.

Flow should not be sold as a legal shortcut. It should be the orderly place where a necessary procedure stops looking like a scam.

Where to actually start

• Add a short explanation before the document request. Not after, not only inside a long privacy notice: before.
• Avoid WhatsApp or personal chats to collect document images.
• If you ask for a selfie with a document, explain it as an additional measure of yours or of the system, not as a generic legal obligation.
• Say clearly what is used, for which purpose, and what is deleted after the required communication.
• Put the request inside a recognizable stay path, not in a bare link.

The rule that avoids almost every mistake

Before asking a guest for a document, ask yourself one question: if I received this link from a stranger, would I open it?

If the answer is no, the problem is not the guest's distrust. It is the way the request presents itself.

Conclusion

Guest registration is one of the least negotiable steps in the stay. That is exactly why it must be one of the clearest.

When you ask for a document without context, the guest sees risk. When you explain the reason, the channel and the handling, they see a procedure.

The difference is often one line, written in the right place.