Amex C18 Chargeback: No-Show or Cancelled Reservation

Preserve the reservation as it was booked

Save booking confirmation, date/time, party/service/room details, deposit or guarantee terms, cancellation cutoff, no-show charge, and the version of the terms shown to the customer. If acceptance was recorded, keep the timestamp or booking-system event.

Do not rely on a current booking page if policies change seasonally or by product. The purchase-time terms are the relevant starting point.

Search every cancellation channel

Check booking portal, email, text, phone log, support ticket, property or venue system, and third-party booking channel where applicable. Record whether a cancellation request exists, when it arrived, and what response the customer received.

A no-show case can become a cancellation case if the merchant overlooked a timely request. Investigate before drafting.

Prove the merchant held or provided the reserved capacity

Use reservation status, room/appointment inventory, event check-in, service schedule, or other retained record to show the reserved slot and whether the customer appeared. For prepaid services, separate the value delivered from any no-show fee.

Avoid claiming financial loss beyond what the merchant records can show. The dispute packet needs the transaction terms and event, not a theoretical damage calculation.

Document waivers, rebooking, and exceptions

If staff waived the fee, moved the reservation, issued a voucher, or promised a refund, preserve that decision. A transaction-specific exception can override the merchant's normal policy for the case at hand.

If the customer accepted rebooking instead of refund, show the new reservation and whether it was used or later canceled. Keep the original and replacement reservation linked but distinct.

Reconcile the amount charged

Show deposit, final charge, no-show/cancellation fee, taxes or other components, then any credit. The disputed amount should map to the fee or reservation value the merchant says was owed.

If only part of the reservation was chargeable, do not defend the entire booking amount. Use an amount table.

Create a reservation-event exhibit

A concise exhibit can show booking, terms accepted, cancellation cutoff, customer contact, scheduled time, no-show/cancellation status, charge, and refund/waiver. Attach the source records in the same order.

This format is easier to review than screenshots from separate booking and payment systems with no chronology.

Use C18 to improve booking controls

Trend disputes by booking channel, cancellation channel, policy visibility, staff overrides, and confirmation messaging. Many no-show disputes are preventable when cutoff times and cancellation confirmation are explicit.

Use current American Express merchant rules and the live case for formal response requirements. Internally, make sure policy changes are versioned so future reservations can be reconstructed accurately.

Example: reservation was canceled through a third-party booking channel

A customer cancels through the same third-party platform used to book, but the merchant's direct reservation system does not receive the cancellation. The guest is marked no-show and charged. An Amex C18 audit should search both channels before relying on the internal no-show flag.

If the third party sent a cancellation confirmation, that external record can be decisive. Integrate booking-channel updates or create a reconciliation queue so reservation state does not drift between systems.

Separate reservation creation, cancellation, and actual no-show

For C18, preserve booking time, service date, disclosed cancellation/no-show terms, reminders, cancellation requests across supported channels, check-in or attendance records, and the charged fee. A reservation existing in the system is not by itself proof that the customer failed to cancel correctly.

If the business changed the appointment, venue, or service availability, document that too. A no-show defense should not ignore merchant-side changes that may have affected whether the customer could use the reservation as originally agreed.

Create a reservation event ledger that can distinguish cancellation from a true no-show

C18 requires a complete reservation record: booking date, reservation date/time, location or service, price and cancellation terms, customer confirmation, and any deposit or guarantee. Then search every cancellation channel. A customer may cancel through a marketplace, travel agent, phone, email, app, or direct site, and one system may not sync to another. The merchant should not call a case a no-show until it has checked the channels it accepts.

Prove that capacity was held or the service was available. For hotels or rentals, preserve reservation and inventory records. For appointments, keep schedule and staff allocation. For events, show ticket or seat allocation and event status. A no-show charge is easier to explain when the merchant can show that the booked resource was reserved and the customer did not use it or cancel under the disclosed terms.

Waivers, rebooking, and exceptions can change the financial story. If staff waived the fee, moved the reservation, issued a voucher, or partially refunded the charge, include that outcome. If the customer canceled late and the policy allowed a fee, show the purchase-time term and exact timing. Do not defend a full charge when the merchant's own support record promised a waiver or reschedule that was not honored.

Use C18 disputes to improve channel synchronization. Track third-party cancellations that fail to reach the property or service system, ambiguous confirmation messages, timezone errors, and staff overrides. A shared event ledger should make reservation, cancellation, attendance, and financial outcome visible in one place. That reduces both invalid no-show fees and weak evidence when a genuine no-show is disputed.

Distinguish venue no-show charges from prepaid nonrefundable reservations

A no-show fee charged after absence and a prepaid reservation retained under disclosed terms can create similar customer complaints but different financial records. Preserve whether the original transaction was a deposit, guarantee, or full prepayment and what amount was later charged or retained. The evidence should not call every retained amount a no-show fee.

This distinction improves both customer messaging and reconciliation. If the business adds a separate fee after absence, show its authorization and basis. If it simply retains a prepaid amount, explain the original purchase terms and any rebooking or refund exception.

Record reservation timezone and locale on third-party channels

Bookings from travel, ticket, or appointment partners can display dates and cutoff times in a different timezone from the merchant's local system. Preserve the timezone embedded in the booking confirmation and the cancellation request. If a customer cancels near the deadline, convert both times to one reference while retaining the customer-facing local time. This avoids false no-show conclusions created by cross-system timestamp conversions rather than actual late cancellation.

Reservation disputes should preserve the time basis used by both merchant and customer. Record the property's or venue's local timezone, the customer's displayed timezone if the platform converted it, scheduled arrival, cancellation cutoff, actual cancellation request time, and any third-party channel timestamp. A request sent at 11:30 p.m. can fall on different calendar dates depending on the system, which makes screenshots without timezone context unreliable. Also document whether the reservation was modified before cancellation and whether a no-show fee or retained deposit followed the current terms. This timing record lets the reviewer see the event sequence without guessing which clock governed the policy and helps prevent support agents from applying a cutoff using their own local time.