Chargebacks in Short-Term Rentals: How They Work, Why They're Rising, and What Hosts Can Do

A short-term rental chargeback usually arrives weeks after the guest has checked out. The stay went fine. The review was four stars. Then a notification appears in the host's payment dashboard: a disputed charge, the full booking amount withheld, and a short window to respond with evidence. Many hosts have never been through one before, and most lose the first one they fight.

Chargebacks themselves are not new. What is new is how many of them are landing in front of short-term rental hosts, and how much of the financial risk now sits with the property owner rather than the booking platform. Two shifts during 2025 — a steady migration of inventory toward direct-booking websites, and an update to Airbnb's payment terms that broadens host liability — have combined to make chargeback exposure one of the more consequential operational topics in vacation rental management heading into the 2026 summer season.

What a chargeback actually is

A chargeback is a reversal of a credit-card payment initiated by the cardholder's bank, not by the merchant. When a guest disputes a charge — claiming the card was used without authorization, that the service was never rendered, or that the property was not as described — the issuing bank pulls the funds back from the merchant's account while the dispute is investigated. The merchant has a limited window, typically seven to fourteen days, to submit evidence that the charge was legitimate.

In a vacation rental context, the merchant is whoever processed the payment. For a booking on Airbnb or Vrbo, that's the platform. For a direct booking, it's the host or the host's property management software, usually through a payment processor like Stripe.

Two categories drive most short-term rental chargebacks. The first is true fraud, in which someone uses a stolen card to book a stay; the cardholder spots the charge later and files a dispute. The second, and by far the more common, is what the payments industry calls "friendly fraud" — a guest who stayed, used the property, and then disputes the charge anyway, often citing a problem they never raised during the stay. Industry estimates put friendly fraud at roughly 42% of all short-term rental payment disputes.

Why the exposure has grown

For years, hosts who booked exclusively through Airbnb or Vrbo treated chargebacks as a platform problem. The OTA was the merchant of record, the OTA absorbed most chargeback losses, and the host's payout was generally final. That arrangement has shifted on both sides of the OTA-versus-direct decision.

On the platform side, Airbnb updated its payment terms in September 2025 to widen the circumstances under which a host can be charged back for a completed stay. Under the revised terms, a successful guest payment dispute can result in the disputed amount being clawed back from the host's future payouts, including in cases where the stay was uneventful and the review was positive. The cash-flow effect is immediate: Airbnb withdraws the funds first and resolves the dispute afterward. These changes sit alongside a broader wave of Airbnb policy shifts in 2024–2025 and updated damage-claim rules that have pushed more financial risk toward hosts. A separate update that took effect October 1, 2025 attached a mandatory 24-hour cancellation grace period to every booking under 28 nights, including reservations made under what had previously been the platform's Strict policy.

On the direct-booking side, the structural exposure has always been there — it just now affects more hosts. A host who accepts a direct booking through their own website is the merchant of record. Any dispute the guest files lands on the host's payment processor, and the burden of producing evidence falls on the host. There is no platform guarantee sitting behind the transaction. Hosts building that channel need the payment, verification, and documentation stack in place before the first reservation — the same baseline covered in what a direct booking site needs to accept its first reservation.

The combination is what has changed the operational picture. Hosts diversifying away from Airbnb to capture better margins outside the OTA fee stack inherit the merchant-of-record risk. Hosts who stay on Airbnb now carry more of that same risk than they did a year ago.

The evidence that wins disputes

Card networks evaluate chargeback disputes through a fairly standardized set of evidence categories. Hosts who win disputes generally do so by anticipating those categories and assembling the underlying records before a chargeback ever arrives.

For an "unauthorized transaction" claim, the strongest evidence is proof that the person who made the booking is the same person whose card was used. Identity-verification tools — services such as Stripe Identity, Superhog, or Autohost — collect a government ID and a selfie at the time of booking and match the name on the ID to the name on the card. Without that step, defending against a stolen-card claim is difficult.

For a "service not rendered" or "not as described" claim, the strongest evidence is documentation of the stay itself. A signed digital rental agreement, time-stamped guest communications, smart-lock entry logs showing the guest accessed the property, and any prior conversations about amenities or issues all become exhibits in a dispute file. Property management systems and channel managers have begun bundling these records into exportable "chargeback evidence packs" precisely because hosts are asking for them.

The other tool that materially changes the math is 3D Secure, a payment-authentication standard that requires the cardholder to verify the transaction through their bank, usually via a one-time code or banking app. When a payment is authenticated through 3D Secure, the liability for fraud-related chargebacks shifts from the merchant to the card issuer. The tradeoff is added friction at checkout, which can reduce conversion, but for high-value reservations the shift in liability is often worth it. Some direct-booking platforms now apply 3D Secure automatically above a configurable transaction threshold.

Where most hosts get caught

Three patterns turn up repeatedly in cases where hosts lose disputes they expected to win.

The first is name mismatches that go unchallenged at the time of booking. A reservation made by "Sarah K." but paid with a card belonging to "Marcus T." may not be fraudulent — couples and roommates pay for each other's trips all the time — but it complicates a dispute later, because the host cannot show that the cardholder authorized the charge. Asking for clarification at the time of booking, and recording the response, is a small step with meaningful protective value.

The second is missing rental agreements. Many hosts running a direct booking site rely on the terms of service printed on the checkout page and never collect a signature. In a dispute, a separately signed agreement that the guest read and accepted is materially stronger evidence than a footer on a confirmation screen.

The third is the absence of access logs. Smart locks that record entry events — and that issue a unique code to each guest — produce a record that the booked guest actually entered the property. Without that, a "service not rendered" claim can be difficult to rebut, especially if the host used a shared lockbox code that anyone could have used.

A note on cancellations and "item not received"

Not every chargeback originates as fraud. A subset of disputes come from guests who cancelled, expected a refund under a flexible policy, and filed a chargeback when they didn't get one quickly enough. From the issuing bank's perspective, this often gets categorized as "item not received." The defense isn't an identity-verification record — it's a clear, accessible cancellation policy that the guest agreed to, paired with documentation of how the host applied it.

For direct bookings, that argues for a cancellation policy that is short, plainly written, and surfaced both on the booking page and in the confirmation email. For Airbnb reservations, the October 2025 grace period now overrides stricter cancellation terms within the first 24 hours, which has reduced the volume of these disputes inside the window but has not eliminated them outside it.

The decision context

For most hosts, the goal is not to eliminate chargebacks — that is not realistic — but to make them rare and winnable. The baseline that property managers have converged on includes identity verification on every direct booking, 3D Secure enabled at a sensible transaction threshold, a separate digital rental agreement with an explicit signature step, smart-lock access with unique guest codes, and a habit of preserving guest messages and timestamps in a single retrievable place.

Each step adds a little friction to the booking flow. For low-priced one-night stays from familiar markets, the friction may not be worth the protection. For multi-night, high-value reservations — especially during peak weeks, holidays, or large events when fraudulent bookings spike — the protection is usually worth more than the marginal lift in conversion friction.

The underlying point is that chargebacks have moved from a fringe concern to an operational cost line that hosts need to plan for. The platforms have stopped absorbing as much of the risk. The hosts who fare best are the ones who have decided, in advance, what their dispute evidence file looks like — before they need to assemble it under deadline.

Sources

• Short-Term Rental Chargebacks and Fraud Prevention — RedAwning
• New Airbnb Chargeback Policy = More Risk for Hosts — The Host Co
• Airbnb 2025 Policy Changes and How PMS Platforms Must Adapt — Autohost
• How does 3D Secure authentication work? — Stripe
• Protect Your Vacation Rental from Bad Guests (2026 Guide) — Now I Stay