How to Handle Chargebacks and Payment Disputes at Your Campsite

It usually turns up as a short, slightly alarming email from Stripe or your bank. A guest has disputed a payment. Perhaps it is a deposit for a weekend that never went ahead, perhaps it is a full week's stay the guest now says they never authorised. Whatever the reason, campsite chargebacks are one of the more stressful parts of running a UK site, because the money disappears from your account before you get any real chance to explain your side of the story. The good news is that most chargebacks are avoidable, and the ones that do land can usually be won with a bit of preparation and the right paperwork.

This guide covers what a chargeback actually is, why campsites see more of them during busy months, how to stop most of them happening in the first place, and exactly what to do if one lands in your inbox this summer.

What a Chargeback Actually Is

A refund is something a guest asks you for directly. You agree, you process it, and everyone knows where they stand. A chargeback is different. Instead of contacting you, the guest goes straight to their card issuer and asks them to reverse the payment. Your first sign that anything is wrong is often a notification from your payment processor telling you the funds have already been pulled back, along with a deadline to respond with evidence if you want to dispute it.

Chargebacks exist to protect genuine card fraud victims, and that is a good thing. The problem for small businesses like campsites is that the system is also used, sometimes accidentally and sometimes deliberately, by guests who would get a faster result simply by picking up the phone to you. Either way, once a chargeback is raised, you are working to your processor's rules and timelines rather than your own.

Why Campsites Are Seeing More of Them

A few years ago, most small UK sites took payment in cash or by bank transfer, and chargebacks barely came up. That has changed as more CL and CS owners, and plenty of larger parks, moved to online booking with card payments through systems like Stripe. Card payments are brilliant for cash flow and guest convenience, but they do open the door to disputes in a way that cash never did.

Common triggers include:

• Unrecognised billing descriptors. A guest sees an unfamiliar name on their bank statement and assumes fraud, when it is actually your park's payment under a different trading name
• Family bookings. One family member books and pays, another sees the charge on a shared card and disputes it without realising what it was for
• Genuine confusion over cancellation terms. A guest thinks they cancelled in time for a refund, you disagree, and rather than argue it out with you they go to their bank instead
• Buyer's remorse or a change of plan. Occasionally a guest simply decides not to travel and finds a chargeback quicker than requesting a refund through you
• Actual card fraud. Rare, but it happens, particularly with card-not-present bookings taken over the phone

Notice how few of these are genuine fraud. Most are misunderstandings that a clear process and a recognisable billing name would have prevented.

Fix the Billing Descriptor First

This is the single easiest win available to most site owners, and it is astonishing how often it gets overlooked. Every card payment carries a short billing descriptor, the text that shows up on a guest's bank statement next to the amount. If that text reads something generic or unfamiliar, a guest scanning their statement weeks later may not connect it to their lovely weekend away, and dispute it out of caution rather than malice.

Check what descriptor your payment processor is currently showing and make sure it clearly reflects your site's trading name, not an old business name, a parent company, or a shortened code that means nothing to a guest. If you take payments through CampSuite's payments feature, this is worth confirming as part of your setup, and it is a five minute job that can meaningfully cut down the number of "I don't recognise this charge" disputes you receive.

Preventing Chargebacks Before They Start

Prevention is far less stressful than fighting a dispute after the fact, and most of it comes down to good, boring administration.

• Get guests to actively accept your terms and conditions at the point of booking, not just see a link they might not click
• Send a booking confirmation immediately, showing the dates, the pitch, the total price and what was paid, so there is a paper trail from day one
• Keep your cancellation and refund policy short, clear and easy to find, so guests know what to expect rather than guessing
• Reply quickly to guest queries and complaints. A guest who feels heard rarely escalates to their bank
• Where possible, take card payments in person with chip and PIN or contactless rather than by card-not-present methods, since in-person payments carry far lower dispute risk
• Keep a simple log of guest communication so you are never trying to reconstruct a conversation from memory weeks later

If you handle guest messages and confirmations through automated guest comms, this record keeping largely happens for you, which matters a great deal if a dispute ever does land.

What to Do the Moment a Chargeback Lands

Once you get that notification, the clock is running. Most card networks give you somewhere between seven and twenty one days to respond with evidence, and missing that window usually means an automatic loss, regardless of how strong your case actually was. So the first job is simply to read the notice carefully and note the deadline.

Do not ignore it, and do not assume it will sort itself out. Log into your payment processor's dashboard (Stripe's dispute centre is the most common for CampSuite users) and start pulling together your evidence straight away rather than leaving it until the last few days.

Building Your Evidence Pack

Winning a chargeback dispute comes down to showing the card network that the guest received what they paid for, agreed to the terms, and had every opportunity to raise a problem with you directly first. A strong evidence pack typically includes:

• The original booking confirmation showing dates, pitch, price and the guest's details
• Proof the guest accepted your terms and conditions, such as a ticked checkbox timestamp at the point of booking
• Any email or message correspondence with the guest, particularly anything showing they were aware of your cancellation policy
• Check-in records proving the guest actually arrived and used the pitch, which is often decisive when a dispute claims "services not received"
• Your invoice or receipt showing exactly what was charged and when

This is exactly why keeping good records matters even when nothing has gone wrong. CampSuite's invoicing and check-in tools keep a running paper trail against every booking automatically, so when a dispute notice does arrive you are gathering evidence rather than scrambling to reconstruct it from memory, a spreadsheet and a pile of old emails.

Know When to Fight and When to Let It Go

Chargebacks cost you money whether you win or lose. Most processors charge a dispute fee, often somewhere between ten and twenty five pounds, purely for processing the case, on top of whatever amount was disputed. For a small chargeback on a single night's stay, it is worth weighing up whether an hour of your time gathering evidence is worth more than simply accepting the loss and fixing whatever process gap allowed it to happen.

For larger disputes, particularly a full week's booking or a group pitch, it is almost always worth building the evidence pack properly. Card networks generally favour merchants who respond with clear, organised documentation, so a well-prepared response has a genuinely good chance of success.

What This Means for CL and CS Sites

If you run a CL or CS site, chargebacks are less common simply because you are handling fewer transactions, but they still sting when they happen, and they can feel more personal on a small site where you know most of your guests by name. The same principles apply at any size: a clear billing descriptor, a written cancellation policy, prompt replies to guest queries, and a simple record of who booked what and when.

You do not need expensive software to get this right, but you do need somewhere consistent to keep the paper trail. CampSuite is free for CL and CS sites and keeps your bookings, payments and guest messages in one place, so if a dispute ever does land, the evidence is already sitting there waiting for you rather than scattered across old texts and a notebook.

The Key Takeaway

Chargebacks feel personal because they arrive without warning and take money you have already earned. But most of them come down to fixable causes: an unclear billing name, a guest who was not sure of your policy, or a paper trail that simply was not there when it was needed. Get the billing descriptor right, put your policies in writing, keep records of every booking and conversation, and respond quickly when a dispute does arrive. Do those four things consistently and chargebacks stop being a source of dread and become just another piece of admin you know how to handle.