Guest Fraud Signals Before Check-In: A Factual Screening Checklist

Screening works on verifiable facts about the booking. The moment it turns on who the guest is, it stops being screening.

Last updated: September 29, 2026

Screening a booking and judging a person look similar from the outside and are completely different inside. One works on facts you can check in the reservation. The other works on assumptions about who someone is, and it's both unfair and unreliable. This checklist keeps the two apart: four signals that live inside the booking record, and a clear rule for what to do when one of them fires.

Key Takeaways

• Screen the booking, not the person. Every signal here is a fact about the reservation, not a guess about the guest.
• Four signals live in the order. Payment shape, booking window, name match and message pressure.
• A signal is a pause, not a verdict. It tells you to look closer, not to decide.
• Write down what you checked. A short note turns a hunch into a repeatable process and a defensible one.
• Keep the rule the same for every booking. Consistency is both fairer and a stronger position if you're ever challenged.

The line between screening and discrimination

Start with where the line sits, because it's easy to cross without meaning to. Screening asks what the booking shows. Discrimination asks who the guest is. Only one of those is something you're allowed to act on.

Protected characteristics are the dividing line. Nationality, race, religion, age, sex, language, family status and where someone lives are the kind of personal traits that anti-discrimination rules protect, and they're never a legitimate screening signal, however they feel in the moment. In many jurisdictions, including across the European Union, treating a booking differently because of those traits isn't a judgement call; it's a breach. That's not a reason to screen less carefully. It's a reason to aim every check at the booking rather than at the person.

The practical test is simple. If you can point to the specific field in the reservation that raised your concern, and you'd raise the same concern for any guest whose booking showed it, you're screening. If your concern only exists because of who the guest appears to be, you've crossed the line, and you'd be hard pressed to explain the difference to anyone who asked.

It also helps to know that the channel side is doing some of this work already. Across the European Union, short-term rental data-sharing rules have applied since 20 May 2026, requiring platforms to verify a registration number before a listing goes live. That's about your listing, not your guests, but it's a reminder that written, checkable process is the direction everything is moving. Your screening should be written down in the same spirit.

Signals that live in the booking record

The first two signals are the quietest, because they sit in the reservation itself and never announce themselves. Read them as shapes, not as verdicts.

Payment shape. Look at how the booking is being paid against how that channel normally behaves. A payment route that doesn't match the channel's usual pattern, repeated failed attempts followed by a switch to a different method, or a guest pushing hard to move payment off the platform, are all facts about the booking. None of them proves anything on its own. Together with other signals, they're a reason to look closer before check-in.

Booking window. Look at whether the timing is plausible for your property and your season. A same-night booking for a large group in a quiet week, or a long stay booked minutes before arrival, can be entirely legitimate. It can also be a sign that something about the reservation doesn't fit, so check it against what you actually offer.

Name match is the third, and it belongs in this section too. Does the name on the booking match the name that shows up at check-in, or the name on the payment? A mismatch is worth a question, not an accusation. Names vary with spelling, marriage, transliteration and booking-on-behalf, so treat it as something to confirm rather than something to reject. The point of the check is consistency within the record, not a judgment about the person behind it.

Run all three against the same booking and you get a shape. One signal on its own is noise. Two or three pointing the same way is worth a conversation. Neither outcome tells you who the guest is, and that's deliberate.

Signals that live in the message thread

Some of the clearest signals aren't in the booking fields at all. They're in how the conversation moves before check-in.

Watch the pressure, not the politeness. A guest who repeatedly pushes to bypass the platform's normal process is showing you a pattern. So is one who asks to confirm details off the record, resists any documented step, or wants the address released before the booking is settled. The pattern is the signal, not the tone. Plenty of anxious but perfectly honest guests ask a lot of questions; the thing to notice is pressure aimed at skipping a step, not curiosity aimed at understanding one.

Watch the inconsistency too. Details that change between messages, a story that shifts when you ask a follow-up, or answers that don't line up with what the booking already says are all worth noting. Write down the specific message, not a general impression. "Asked twice to move payment off the channel" is a fact you can act on and defend. "Felt off" isn't.

Then hold the two together. Booking-level signals and message-level signals are strongest when they agree, and weakest when you're forcing them to. A single odd message from an otherwise clean booking is usually just an odd message.

When something does line up, the move is to slow down and keep it documented. Record what you checked, where you saw it, and what you decided. Your booking data helps here, because each connected channel reports its own source status for the reservation, so you can confirm which channel a booking came from rather than relying on memory. Keeping that review contained is the same discipline: check the reservation at localsbnb.com, where guest details are masked by default and access is granted by area, so a closer look doesn't mean exposing more than you need.

What to do when a signal fires

A signal is a trigger for a process, not a decision about a person. Follow the same four steps every time, and the outcome takes care of itself.

First, pause and verify. Re-read the booking against the signal, and check whether the same fact would concern you on any booking, from any guest. If the answer is no, you're looking at a bias, not a signal.

Second, ask a specific, neutral question. Name the field, not the person. "I see the payment method changed after two attempts, can you confirm the card name for me?" is a booking question. Anything that asks a guest to explain who they are isn't.

Third, give the guest a clear, ordinary next step. Use the same process you'd use for anyone: the same ID step, the same deposit rule, the same arrival instructions. Routine is what keeps a legitimate guest from feeling singled out and keeps your process consistent.

Fourth, write it down. Date, signal, what you checked, what the guest said, what you decided. That note protects you if the same pattern appears again, and it's the record you'd want if your handling of a booking is ever questioned.

If the signals still don't resolve, don't make the guest the subject of the decision. Decline on the basis of the process, if you decline at all, and refer to the platform's own booking terms for anything that involves the channel. Then keep screening the next booking the same way, which is the whole point.

FAQ

What counts as a red flag?

A mismatch between the booking and the channel's normal pattern, checked against the same standard you'd apply to every guest. Payment shape, booking window, name consistency and pressure in the messages are all fair game, because all four are facts about the reservation. Anything based on who the guest appears to be isn't.

Can I ask a guest for ID?

Many hosts do, as part of a consistent check-in process applied to everyone. The rule that matters is evenness: the same step, asked the same way, for every booking. Whether you may ask, what you may retain and for how long also depend on local privacy rules, so check the current requirements where you operate.

What if a signal turns out to be nothing?

Then you've spent a few minutes on a booking that was fine, which is the normal cost of screening. The important part is that you checked the booking rather than the person, so a false alarm costs you a question, not a guest's dignity or a discrimination claim.

Should I tell the guest why I'm asking?

Keep it to the specific field, not to your suspicion. "I need the card name confirmed because the payment method changed" is honest and understandable. Explaining that a guest triggered a fraud check invites a conflict you don't need and tells them they've been profiled rather than verified.

Screening that stays on the booking is both more accurate and more defensible, because it turns a gut feeling into a written, repeatable check that applies to everyone equally. Keep the four signals in view, act on the booking rather than the person, and note what you did. Because that record depends on booking data staying contained, localsbnb.com is where the reservation and the channel behind it can be checked, with access granted by area.

---

This article is general guidance for hosts and isn't legal or fair-housing advice. What you may ask of a guest, what you may retain and what counts as discrimination are set by local and platform rules that differ by place and change over time; check the current requirements of your local authority and the current terms of every platform you use.