When a Guest Is Refused Entry at the Border: Booking and Refund Rules
Compliance and Rules

When a Guest Is Refused Entry at the Border: Booking and Refund Rules

Localsbnb Editorial TeamSeptember 26, 20268 min read

A guest stopped at the border has neither cancelled nor checked in. The refund question turns on the channel's terms, the timing of the refusal and the evidence the guest can produce, while the host's job is to make the nights sellable again.

Screenshot of the LOCALSBNB single-channel detail page with a 'Rules that decide the refund' headline overlay, showing the channel's policy fields and connection state
The single-channel view shows the policy fields that apply to that booking, and whether the connection is live.

A guest turned away at immigration is a cancellation made by nobody. How it unwinds depends on the channel, the timing and what the guest can actually prove.

Last updated: September 27, 2026

A guest stopped at immigration doesn't cancel. They don't check in either. The booking just sits there, holding nights nobody will sleep in, and the money question doesn't settle itself. What happens next turns on three things: which channel the booking came through, when the refusal happened relative to check-in, and what the guest can actually put in front of that channel.

Key Takeaways

  • Nobody cancelled this booking. A border refusal isn't a guest cancellation or a host cancellation, so the usual policy ladder doesn't map cleanly.
  • The channel's terms decide. Refund and cancellation rules are set by each platform and by local rules, not by a general standard.
  • Evidence is the hinge. What the channel accepts as proof of refusal is what determines the outcome.
  • Some nights may still be chargeable. Which ones, and whether anything is, follows the channel's terms and your local authority.
  • Reset the calendar first. Turning held nights back into sellable nights is the host's own job, and it's time-sensitive.

Why this is not handled as an ordinary guest cancellation

Cancellation policies are built on a decision. Someone chooses to cancel, the timing of that choice sets the consequence, and both sides can see the choice. A border refusal breaks that model at the first step, because neither party decided anything. The guest tried to travel. You did nothing at all. The stay became impossible anyway.

That's why the usual ladder of flexible, moderate and strict doesn't give you an answer. It answers a different question. What you have instead is a case that the channel assesses on its own terms, and those terms vary by platform. Some treat a documented refusal close to a documented emergency. Some apply the policy as written and leave the guest to claim separately. Some have a defined process for requesting an exception, and some don't. Read the terms that apply to your booking rather than the ones you remember from a different platform.

Timing does most of the work. A refusal three weeks before arrival and a refusal at the gate on the arrival date land in different places, because the first still leaves you a chance to resell and the second doesn't. Note the actual moment the guest was refused, and note it in writing.

The regulatory background is moving too, which is worth watching even though it rarely changes a single refund. Clark County in Nevada is one place where the rules already bite: from 2 September 2026, platforms are barred from processing payments for unlicensed short-term rentals. That's in force. Further out, Washington DC's Bill 26-757, heard on 24 September 2026, would treat guests who overstay their contract as intruders, and Maui County's Bill 9 would phase out apartment short-term rentals in stages, with dates proposed for 31 December 2028 in West Maui and 31 December 2030 in South Maui. Both of those are proposals, still awaiting decisions. None of them tells you what to refund today, but all of them shape how channels write their terms.

The evidence a channel will actually accept

This is the part hosts get wrong, and it's the part that decides the money. A message saying "they wouldn't let me in" isn't evidence. Paperwork is.

Exactly what counts is set by the channel, so check its current requirements rather than guessing. What you can do is make sure the guest knows to keep and share whatever the border gave them, on the day it happened. A refusal record, a dated stamp and any accompanying document are the usual starting point. So is anything tying the guest to the booking: the travel document name matching the reservation, the flight or journey that was booked.

Two things help beyond the paper itself. Get it early, because a claim made while the dates are still in the future is easier to assess than one reconstructed a month later. And get it in the channel's own thread rather than by email, so the record of when you were told sits with the booking it concerns.

One caution about the guest's privacy. You'll be handling identity documents you didn't ask for and shouldn't keep longer than the claim needs. Ask for what the channel requires, keep it in the booking thread, and don't copy it anywhere else.

Card: the evidence that decides a refusal case, sorted into what the guest holds, what the channel requires and what the host must not keep
The outcome turns on paperwork filed in the booking thread, not on how the guest describes the refusal.
Card: the sequence for turning nights held by a refused booking back into sellable nights
The nights expire faster than the refund question resolves, so reopen the dates first.

What the host can still charge, and for which nights

Here's the honest answer: it depends on the channel's current terms and on local rules, and no general figure applies. Anyone quoting you a standard percentage or a standard number of days is describing one platform's habit, not a rule.

What you can do is organise your own facts so that whichever terms apply, you can apply them accurately. Separate the nights into three groups. Nights the guest could not use because the refusal happened before or on the arrival date. Nights the guest could have used but chose not to travel. And nights you managed to resell. Those three are treated differently under most policies, and mixing them into one number is how disputes start.

Then check what the channel's own policy fields say for that booking, rather than what you'd like them to say. The single-channel view shows the policy fields that apply and whether the connection is live, which matters when you're deciding whether a decision came from the platform or from your own settings. On the calendar, each connected channel shows its own source rate and source status, so you can see which nights are still held and which have already come back. Reading that before you promise a guest anything beats reconstructing it later. One read-only question returns the arrival, the in-stay guest and the departure, plus the reservation detail behind them, on localsbnb.com. Airbnb, Booking.com, Agoda and Trip.com bookings sit on the same grid, which is what makes the nights figure arguable.

One more thing that isn't about the money. Don't tie your response to how sympathetic the guest sounds. Follow the terms, document the dates, and be clear about what you can and can't do. A guest who's been refused entry is having a bad day, and a host who explains the process plainly leaves a better record than one who improvises.

Getting the calendar back to sellable quickly

The nights are the part you control, and they're the part that expires. A refusal that frees up a week in peak season is recoverable. The same refusal three days out usually isn't, so speed matters more than perfection.

Work in a fixed order. Confirm what the channel has decided, so you know whether the nights are released or still held. Unblock any dates the booking was holding once it's clear the stay isn't happening. Recheck your minimum stay and any arrival restrictions, because a week that was worth holding for a long booking may now be worth splitting. And if the dates are close, don't wait for the claim to finish before you reopen them.

Then tell the truth on the listing side. If a guest asks why a date opened up, you don't owe them the story, but you do owe them accuracy about availability. And if the refund question drags on, keep your own note of what you did on which day, because that's the record that protects you if it's reviewed.

LOCALSBNB — start free

FAQ

Is a refused guest entitled to a refund?

Entitlement depends on the channel's current terms and on local rules, and it isn't decided by a general standard. Some platforms treat a documented refusal as an extenuating circumstance, and some apply the policy as written. Check the terms attached to that specific booking.

What if the guest can't produce any paperwork?

Then you're dealing with an undocumented case, which most channels assess differently from a documented one. Ask the guest to request whatever record the border can provide, and see what the channel will accept before you make any commitment.

Should I cancel the booking myself?

Usually not. A host cancellation can carry its own consequences under the channel's terms, and it may remove the guest's route to a documented claim. Let the channel assess it, and keep the booking thread intact.

Speed is the host's advantage here, and the nights are what expire. Get the dates unblocked and the restrictions rechecked while the claim is still moving, and keep every note where the booking lives. Anyone tracking several channels at once can watch each one's status and source rate settle on localsbnb.com.


This article is general guidance for hosts and isn't legal or platform policy advice. Refund and cancellation outcomes are decided by the current terms of the channel that took the booking and by local rules, which differ by platform and by place; the regulatory items named here are dated and, where pending, marked as proposals.

Reviewed by

Localsbnb Editorial Team