Most properties will deal with a chargeback at some point, especially around cancellations, no-shows, or disputes about the stay itself. Being prepared ahead of time can help you respond more confidently and with better supporting evidence. We're using Stripe's documented dispute models to build our information and workflows in our examples because it powers ThinkPayments and is well-documented. However, many of the same evidence principles likely apply to other processors because the final decision is made by the cardholder’s bank under card network rules, not by the processor, gateway, or software platform itself. This guide is meant to help our clients prepare a stronger response, not guarantee a favorable result.
What is a chargeback?
A chargeback occurs when a cardholder asks their bank to reverse a payment rather than resolving the issue directly with the property. According to Stripe’s documented process, the disputed amount and dispute fee are typically debited while the case is under review, and the merchant must respond by the dispute deadline, usually within 7 to 21 days, depending on the card network. If no response is submitted before the deadline, the dispute is automatically lost. In practice, that means the property must be ready to show that the charge was valid and properly disclosed.
Why chargebacks are common in lodging
Lodging businesses are more exposed to chargebacks than many other industries because reservations are often card-not-present transactions, the dollar amounts can be higher, and there is usually a gap between the booking date and the stay itself. Third-party bookings can also add complexity. For boutique hotels, the most common disputes often involve cancellations, no-shows, or guests who later question or do not recognize the charge.
What happens when you get one
When you receive a chargeback, start by identifying the reason for the dispute and build your response around that specific claim. Email the guest to understand why they filed the dispute. You may be able to work with the customer to a point where they withdraw the dispute. When communicating with the client, keep in mind that you have a deadline to complete your response.
Disputes are typically organized into categories such as "fraudulent", "credit not processed", "canceled services", "product not received", and "product unacceptable", and the issuing bank decides the outcome. That means the best response is usually the one that directly addresses the reason code, not just the overall reservation story. For example, a folio or stay record may help in a service-related dispute, but it usually does not prove cardholder authorization in a fraud dispute. Focus your evidence on the actual basis of the claim.
How to prepare your response
Build one clear, reviewer-friendly evidence packet: start with a short summary, present the timeline in order, group evidence by type, keep screenshots readable, and include only material that supports the specific claim. Treat the first submission as your strongest chance. It's likely you cannot edit the response or add files after submission. Mastercard’s current chargeback guide says material that should have been included earlier may not be considered later in the process.
For cancellation, deposit, and no-show disputes, a strong response usually answers four questions:
What did the guest book?
What policy was shown?
How did the guest acknowledge it?
What happened after the booking?
Use policies, communications, reservation details, payment and refund records, and Digital Registration records where available.
Example evidence package
A useful evidence packet could look like this for a direct reservation made online through the online booking engine:
Cover summary
One page that states the dispute reason, booking date, stay date, charge date, cancellation deadline, booking channel (source), and why the charge complied with the property’s disclosed policy. Start with a concise summary, and provide an organized timeline.Reservation record from ThinkReservations
Include a screenshot of the reservation view showing the guest name, confirmation number, room, stay dates, amount, and booking channel. If the dispute is about a cancellation or no-show fee, the channel matters because it helps explain how the policy was disclosed.History tab
Include the history entry showing that the reservation was made online and that the guest agreed to the Terms & Conditions and Cancellation Policy. Plus, later events such as cancellation, card charge, refund if any, and emails sent.Checkout flow evidence
For direct online reservations, include screenshots from the checkout flow showing the policy excerpt, link to the full policy, acknowledgment checkbox, and final Confirm Reservation button.. A separate screenshot should include the pop-up/modal that appears after clicking the link, showing the full policy.Confirmation email
Include the reservation confirmation email that went to the guest, and highlight the cancellation language that should be present. Visa says the confirmation should include reservation details, as well as a clearly stated cancellation policy and procedures.Digital Registration PDF, if used
This can be one of the strongest supporting documents. The document is found under the History tab if available. It includes the reservation summary, itemized charges, policy acknowledgments, signature, IP address, and browser user agent, and page 2 includes the full Terms & Conditions and Cancellation Policy. This can be especially helpful for phone reservations, where a later signed Digital Registration record may strengthen the evidence packet.Payment and refund records
If a refund was issued, include the refund amount, date, and processor record. If no refund was due, make sure the policy and timeline explain why.Additional Supporting Evidence
Depending on the reason for the dispute, consider adding call logs, customer SMS and email communications, notes, SOPs, maintenance logs, and receipts.
SOPs can help demonstrate that you have a documented process staff are trained to follow, such as carefully explaining the cancellation policy for phone reservations and regularly inspecting rooms for issues.
How to reduce disputes before they happen
Prevention is usually less about writing a longer cancellation policy and more about making charges and policies easy for guests to understand, recognize, and verify later. Clear communication, transparent cancellation and refund terms, recognizable charges, and strong recordkeeping can all help reduce avoidable disputes.
Make charges recognizable on the guest’s statement.
Use a billing descriptor that clearly reflects the property name guests will recognize. Confusion over an unfamiliar business name is one reason some guests dispute otherwise valid charges.
Send an email after charging the card.
A confirmation email or receipt sent after a deposit, prepayment, or balance charge can help the guest recognize the transaction later and reduce disputes caused by confusion or forgetfulness.
Reduce manual handoffs where possible.
Keeping reservation, payment, and guest records connected makes it easier to find supporting documentation quickly if a dispute happens.
A few practical habits help:
Use plain language for deposit, cancellation, and no-show rules so guests can understand them easily at the time of booking.
Keep the guest-facing version of the policy consistent across the website, checkout flow, registration, and confirmation email.
Keep a clean record of any cancellation request, refund decision, or guest communication.
When a cancellation is accepted, send written confirmation and keep the refund record. Visa says properly canceled reservations should be followed by a written cancellation or refund confirmation, and, when applicable, a credit transaction receipt. Our default "Reservation Canceled" email template handles this well, but you should review it to ensure any changes still meet those recommendations.
Where available, it also helps to preserve stronger authorization signals such as billing details, email, phone, line items, and communication history.
What about disputes over the quality of service?
These cases can be much harder to challenge because the question is not only whether the guest booked, but whether the stay matched what was promised. Stripe’s evidence guidance for "product unacceptable", "not as described", and "service not received" disputes leans heavily on accurate marketing materials, service logs, support records, and documented resolution attempts. For you, that means objective evidence usually helps more than a broad rebuttal: property descriptions, photos, amenity disclosures, maintenance notes, guest communications, and records of any resolution offered.
When to ask for help
If you are deciding whether to accept or contest a dispute, start with the reason code and the submission deadline. For ThinkPayments clients, disputes are managed within ThinkReservations using the embedded dispute workflow. Because payment activity is tied to the reservation and guest record, it can be easier to locate the original transaction and gather supporting documentation in one place. Focus first on gathering your evidence and submitting the strongest possible response before the deadline.
If you need help finding reservation details or supporting records inside ThinkReservations, our Support team may be able to help you locate items such as the reservation record, History tab, emails, or Digital Registration records. However, ThinkReservations cannot help evaluate the dispute, create your evidence packet, determine dispute outcomes, or override the cardholder bank’s decision. Because the issuing bank makes the final decision, every dispute should be evaluated individually.
However, ThinkReservations cannot help evaluate the dispute, create your evidence packet, determine dispute outcomes, or override the cardholder bank's decision.
Additional Notes and Tips
Treat your first evidence packet as your best and most complete response. Prepare it as though you may not have the opportunity to add more information later. Stripe says merchants cannot edit a response after submission, and if you miss the deadline, the dispute is automatically lost.
If the reservation came through an OTA, contact the OTA to see whether they can provide supporting reservation documents or policy records to add to your evidence packet. Depending on the booking source, the OTA may be able to provide reservation details, cancellation terms, guest communications, or other records that strengthen your evidence packet.
Do not issue a refund after a formal dispute has already been filed just to try to resolve it. In many cases, the dispute process will continue anyway, which can create unnecessary extra work and may complicate reconciliation. Review the dispute reason and your processor workflow before taking any action. Stripe notes that chargebacks formally reverse the payment through the issuer-led process. See here for more on this: Update a Reservation After a Chargeback
Be cautious with cancellation and no-show fees, especially when card-brand rules may apply. Visa’s guaranteed reservation guidance says cardholders must generally be allowed to cancel without penalty within at least 24 hours of booking, and Visa’s and Mastercard’s lodging guidance describe one-night no-show limits in their guaranteed reservation programs. At the same time, these rules can vary by region, country, card program, and acquirer requirements, and network standards can change over time. If you are unsure, confirm with your payment processor or payments team before relying on a policy position in a dispute.
Use every signed or acknowledged guest record you have. A guest’s reply to an email that includes your cancellation policy may help show that the guest received the information.
The Digital Registration PDF can also be especially helpful because it shows the guest’s policy acknowledgments, signature, IP address, and browser data, along with the full terms and cancellation policy they agreed to on page 2.If a guest says they do not recognize the charge, check how your business name appears on their statement.
A valid charge may still be disputed if the billing descriptor is unfamiliar or does not clearly match the property name the guest remembers.
Important Disclaimers:
This article is for general information only and is not legal advice.
The final decision on disputes is made by the cardholder’s bank under the card network rules, not ThinkReservations, ThinkPayments, the payment processor, or the payment gateway.