What Almost Losing $700 on Airbnb Taught Me About Booking Low-Friction Stays
I’ve used Airbnb for years, across dozens of countries. Most of the time, it works — until it doesn’t.
In Lima, our 2.5-week Airbnb stay fell apart the day before check-in after a document deadline that had not been clearly communicated in the message thread turned into a building access problem, and then into a cancellation dispute that nearly cost us $700. I eventually got the money back through a bank dispute, but only after hours of support messages that left the core issue unresolved, a last-minute replacement booking, and a stressful start to the trip before we had even arrived.
This is not meant to be a vent (though it would’ve been cathartic at the time). It’s an attempt to turn a disempowering travel situation into something useful: what happened, what I learned, and how I’m changing the way I book accommodation so one bad stay is less likely to take over the trip.
The booking problem that almost cost us $700
We booked a 2.5-week Airbnb stay in Lima, Peru.
Shortly after booking, the host messaged us asking for passport photos for building registration. That part didn’t seem unusual — in some countries, buildings or local authorities may require guest registration, especially for foreign travelers.
We responded that we’d send the documents closer to the check-in date.
The host replied, “Perfect.”
No deadline was mentioned in the chat. No warning, no “please send these at least 24 hours before arrival.” Nothing that made it clear this was a strict access requirement.
The day before check-in, the host reminded us to send the passport documents. By that point, the 24-hour deadline they later relied on had actually already passed. We sent them right away. The host thanked us and then sent check-in instructions.
So at that point, it seemed like everything was fine.
Then, shortly after sending the check-in instructions, the host messaged again and said they could not generate the building access code because the passport documents had been submitted too late. When we asked what that meant in practical terms, they pointed to the 24-hour deadline in the listing’s additional house rules and told us we would not be able to enter the building. What made that part of the exchange feel almost absurd was the tone: the host continued using casual emojis during the access-code discussion, even as we were being told we could not enter a reservation we had paid for and were supposed to check into the next day.
Then, they said the reservation would need to be canceled “in the guest’s name.” In other words, they were asking us to cancel the reservation ourselves and lose the $694.60 we had paid.
So even though we were still ready to check in, and even though they were the ones saying building access could not be generated, they were asking us to be the ones to cancel. That would have made it look like we had chosen not to stay there and willingly given up the full cost.
To be clear, the deadline did exist in the additional house rules. But if the deadline was truly strict, it should have been communicated clearly when they first asked for the documents, especially after we said we’d send them closer to the date. Instead, the host replied positively, reminded us the day before check-in after the deadline had passed, thanked us for the documents, sent check-in instructions, and only then treated the timing as a reason we could not enter.
To me, that is what turned this from a missed rule into an access issue that was being handled as if we had chosen not to stay. This did not start as us trying to back out of the stay. We were being told we couldn’t get into the building after we had complied with their document requests, and then being asked to cancel as if we had chosen not to come.
What happened with Airbnb Support
I reached out to Airbnb Support right away.
Over 8 hours (from about 6pm to 2am, the night before we were supposed to board our flight) I spoke with two support specialists and one senior case manager. Each time, the response came back to the host’s house rules: because there was a 24-hour document deadline listed there, Airbnb treated the host’s position as valid.
But at the time I checked Airbnb’s help pages, the guidance seemed directly relevant here. Airbnb says that if a host says they can’t accommodate your reservation anymore, guests should not cancel for them. Airbnb’s Host Cancellation Policy for homes also says that if a host cannot honor a reservation, regardless of the reason, it is the host’s responsibility to cancel, and that a host may not encourage the guest to cancel the reservation. I cited these pages in the support chat, but they were not clearly addressed in relation to our case.
Support also did not meaningfully address the message timeline. The host had thanked us for the documents after we sent them, sent check-in instructions, and only after they could not generate building access said the documents were too late. At some point during the support exchange, I did say I no longer felt comfortable staying there. That discomfort came from how the host had handled the access issue and cancellation request. When I asked Airbnb to intervene, I was asking them to treat the situation as a host cancellation with a refund, not to process a non-refundable cancellation against us.
The senior case manager did acknowledge that the host could have communicated the ID requirement more clearly, but the final decision still came back to the house rule. In the same review, they also referenced “local law in Spain,” even though the reservation was in Peru. They later apologized and clarified that the Spain reference was a mistake. I appreciated the correction, but from my side, it still made it harder to trust that the case had been reviewed carefully in the moment.
By the end of the back-and-forth, Airbnb had closed the case, accepted the host’s position, and offered no refund.
The next day, after landing in Peru, I saw that Airbnb had processed the cancellation without a refund, citing a violation of the host’s house rules. I had not asked Airbnb to process that kind of cancellation, and I was not asked to confirm that specific outcome before it was processed. In practical terms, the final outcome was treated like a guest-side cancellation: the reservation was canceled, the host’s cancellation policy was applied, and the refund was listed as $0.
That distinction mattered. Airbnb’s Host Cancellation Policy says host cancellations can come with consequences, including cancellation fees and blocked calendar dates. But when a guest cancels, Airbnb’s host-facing guidance says the dates are automatically unblocked, meaning the host may be able to accept another booking.
Why this changed how I think about accommodation
I did eventually recover the money through a bank dispute (with very careful documentation). But by that point, we had already spent hours dealing with support, booked (and spent more) on a last-minute replacement stay, and started the trip stressed before we had even arrived.
I don’t think every accommodation problem means someone is acting maliciously. Mistakes happen. Rules can be unclear. Buildings can have their own registration systems. Support agents may be working within limited procedures.
But this experience made me much less willing to assume that a platform will protect guests just because the situation seems obvious from the guest side. From my perspective, the host’s reliance on the deadline shifted responsibility for what felt like an access problem, and Airbnb’s handling of the case ended up supporting that outcome.
That is what made the situation feel so disempowering. It was not just the last-minute scramble to book somewhere else. It was the stress of trying to solve the problem for hours while preparing to board an international flight, and realizing that a platform I had used almost a hundred times was not necessarily going to protect me when something went wrong.
After this experience, I’m much more careful about the hidden friction points inside a booking: document deadlines, building access systems, strict house rules, cancellation handling, and how clearly the host communicates anything that could affect check-in.
A place can look nice, be well located, and have strong ratings, but it can still create a huge amount of friction if the check-in system is fragile, the rules are easy to miss, or the host does not communicate strict requirements directly.
What I’ll check before booking from now on
Here are things that I now do and keep in mind to protect myself when booking on Airbnb (and any other housing platform really). I’ve also written a broader guide to Airbnb tips I’ve learned from 100+ stays, but this experience made the access, documentation, and cancellation side feel much more urgent.
1. Read every part of the listing, including the additional house rules
I used to read the main listing, reviews, cancellation policy, location, and main house rules, then rely on the host’s messages for any important logistics. And for the vast majority of stays, that worked fine. If a host had specific or strict requirements, they usually communicated them directly.
I don’t assume that anymore.
Now, I read the full listing in detail before booking, including the additional house rules. If there are any strict requirements hidden there — ID deadlines, registration rules, check-in windows, extra fees, any restrictions — I want to know before I commit.
This is partly about avoiding situations like this one. But it’s also about reading the tone of the listing.
If a host has a long list of strict rules, unclear penalties, or requirements that feel easy to miss, that tells me something. It may still be a legitimate stay, but it may not be the kind of low-friction stay I want. Knowing it beforehand lets me decide whether I want to deal with all the rules or not.
2. Ask the host to confirm strict requirements in writing
If I see any requirement or restriction that could affect check-in, I’ll ask the host to confirm it in writing before the trip.
For example:
“Hi! I saw the note about [ID/building registration/check-in deadline]. Just confirming what needs to be submitted, when it needs to be submitted by, and whether there is anything else required for check in.”
This creates a clearer paper trail. It also gives the host a chance to surface anything important before it becomes urgent.
3. Don’t make it look like you initiated the cancellation
If the host is the one saying they cannot accommodate you or give you access to the stay, don’t cancel the reservation yourself — even if the host refuses to cancel, support is not helping, and you’re under pressure to book somewhere else.
Airbnb’s own guidance says that if a host tells you they can’t accommodate your reservation, guests should not cancel for them. The person who cannot honor the reservation should be the one to cancel.
This distinction matters because the record can affect what happens next. If you cancel yourself, Airbnb or your bank may treat the situation as a guest-initiated cancellation, even if you only did it because the host said you could not access the stay. That can weaken your refund request, your support case, and any later attempt to dispute the charge.
In my case, I did not cancel for the host. But the experience still made this point very clear: when a host says you cannot stay, keep the record as clean as possible. Put it in writing that you are not choosing to cancel — you are being told you cannot access a stay you paid for.
4. Keep the conversation on-platform, then screenshot everything
When a situation starts to go sideways, documentation matters.
Always keep your conversation with the host inside Airbnb. If a host makes a request, changes the check-in terms, says you cannot access the stay, or asks you to cancel, you want that written in the platform thread instead of buried in WhatsApp, text messages, or a phone call. That way, Airbnb can see the same record you are referencing, and the host cannot later say the exchange happened differently or outside the platform.
Then screenshot everything for your own backup: the host’s messages, the listing rules, the check-in instructions, and the support conversations. Having a copy on your end helps if messages become harder to find or somehow deleted, the listing changes, or you need to explain the timeline to someone outside Airbnb.
I know this sounds excessive, but when you’re trying to explain a timeline to support, your bank, or anyone else, a clean paper trail helps. In my bank dispute, having the key screenshots already organized made it much easier to show what happened.
5. Professional-looking doesn’t always mean professionally handled
A polished listing, strong ratings, a managed-property feel, or even a platform badge (such as Airbnb’s Superhost badge) can all be useful signals. But none of them guarantee that the stay will actually be lower-friction.
Some of my best Airbnb experiences have actually been in slightly less “professional” looking homes, run by hosts who only manage one or two properties. That can come with its own risks, of course, but I’ve also had some of the most thoughtful communication and care from hosts like that.
On the other hand, a polished listing or company-run setup does not automatically mean the stay will be smoother. The listing from this stay looked polished and appeared to be managed by a team, but the building access process did not seem to be handled with the same level of clarity that the listing presentation suggested.
So now I pay much more attention to how the listing and host actually communicate, not just how professional the page looks. I put more weight on the reviews themselves, especially the lower-rated ones, because that’s where check-in problems, strict rules, surprise fees, and communication issues are more likely to show up. Strong ratings can tell you what happens when things go smoothly. Lower-rated reviews can show you what happens when they don’t.
I also pay attention to the tone of the host’s review responses. If they seem defensive or dismissive with past guests, that tells me something. Even if the listing has strong ratings overall, I’d rather book a place where the host seems clear and reasonable when things do not go perfectly.
Final thoughts
I still use Airbnb a lot because it can be cheaper, I’m familiar with the platform, and it often has the kind of stay I need. But I’m much less casual about it now and make sure to do the checklist above before I book.
I’m also trying to compare alternatives more often instead of defaulting to Airbnb automatically. Depending on the trip, that might mean hotels, hostels, Booking.com, Agoda, longer-stay platforms, or smaller local accommodation options. I haven’t seriously tested every alternative platform yet, but I’m trying to consider more options where I can.
This also ties into my existing discomfort with large-scale, corporate-style short-term rentals, especially listings run by hosts or management companies with many units. The relationship between short-term rentals and housing is complicated and varies by city, but there is research suggesting that short-term rental growth can affect long-term housing supply and affordability in some markets.
That concern did not start with this one bad booking. But after this experience, I’m more hesitant to book polished, company-run Airbnbs when a hotel, hostel, or locally run stay makes sense.
I did get the money back in the end, but only after a bank dispute with careful documentation and a good amount of stress and frustration. For me, low-friction travel is not about assuming nothing will go wrong. It is about noticing where things are most likely to break, reducing the avoidable risks, and keeping enough documentation and flexibility that one bad accommodation problem does not take over the whole trip.
Thanks for reading — happy planning, and here’s to fewer booking surprises.
Have a question about this?
Shoot me a message or leave a comment below — I read everything, and I’m always happy to help if I can!
