It usually arrives as an email from your payment processor, weeks after the stay. A guest — sometimes one you remember, sometimes a name you have to look up — has told their bank that a charge from your park wasn't valid. The bank has already pulled the money back out of your account, added a dispute fee on top, and given you a deadline to prove the charge was legitimate.
That's a chargeback. If you take cards — and nearly every park does now — you'll eventually get one. They're rare at most small parks, a handful a season at most, but each one is annoying out of proportion to its size: money clawed back without warning, a fee stacked on top, and a stack of paperwork due by a date you didn't pick.
The good news is that chargebacks are mostly a records problem, and records are something a small park can get right. Here's how the process actually works, why campground charges get disputed, and what wins.
What a chargeback actually is
A chargeback is not a refund request. A refund is between you and the guest. A chargeback goes around you entirely: the guest calls their card issuer, the issuer provisionally sides with its cardholder — that's how the system is built — and the money comes out of your account while the question is still open.
From there you have a choice. You can accept the dispute and let the money go, or you can submit evidence: the reservation confirmation, the policy the guest agreed to, any correspondence. The issuer reviews it and makes a decision, which typically takes several weeks. There's no phone call, no hearing, no chance to explain in person. The evidence is the whole case.
Two details worth knowing before your first one. First, the dispute fee — around $15 with most processors — usually isn't returned even if you win. Second, the person deciding works for the guest's bank, not a neutral party. You're arguing on someone else's home field. That shapes the whole strategy: the fight is winnable, but the better play is not needing to fight. (For the broader picture of how card money moves and what it costs, see where the money goes in campground payment processing.)
Why campground charges get disputed
Almost every campground chargeback traces back to one of three causes.
- The guest didn't recognize the charge. Your park is "Riverbend Campground" on the sign, but the card statement says "FROG HOLLOW LLC" or the name of a management company. The guest — or their spouse, who didn't make the booking — sees an unfamiliar charge and disputes it in good faith. This is the most common cause and the most preventable one.
- A cancellation disagreement escalated. The guest canceled, believed they were owed a refund, didn't get one (or didn't get it fast enough), and let the bank sort it out. Sometimes your policy genuinely supports the charge; sometimes the policy was never clearly shown, and the bank will notice that.
- A no-show got charged. You held the site, they never came, you charged the card on file per your policy. To the bank this looks like a card-not-present charge for a service the cardholder says they never received — which is exactly what fraud looks like. These are the hardest disputes to win without a clearly documented, clearly disclosed policy.
Actual stolen-card fraud happens too, mostly on phone bookings where a card number is read out and keyed in. But at a small park, the honest-confusion and policy-disagreement disputes outnumber the criminal ones.
Most chargebacks are won or lost before they're filed
Each cause above has a fix, and none of the fixes involve arguing with a bank.
Make the statement descriptor match the sign. Your processor lets you set the text that appears on guests' card statements. Set it to your park's name — the name on the highway sign, not your LLC. This one change prevents the largest single category of disputes.
Put the policy in front of the guest before they pay, and keep proof. A cancellation policy that lives on a laminated sheet at the check-in desk protects you from nothing. A policy shown at checkout, agreed to before payment, and restated in the confirmation email is evidence a bank will actually accept. If yours needs work, start with how to write a cancellation policy guests actually accept — a policy guests understand up front is one they don't dispute later.
Stop taking card numbers over the phone. Every scribbled card number is a card-not-present charge with no cardholder agreement attached — the weakest possible position in a dispute. When guests book and pay themselves online, the transaction carries its own paper trail: who booked, what they agreed to, when they paid. That's what a modern guest booking flow does quietly in the background of every reservation.
Answer refund requests fast. A guest who emails about a refund and hears nothing for a week calls their bank. A $45 refund you disagree with is still cheaper than a $45 chargeback plus a $15 fee plus an hour assembling evidence — and disputes on your account are a mark against you with the processor even when you win.
When to fight and when to let it go
When a dispute does land, decide like a business, not on principle.
Fight when the record is clean: the guest booked online, the policy was displayed and agreed to, the confirmation went out, and the charge followed the policy exactly. Submit the confirmation, the policy as shown at checkout, the timestamps, and any emails. Keep it factual and short.
Let it go when the amount is small and the record is thin — a phone booking with no written agreement, a policy you can't prove the guest ever saw. You'll spend an hour to lose anyway.
Here's the honest trade-off: even a clean case loses sometimes. Banks lean toward their cardholders, and a well-documented no-show charge can still go the guest's way. Good records turn chargebacks from a coin flip into a strong bet — not a sure thing. Budget a little patience for the occasional unfair loss, and don't let one sour you on charging fair policies fairly.
The takeaway
Chargebacks aren't really a payments problem. They're a records problem. A recognizable name on the statement, a policy the guest demonstrably agreed to, and payment taken through a real checkout instead of over the phone will prevent most disputes and win most of the rest.
This is one of the quieter arguments for running reservations through booking software. With Bunkpost, every reservation is charged through your own Stripe account under your park's name, the guest accepts your cancellation and deposit policies at checkout, and the confirmation email restates them — so when a dispute comes, the evidence already exists. Bunkpost is free for the park; the only fee anywhere is a flat $3 the guest pays at booking, shown as its own line before payment. If you'd rather see it than read about it, here's how setup works — most owners are taking bookings the same afternoon.
You can't opt out of chargebacks. You can make them boring. That's the win.