The Chargeback-Proof Tour Operator Playbook

The email from your payment processor lands on a Tuesday morning. Subject line: "Dispute notification - $380.00." Your stomach does the thing. You know the booking. You remember the guest. You know for a fact they boarded the boat.

But knowing it and proving it are not the same thing. And the bank does not care what you know. It cares what you can document in the next 48 hours.

That is the part nobody tells you upfront. A chargeback is not a refund. A refund is between you and the guest. A chargeback is a punch in the face from the card network - the guest went around you, straight to their bank, and now you are playing defense on someone else's court. The bank's default position is: the guest is right unless the merchant can prove otherwise.

I have a very specific opinion about when chargebacks are won or lost, and it is probably not what you think.

The documentation gets built at booking, not when the dispute lands

By the time that Stripe email arrives, the case is already 90% decided. If you built your proof kit at the moment of booking - timestamps, signed acknowledgements, a confirmation the guest opened - you win. If you did not, you are digging through WhatsApp threads hoping something is useful.

The 48 hours that matter are the 48 hours after the guest books. Not after the dispute. After the booking. That is when you capture the evidence. The dispute just tells you whether you did or you did not.

I know an operator in Simpson Bay who had a guest dispute a $620 catamaran trip three months after the fact. "I never boarded," the guest said. Classic claim. Hard to disprove if you are relying on memory. But this operator had a photo - literally a boarding scan photo, timestamped, with the guest in frame at the gangway. He responded to the dispute in about 20 minutes with the photo, the signed waiver, and the confirmation email showing the guest opened it 36 hours before departure. Dispute reversed. Done.

The bank sided with the operator because the operator had done the work in advance. Not because he was lucky. Because he had a system.

The proof kit - what every booking needs to produce automatically

You should be able to pull the full file for any booking in under 60 seconds. If you cannot, that is the problem to fix first. Here is what the kit looks like:

• Timestamped confirmation email: Date, time, meeting point, what is included - sent the second the booking is made, with a read receipt or open-tracking if your system supports it. "The guest says they did not know the terms" is a hard argument when you can show the email was opened.
• Signed or checked waiver: Policy acceptance at checkout, not buried on a separate page three clicks away. A checkbox with a timestamp is evidence. A PDF link they may or may not have clicked is not.
• Receipt with your actual business name: A lot of chargebacks start as "I do not recognize this charge." Make your statement descriptor match your brand name and your receipt exactly. That alone eliminates a chunk of disputes before they start.
• Boarding documentation: A scan, a photo, a check-in log - anything that shows the guest was present. This is the single best piece of evidence in a "service not rendered" dispute, and most operators do not have it.
• Message history: Any pre-trip communication - weather updates, meeting point reminders, guest questions you answered. Timestamps matter.
• Your cancellation policy as it appeared on the booking date: Screenshot or PDF. Policies change. You want the version the guest agreed to, not the current one.

The no-show policy has to live on the receipt, not just in your head

A guest who no-shows, then disputes the deposit three months later - I have seen this play out badly for operators whose policies were never written down anywhere the bank could see them.

Your no-show policy needs to be in three places: the booking page before the guest pays, the confirmation email, and the receipt. Not your website footer. Not a PDF nobody downloads. The actual receipt the guest keeps.

Same goes for deposit terms. "Non-refundable deposit if cancelled within 48 hours" is a sentence. Put it on the receipt. When the dispute arrives and you paste that receipt into the response form, the case changes.

The day-before reminder matters more than people think. Send it. Meeting point, check-in time, one sentence on what happens if there is weather or a no-show. Another timestamp showing the guest was informed - and it reduces the number of guests who arrive at the wrong dock.

What the bank actually needs to reverse a dispute

Card networks give you a rebuttal window - usually 7 to 20 days. You are submitting evidence, not making a legal argument. Keep it clean and factual.

What moves the needle:

• Proof of service delivery: Boarding photo, scan record, crew check-in log. This wins "service not rendered" claims faster than anything else.
• Proof the guest agreed to your terms: The signed or checked waiver with a timestamp. Not a link to your policy. The acceptance itself.
• Proof the guest was informed: Open receipt showing the confirmation was read. Message thread showing pre-trip contact. The day-before reminder with a delivery timestamp.
• Proof of your identity: Your business name, license number if applicable, and matching statement descriptor. "Unrecognized charge" disputes collapse the moment the merchant is clearly identified.

Do not write an emotional response. I have made this mistake. A calm, documented file with four attachments beats a three-paragraph explanation every time.

Why 80% of disputes go against the operator - and what that stat actually means

Banks side with the guest roughly 80% of the time in travel disputes. That sounds like the system is rigged. I do not think it is rigged. I think 80% of those operators did not have the documentation to win. The operators running on spreadsheets and forwarded emails lose. The operators where every booking automatically produces the proof kit - confirmation, waiver, receipt, record - win.

That is exactly the reason we built Junglebee the way we did. Every booking generates a timestamped confirmation, a receipt, and a guest record that sits there ready to pull. You are not building a chargeback file manually. You are just running bookings, and the documentation builds itself.

If the boarding pass got scanned, you win

That is my one rule for this. If you can show the boarding pass got scanned - or a photo of the guest boarding, a check-in entry, anything that proves presence - you win "service not rendered" disputes. Almost every time.

If you cannot show that, the bank sides with the guest. Not because you are lying. Because you cannot prove the negative. And "I remember they were there" is not evidence.

Build the scan habit. Ten seconds per guest. Do it before the Tuesday morning email arrives. And if you want a booking system where the proof kit builds itself automatically, the pricing is at junglebee.com/pricing.