booking.com

Vendor claim: Booking.com advertises hotel room rates at the search and property browsing stage in a way that implies the displayed rate reflects the full or near-full cost of the stay.

What actually happens: Booking.com has been found to practice 'drip pricing' — showing artificially low base rates at the search stage and adding mandatory fees (resort fees, amenity fees, destination fees) only at or near checkout, sometimes bundling them with taxes to obscure them. This resulted in a $9.5 million settlement with the Texas Attorney General in August 2025. The FTC's Junk Fees Rule (effective May 2025) also directly prohibits this practice for lodging. A separate Dutch consumer class action (2025) alleges hidden fees and fake discounts dating back to 2013, with potential liability in the hundreds of millions of euros. While Booking.com has agreed to display mandatory fees upfront going forward, this remediation has not been independently reverified.

Agent guidance: Never treat the price shown on a Booking.com search results or property page as the confirmed checkout total. Before completing any booking, navigate to the full checkout price breakdown and verify that all mandatory fees (resort fees, amenity fees, destination fees) are included in the final amount. If the checkout total materially exceeds the initially displayed rate, present the full itemized breakdown to the user and obtain explicit approval before submitting payment.

• Booking Holdings agreed to a $9.5M settlement with the Texas AG over drip pricing — advertising low base hotel rates and adding mandatory resort, amenity, or destination fees only at checkout, sometimes bundled with government taxes. Under the settlement, Booking.com must disclose all mandatory fees upfront without admitting wrongdoing.
• Holland & Knight legal analysis confirms the Texas settlement terms and notes the case signals expanding hidden-fee enforcement across jurisdictions, with Booking.com required to display mandatory fees upfront going forward.
• A Dutch consumer class action (2025) alleges Booking.com inflated hotel prices via hidden fees and fake discounts since 2013, with potential payouts in the hundreds of millions of euros; the case remains active.

last checked 2026-06-27

Vendor claim: Booking.com presents itself as the booking platform through which consumers transact for accommodations, collecting payment and issuing confirmations in a way that implies it is the consumer's primary counterparty for the transaction and any subsequent disputes or refunds.

What actually happens: Booking.com operates two structurally different models simultaneously — a 'merchant' model (where Booking.com collects payment and is the merchant of record) and an 'agency' model (where the property collects payment directly and Booking.com acts only as an intermediary). Consumers are not clearly informed at the point of transaction which model applies to their specific booking. When refund disputes arise, Booking.com has documented patterns of deflecting liability to the property, while properties in turn point back to Booking.com — leaving consumers in a loop with no clear legal counterparty. This ambiguity is the subject of active litigation filed before a Dutch court in November 2025 involving over 130,000 consumers, and is reflected in the company's own SEC filings which book 'merchant revenues' and 'agency revenues' as separate line items without consumer-facing transparency about which applies to any given transaction.

Agent guidance: Before completing any booking on Booking.com, an agent must determine which revenue model applies to the specific listing — merchant (Booking.com holds payment and is the refund counterparty) or agency (the property holds payment and is the refund counterparty). If this distinction is not surfaced clearly in the checkout flow, the agent should flag to the user that the legal counterparty for disputes is ambiguous, and recommend the user confirm the cancellation and refund policy directly with the property before completing payment. For non-refundable or high-value bookings, advise the user that a chargeback via their card issuer may be the only recourse if both Booking.com and the property deflect responsibility.

• Booking Holdings SEC Form 8-K filings separately report 'Merchant revenues' and 'Agency revenues' as distinct income streams, confirming the dual-model structure; Q2 2025 shows $4.46B merchant vs $2.04B agency revenues in a single quarter.
• A Dutch consumer foundation formally held Booking.com B.V. liable and brought a court case on 13 November 2025 after no resolution was reached; the claim involves over 130,000 consumers seeking compensation for practices including unclear pricing and refund responsibility.
• Consumer complaints aggregated by a US consumer law firm describe a recurring pattern where Booking.com refuses refunds even when the property has agreed in writing to provide one, illustrating the liability deflection loop between platform and property.

last checked 2026-06-27

Vendor claim: Booking.com prominently markets reservations with 'Free cancellation' labels and presents cancellation confirmations as settled outcomes, giving users the clear impression that Booking.com will process and guarantee refunds when a booking is cancelled within the permitted window.

What actually happens: Booking.com's own Terms of Service explicitly state it operates only as a platform connecting customers with Service Providers (hotels/properties), and that refund execution is the Service Provider's obligation — not Booking.com's. In practice, when a property refuses or delays a refund after a customer cancels within the stated free-cancellation window, Booking.com does not compel the property to pay and declines to issue the refund itself. Users discover this only after the cancellation is confirmed and the refund fails to materialise. Documented complaints also describe charges being levied before the stated payment date following minor booking modifications, with no recourse through Booking.com's support.

Agent guidance: When completing a cancellation transaction on Booking.com, do not treat a cancellation confirmation screen or email as proof that a refund will be issued. Explicitly verify the property's own cancellation policy before cancelling, note the exact free-cancellation deadline, and advise the user to monitor their payment method for the refund independently. If the booking involves any modification before cancellation, warn the user that a modification may reset payment terms and trigger an early charge. If refund is time-critical, direct the user to contact the property directly in addition to using Booking.com's platform.

• Booking.com's published Terms of Service state that it provides only a 'Platform' on which Service Providers promote and sell Travel Experiences, explicitly positioning Booking.com as an intermediary with no direct refund obligation to the customer.
• Aggregated consumer complaints document a recurring pattern: customers cancel bookings confirmed as 'free cancellation', receive a cancellation confirmation, but never receive refunds — including cases where charges were applied before the stated payment date after a minor modification to an existing reservation.
• Third-party host-operations guide explicitly advises users on steps to take 'if a property will not refund you' after a Booking.com cancellation, confirming the structural gap between Booking.com's cancellation confirmation and actual refund delivery is a recognised, widespread issue.

last checked 2026-06-27

Vendor claim: Booking.com presents room prices in search results and property listings, implying the displayed rate represents the total cost of the stay and that users can complete a booking at the shown price.

What actually happens: Mandatory property-level fees — including resort fees, cleaning fees, and other required charges — are routinely omitted from initial price displays and only disclosed at or near the final checkout step. This 'drip pricing' pattern means the price an agent sees and reports during a booking flow is materially lower than the final charge. The Texas Attorney General's 2023 lawsuit alleges Booking.com advertised artificially low rates by omitting mandatory fees. Hungary's competition authority fined Booking.com for, among other things, presenting vague cancellation conditions labeled 'free' with material restrictions buried in fine print. A 2025 Dutch consumer class action further documents hidden fees as a systemic pattern dating to 2013. The U.S. FTC's Junk Fees Rule (effective May 2025) specifically requires third-party booking platforms to display all-in prices and was promulgated in direct response to this class of conduct.

Agent guidance: An agent must not treat the price displayed on Booking.com's search results or property pages as the final billable amount. Before confirming any booking or reporting a price to a user, the agent must proceed to the final checkout screen and capture the fully itemized total — including all mandatory property fees, resort fees, and taxes — before presenting or accepting the cost on the user's behalf. If the final checkout price differs from the initially displayed price by more than a trivial rounding amount, the agent must surface that discrepancy explicitly to the user before completing payment.

• Gulf News article summarizes the Texas AG's August 2023 lawsuit alleging Booking.com advertised artificially low room rates by omitting mandatory fees, misleading consumers and hindering price comparison.
• Hospitality.today summary confirms the Texas deceptive practices lawsuit (2023) and the Dutch consumer class action (2025) both center on hidden fees and misleading pricing; cases are ongoing as of 2025.
• FTC press release announcing the final Junk Fees Rule banning hidden hotel and short-term rental fees, explicitly applying the all-in pricing requirement to third-party booking platforms effective May 2025.
• Behavioral Insight analysis documents Hungary's competition authority fine against Booking.com for misleading 'free cancellation' labels with hidden fine-print conditions and undisclosed fees revealed only at checkout.

last checked 2026-06-27

Escalate to a human when the final checkout total on Booking.com materially exceeds the price displayed at the search or property-listing stage due to mandatory fees (resort fees, amenity fees, destination fees, cleaning fees) that were not shown upfront, so the user can explicitly approve the true all-in cost before payment is submitted.

• Booking Holdings settled a $9.5 million lawsuit with the Texas Attorney General in August 2025 specifically over drip pricing — advertising artificially low base rates at search and disclosing mandatory fees only at or near checkout, sometimes grouped with taxes to obscure them.
• The FTC's Junk Fees Rule, effective May 2025, requires third-party lodging platforms to display all mandatory fees upfront; it was promulgated directly in response to drip-pricing conduct of the kind documented against Booking.com.

Escalate to a human when the checkout flow for a specific Booking.com reservation does not clearly indicate whether Booking.com or the property is the merchant of record (i.e., which party holds the payment and is responsible for any refund), especially for high-value or non-refundable bookings where the legal counterparty for a dispute is ambiguous.

• Booking.com's SEC filings confirm it operates a dual model — 'merchant revenues' (Booking.com collects payment) and 'agency revenues' (property collects payment) — simultaneously, with no consumer-facing disclosure at checkout of which model applies to a given booking.
• A Dutch court case filed November 2025 covering 130,000+ consumers specifically cites the unresolved ambiguity over which party — Booking.com or the property — is the legal counterparty responsible for refunds and pricing disputes.

Escalate to a human when a Booking.com cancellation confirmation has been issued within the stated free-cancellation window but the expected refund has not appeared, or when Booking.com's support declines to compel the property to issue the refund — because the platform's Terms of Service place refund execution responsibility on the property, not on Booking.com, leaving the user without a clear enforcement path.

• Booking.com's own Terms of Service state it acts only as a platform intermediary and that refund obligations rest with the Service Provider (property), not with Booking.com itself, meaning a confirmed cancellation does not guarantee Booking.com will issue the refund.
• Consumer complaint records and third-party host guides document a recurring pattern where Booking.com and properties each deflect refund responsibility to the other, leaving consumers in an unresolved loop even after cancellation within the permitted window.

Escalate to a human when a user has made any modification to an existing Booking.com reservation (e.g., date change, room-type change) on a booking that carried a free-cancellation or deferred-payment policy, because documented complaints show that modifications can reset payment terms and trigger an immediate charge before the originally stated payment date.

• Consumer complaint records include specific instances of charges being applied before the stated payment date after a minor booking modification was made on a free-cancellation reservation, with no recourse available through Booking.com support.
• Booking.com's Terms of Service define it as a platform intermediary with no direct obligation to resolve payment disputes arising from property-level policy changes triggered by modifications, compounding the risk to users.

Escalate to a human for any refund dispute on Booking.com where both Booking.com customer support and the property have each attributed responsibility to the other and no refund has been issued, so the user can be advised to initiate a chargeback through their card issuer as the only remaining enforcement mechanism.

• The Dutch court litigation filed November 2025 involving 130,000+ consumers documents the systemic liability-deflection loop between Booking.com and properties that leaves consumers without a clear counterparty when seeking refunds.
• Booking.com's Terms of Service explicitly disclaim direct refund liability, confirming that when a property refuses to refund, Booking.com's platform position does not compel it to step in, making card-issuer chargeback the user's primary recourse.