Book a Demo

Lodging

Hotel Rates, Fees, Deposits, and Refunds Explained

Rate and refund support should separate the displayed total price, optional charges, government charges, deposit, authorization, folio, payment, and refund states.

Marcus BellCustomer Success LeadPublished 5 min read
Rate and refund support should separate the displayed total price, optional charges, government charges, deposit, authorization, folio, payment, and refund states.
Rate and refund support should separate the displayed total price, optional charges, government charges, deposit, authorization, folio, payment, and refund states.

Separate price components clearly

Identify the property, dates, occupancy, room or unit, rate plan, booking channel, currency, displayed total price, mandatory charges, government charges, optional items, deposit, prepayment, card authorization, taxes, and cancellation terms from the approved source. Do not compare unlike offers or reconstruct a total from memory. A nightly rate, average nightly rate, total price, amount due today, estimated taxes, security deposit, incidental hold, folio balance, card charge, and refund are different measures. Support may define approved fields but should not claim the lowest rate or final amount without authority.

Use current total-price rules and terms

The FTC rule on unfair or deceptive fees covers short-term lodging and addresses prominent total-price display and disclosures for excluded charges. Applicability to a particular transaction, seller, advertisement, fee, government charge, or optional service depends on the facts and current law. Support should use the property and channel’s reviewed presentation, preserve what the guest saw, and route suspected discrepancies. Do not decide that a fee is lawful, optional, unavoidable, refundable, a tax, or properly disclosed from a label alone.

Distinguish deposits holds charges and refunds

A deposit may secure a reservation or stay; an authorization may reduce available card credit without being a settled charge; a folio records property transactions; a payment may be pending, settled, reversed, or disputed; and a refund may be approved, initiated, transmitted, posted, rejected, or returned. Explain only the verified state and timestamp. Never ask for full card data or one-time codes in general support, alter a folio, release a hold, execute a refund, or promise bank posting time without the authorized payment owner and system.

Handle disputes without promising outcomes

Capture the disputed item, displayed and charged amounts at the minimum necessary level, currency, date, booking channel, property, folio or payment reference, guest explanation, evidence, policy version, and prior contacts. Route duplicate charges, card-present issues, chargebacks, currency conversion, damaged-room charges, no-show fees, accessibility-related fees, service-animal charges, and suspected fraud to the correct billing, legal, accessibility, or security owner. Tell the guest what is verified, routed, and expected next without admitting liability or promising a refund, reversal, compensation, bank outcome, or legal remedy.

Build the control table

ControlSupport roleAuthorized owner
Guest factsCapture minimum necessary informationValidate identity and reservation
ExplanationUse dated approved sourcesApprove property and policy wording
Consequential actionPreserve request and routeConfirm, waive, refund, disclose, or respond
UncertaintyState limits and escalateInvestigate and respond

Govern sources and accountable handoff

Every answer should point to a dated, owned source. Separate guest statements, reservation records, property inventory, rate terms, folios, payment-processor states, accessibility data, incident reports, property policy, and public guidance. Require qualified review for inventory commitments, rates, mandatory fees, deposits, cancellations, refunds, accessibility, service animals, safety, guest-location disclosure, privacy, payment disputes, fraud, emergencies, identity, accessibility, contracts, and jurisdiction. Log the source version, verification state, property and channel scope, receiving owner, and confirmation.

Protect guest data and service resilience

Collect the minimum information needed in approved channels. Define guest verification, property and role access, retention, redaction, recording, consent, export, deletion, reservation, folio, payment-token, accessibility, location, and vendor controls. Provide accessible interaction, effective communication, error recovery, a human alternative, and reviewed language support. Test outages, duplicate bookings, stale inventory, malicious prompts, suspicious payment requests, credential disclosure, impersonation, accessibility failures, safety reports, and failed handoffs with synthetic data. Record limitations, owners, incident paths, and rollback procedures.

Apply scope and qualified review

This article provides general operational information, not lodging, travel, pricing, contract, accessibility, legal, safety, emergency, payment, privacy, security, identity, or compliance advice. Property, owner, operator, brand, franchise, booking channel, guest, reservation, rate plan, stay, jurisdiction, payment, facts, and current law control. A configured conversational system may assist approved intake and routing, but this article does not claim LumiTalk reads live inventory or reservation data; books, modifies, or cancels stays; quotes or guarantees rates; waives policies; changes folios; takes payment; issues refunds; confirms accessible rooms; makes accommodation or safety decisions; dispatches responders; discloses guest locations; detects fraud; guarantees outcomes or compliance; or provides exact pricing, availability, language, property, or integration coverage.

Primary sources

Use current primary sources as the factual floor, then obtain property, booking-channel, rate-plan, stay, guest, payment, accessibility, safety, contract, and jurisdiction-specific review. FTC Unfair or Deceptive Fees FAQ · FTC Protecting Personal Information · ADA Title III Regulations · ADA Lodging Guide

Continue through the Lodging cluster

Use the hubs and service page for cluster context, then compare adjacent guides before implementing a workflow. Lodging resource hub · Hospitality resource hub · LumiTalk for lodging operations · Lodging Guest Support Operations Guide · Hotel Reservation Changes Guide · Lodging Support Software Checklist

Quick answers

Frequently asked

What must a hotel total price include?

Current FTC rules generally require covered short-term lodging sellers to display unavoidable mandatory charges in the total price, subject to the rule’s definitions and exclusions.

Is a card authorization the same as a charge?

No. Authorization, pending charge, settlement, reversal, and refund are distinct payment states.

Can support promise when a refund will appear?

No. Support should communicate the verified refund state and route bank or processor exceptions without promising posting time.

Are service-animal cleaning fees allowed?

ADA guidance says hotels may not charge routine cleaning fees for service animals, while actual damage may be handled like comparable guest damage.

Hotel Rates, Mandatory Fees, and Refunds Guide

Map one guest journey, its approved source, property boundary, owner, evidence, and accepted handoff before expanding.

Explore LumiTalk for Lodging