Hotel Deposit Chargebacks: Advance Payments, Cancellations and Refund Evidence

A hotel deposit chargeback is a dispute over money a guest paid before the stay. Your reply should show the captured deposit, the booking, what happened to the stay and any refund. A “nonrefundable” label alone does not answer a service or refund claim.

The hotel chargeback workflow covers the wider process. The travel pillar covers agencies and split payments.

Identify the Hotel Deposit Payment Event

Start with the processor record. Tell four events apart: the hold, the capture, the release and the refund. Each one leaves a different trail.

• Booking guarantee: it saves the room. It may not collect any money.
• Hold: it sets funds aside for a short time. No money moves until you capture it.
• Captured deposit: this is money you actually took for the booking.

These labels decide which money events you can match later.

Save the payment ID, amount, currency, capture date and booking link. Did one person pay the deposit and someone else pay the balance? Then keep both payers and both charge references. Do not use the folio’s net total in place of each payment’s history.

Hold timing matters too. A hold placed weeks before arrival can run out. When it does, the funds go back and nothing is captured. So check that money was really captured before you call a hold a deposit.

The Visa rules information treats some guaranteed bookings differently from normal payments. Confirm the payment and booking terms with your acquirer. Calling a payment a “deposit” does not set its processing type. It does not set the guest’s duties either.

Preserve the Deposit Agreement for This Booking

Find the stay dates, price, deposit amount, cancellation terms and refund terms. Note how each one was shown to the guest. Save the confirmation for this booking and any changes to it. A group contract, an OTA rate and a direct offer may each carry different terms.

Was the deposit part of the room price, or was it for something else? If you later apply it to the folio, show that step clearly. Then finance will not count it as a second payment. If the guest disputes the amount, compare the final capture with the terms you first agreed.

Keep later exceptions and refund promises. A fix a manager approved still counts, even when the policy was stricter. Do not present the booking terms as if no later deal or service failure took place.

Show the Total Price and Deposit Terms Up Front

In the U.S., the FTC’s Rule on Unfair or Deceptive Fees took effect on May 12, 2025. It covers short-term lodging. That includes hotels, vacation rentals, booking platforms and travel agents.

The rule says you must show the total price up front. That total must include every mandatory fee you can work out at the time. If you say whether a fee is refundable, that claim must be true.

This ties straight into disputes. A guest who saw one price and paid another has a clear complaint. Clear and accurate deposit terms at booking are also your best evidence.

For general policy limits, see Chargeflow’s no-refund policy guide. This article focuses on the booking’s payment events and the proof that links them.

Classify What Happened After the Advance Payment

Record what happened next. Did the guest stay, or cancel? Did the property cancel, or did the dates change? Or is the booking still open?

Then name the guest’s real claim. It may be a payment they say they did not make. It may be a room that was not there, a wrong amount kept or a refund that never came.

This table is a map for your review. It does not decide if you may keep the money. It also does not decide if an offered option settles the complaint. If the property canceled the room, a nonrefundable rate is not a full answer.

Reason Codes Behind Hotel Deposit Chargebacks

The reason code tells you which claim to answer. Most deposit disputes land in a few codes. Stripe groups them as “credit not processed,” “product unacceptable” or “fraudulent.”

Amex even has codes that name lodging deposits, such as C18 and 170. Read the code before you build the packet. A fraud code needs proof that the cardholder made the booking. A refund code needs proof about the money.

For a “credit not processed” code, Stripe lists three ways to respond:

• Show you already gave the refund the guest was owed.
• Show the guest is not owed a refund.
• Show the guest withdrew the dispute.

Worked Ledger: A Partly Refunded Advance Deposit

Hypothetical example; taxes and fees are excluded. Booking A-520 has a $900 stay price. The merchant captured a $300 deposit, P-521. The other $600 was due later and was never collected. The booking is canceled. The merchant then completes a $180 refund against P-521. Later, the guest disputes the full $300 payment.

After the refund, $120 of captured funds is left, before any dispute movement. That does not prove the merchant may keep $120. The reply still needs the booking terms, the cancellation facts, the service status and any later deal that backs the position.

The uncollected $600 is not money lost to this chargeback. It may matter for the booking history or for accounting. But do not add it to the $300 in dispute. And do not call the $180 refund a recovered chargeback amount.

The case owner should send the refund proof through the allowed workflow. Explain what is still in dispute. Do not send another $300 refund without checking the open case and the $180 credit. Support and payments should work from the same ledger.

Hotel Deposit Chargebacks Need a Refund Status Trail

Log the refund request, approval, submission and completion as separate events. Keep failures, reversals and retries too. A support note saying “we refunded you” may be wrong if the payment failed. Check the processor status instead of repeating the note as proof.

How Long a Hotel Deposit Refund Takes

Many guests ask how long a hotel deposit refund takes before they call their bank. Stripe says a card refund shows up as a credit in about 5 to 10 business days. It depends on the bank.

A refund sent soon after the charge may post as a reversal. Then the charge simply drops off the statement, with no separate credit.

A missing credit often leads to a “credit not processed” dispute. So give the guest the refund reference number, such as the ARN. The guest’s bank can use it to trace the credit. Stripe notes the ARN can take up to 7 business days to arrive.

Watch for failed refunds. A closed account or a card problem can cause one. What if a guest disputes while a refund is still pending? Stripe may fail the refund so the guest is not paid twice. In that case, accept or fight the dispute. Do not refund again.

Did you send the money back another way? Name that channel clearly. Then check how the dispute can use that proof. Do not assume an off-platform payment updates the original case. Keep the recipient and transaction link, but leave out personal data the case does not need.

Deposits taken through an OTA or a virtual card can involve two separate events: a supplier credit and a guest refund. Sending money back to a platform does not prove when the guest got credit. Use the OTA responsibility guide to map both sides.

Build a Deposit-Specific Response Packet

Lead with the original deposit payment and the real complaint. Add the booking confirmation, the terms shown, a timeline, messages and any completed refunds. Tie each exhibit to the booking and the capture ID.

• Cancellation claim: show who canceled and when.
• Date-change claim: keep the first offer and the guest’s reply to the change.
• Missing-refund claim: show the actual refund status and its reference.

A room photo or a full folio cannot replace those records.

Keep bad news in the file. If a refund was promised but never started, fix that first. If the property could not supply the room, do not frame it as a guest who chose not to travel. Accurate facts beat a forceful but weak rebuttal.

Keep Deposits, No-Shows and Damage Debits Separate

A kept deposit may follow a canceled booking, but it is still an earlier capture. A no-show payment may be a later charge under the booking terms. A damage debit covers a different event and may have its own processing rules.

Use the hotel no-show article when the case is about arrival and a no-show charge. Use the damage and incidental article when a later debit covers the room’s condition or an extra item.

One booking may have all three types. If so, keep each payment on its own row, and note which one the case names. An internal balance can combine them for daily work. But the reply still needs the original transaction’s identity.

Reconcile the Deposit After the Case Closes

Match the case decision to the actual settlement movements. Record deposits, refunds, dispute debits, reinstatements and fees separately. A zero booking balance does not always mean every payment and case is settled.

Chargeflow’s reconciliation guide explains the matching process. For hotel deposits, add one step. Link each money event back to the booking. Never count an uncollected future balance as disputed captured money.

Review repeat refund gaps and cancellation handoffs. Track how often an approved refund has no payment reference. Track how long it waits and which team owns it. These checks help even before a chargeback arrives.

Automate With a Reservation-Level Source Map

Map where each record lives: booking terms, cancellation event, deposit capture and refund status. Confirm that payment and booking IDs can be joined. Make sure the team can pull the original terms after a rate or policy changes.

Chargeflow Automation can help merchants gather evidence and build dispute responses through supported workflows. Bring an anonymized deposit ledger and your processor route to the review. Then the setup can be checked against the records your cases need.

Related Travel Evidence and Automation Guides

• Hotel Chargeback Automation: Connect PMS, Folio and Payment Evidence
• Best Travel Chargeback Management Software: A Buyer’s Guide
• Vacation Rental Chargebacks: Direct Bookings, Property Access and Condition Evidence

Source review: October 20, 2026. Worksheets are original editorial frameworks. All worked case IDs, amounts and timelines are hypothetical. No actual customer outcome or recovery forecast is implied. Check the current case, provider and rules before you submit.