Reducing Chargebacks and Payment Disputes for Rental Operators

Reducing Chargebacks and Payment Disputes for Rental Operators

Say the email arrives on a Tuesday in October. A customer is disputing a $340 charge from the middle of August. Your processor has already pulled the money out of your account and added a fee on top, and you have nine days to send evidence.

You go looking. The booking is in the system. The name matches.

But the boards went out on a Saturday, the staff member who ran the counter that day finished up three weeks ago, and nobody photographed anything. You know the customer brought one paddle back cracked, because you remember the conversation.

There is no record of it. You write two paragraphs about the cracked paddle, attach nothing, and lose.

Swap the board for an e-bike, a Jeep or a ropes course session and it plays out the same way. By the time the notice lands, the result rests on what got written down at the counter in August.

Almost none of the chargeback fixes below cost money. The first is a processor setting you can change before lunch.

What a Chargeback Actually Is

A chargeback is not a refund and it is not a complaint. The customer goes to their bank rather than to you. The bank takes the money back out of your account first, tells you afterward, and charges you a fee whether or not you eventually win.

The window is long on their side and short on yours. Card networks typically give cardholders 120 days to open a dispute, and for a booking paid ahead of time the clock usually starts on the rental or lesson date, not the payment date.

So an August rental can still turn up in December. Your reply window is usually 7 to 21 days, set by the card network and passed on by your processor.

A reviewer at the customer's bank decides from the files each side uploads, checked against the dispute's reason code. Nobody phones you or the customer, and how long you've been open doesn't come into it. What you can show with a date on it does.

The fee is charged either way. On Stripe in the US, receiving a dispute costs $15 that you never get back, and countering it costs another $15 that comes back only if you win.

In the US, Square charges no dispute fee, but if you lose, the processing fee on that payment isn't returned; Stripe and Square price by country. Either way, a dispute you win still costs money plus an hour of your time.

Chargeback clock from the rental date to the reviewer decision, with the reply window marked

Where Rental Disputes Actually Come From

A dispute coded as fraud is often a customer who can't place the charge. In rental, tour and lesson businesses the same six causes keep turning up, and each needs a different fix.

The customer does not recognize the charge. Your business trades as Harbor Paddle Co and the line on the statement reads something else entirely, or the charge landed three weeks after the booking because you took the balance later. The cardholder sees an amount they can't place and files it as fraud, honestly believing it is.

Deposit confusion. You told the customer you were taking a $100 deposit on the tandem board, or $500 on the pontoon. They believed nothing would leave their account.

Then the money actually moved, or the hold sat on their card for a week and their balance looked wrong, and they disputed it as unauthorized. The fix is nearly always in the wording.

A damage or cleaning charge with nothing behind it. You charged $150 for a ding in a paddleboard rail, a bent derailleur hanger or a sandy campervan, or you billed the repair on a bent tie rod after a Jeep tour. The customer says it was already like that. Without a dated record from hand-over, the reviewer has two stories and no proof, and that usually goes the cardholder's way.

A fee the customer says they never agreed to. A late-return fee on the 4 p.m. bike when the next customer is waiting, a no-show charge on a lesson, a course a student paid for and then skipped.

Your policy is fair and it's on the website. What matters is whether this customer accepted it at the time, in a way you can produce on demand.

A session or rental you called off. Wind, swell, lightning, a small craft advisory or a group too small to run, and you offered a rebook or a credit. The customer wanted the money back, so they filed it as a service not received. On their side of the form, that's true.

A session the guest didn't finish, or a booking one person paid for. A kid freezes on the first ropes course platform and the family leaves. One parent paid for twelve kids on a birthday booking, and later says they never agreed to the terms their kids signed. The card in the dispute is the payer's, so the record has to show what the payer accepted and who signed for each minor.

Fix One: Make the Charge Recognizable

This is the cheapest fix on the list, and it takes about ten minutes.

The line on a card statement is the statement descriptor, and your processor lets you set it. If it shows a legal entity name, an old trading name or a payment platform's name instead of yours, change it today. The customer needs to read that line five weeks later and think "that's the paddle place" without effort.

Where you set it depends on the processor:

  • Stripe: Settings, then Business details, in the Stripe Dashboard. The full descriptor runs 5 to 22 characters and has to reflect the name you trade under.
  • Square: card charges always start with "SQ *", followed by your location's business name, which you change under the location settings in your Square Dashboard (Square's statement description docs). That name is most of what you control, so make it the one on your sign.
  • Checkfront, Booqable and Rezdy connected to your own Stripe or Square account: the descriptor is set in that Stripe or Square account, as above, not in the booking system.
  • FareHarbor, or any system's built-in payments: the booking system's payment account takes the card, so you may not control the line at all. Ask their support what the statement shows today and whether it can carry your trading name. If it can't, the confirmation email line below does the work.

Use the name on your shop front and your website, not the name on your incorporation papers. If they differ, the descriptor loses and the dispute starts.

Add the town or beach if you have the characters. "HARBORPADDLE MONTEREY" places the charge in a way "HPC LLC" never will.

It matters most for visitors. A guest from Osaka or Melbourne sees the charge converted into yen or Australian dollars, on a statement that may cut your name short, so the name on your sign goes first, in plain English letters. Put the US dollar amount in the confirmation too, so they can match it to a number that looks different.

On Stripe, card charges can also carry a short suffix after a shorter prefix, such as "HARBORPAD* DEPOSIT", so a deposit or damage charge doesn't look like a duplicate of the rental. The suffix is set on each payment by whatever software creates it, so ask your booking system whether it sends one.

Then repeat it where the customer will see it: the descriptor in capitals, the amount and the date, in the confirmation email. It's one line of template copy.

If you take cards through Stripe on EquipDash, payments run on your shop's own connected Stripe account, so the descriptor is the one you set there, and the Booking Confirmation email template under Settings, then Email Templates, is where that line goes.

Statement descriptor before and after: a legal entity name replaced by the trading name and town

Shops that take a deposit online and the balance at the dock get a second version of this problem. Two charges on different days, for different amounts, one from the website through Stripe and one from a Square reader with a different name, look like a double charge to a suspicious customer. The bank letter will call it "duplicate processing" or "paid by other means" (Visa code 12.6).

Either take both through the same processor so the names match, or say in the confirmation that they'll see two lines and what each is for.

Timing matters too. A charge that lands the week of the rental gets recognized. A charge that lands six weeks after someone booked, with no reminder in between, gets disputed.

If you take a deposit at booking and the balance later, send an email before you take the balance, not after. An online booking system sends that reminder on its own; a card machine and a notebook don't. Shops that take full payment at booking skip this one.

If your confirmation is a WhatsApp message or a text, that message is the place for the line. Cash can't be charged back, but a tap on a phone card reader can, so it needs the same records as an online booking. Our guide to taking deposits and partial payments covers how to split the two cleanly.

Customer tapping a card on a counter terminal to pay at a shop

Bookings sold through Viator or GetYourGuide

The guest paid Viator or GetYourGuide, so the OTA is the merchant and the dispute goes to them, not to your processor. Check your supplier agreement for how they pass it on to you. When they ask for your side, send it the same day: the booking reference, the check-in record with the time, the guide's headcount, the signed waiver, every message with the guest and, for a canceled departure, the forecast or warning you called it on.

The records below win those claims too. The descriptor fix doesn't apply, because the charge isn't yours. If your Viator bookings land in your own calendar, as they do through the EquipDash Viator connection, the check-in record sits on the booking like any other.

Fix Two: Get Deposit Language Right

A deposit means three different things in a rental shop, and the word gets used for all three.

An authorization hold puts a temporary block on part of the customer's available credit. No money moves. For an online card payment the hold usually stays valid for about 7 days before it has to be captured or released, and in-person holds can be as short as 2 days depending on the card.

Even after you release it, the customer's bank can take a few more days to show the balance back. Nothing was charged, but their balance looked lower for a week, and that is what they'll remember.

A captured charge actually takes the money, with a refund later if the gear comes back fine. Money left their account. Calling it a hold when you've captured it is the most reliable way there is to generate a dispute.

A non-refundable booking deposit is part of the price, taken up front to secure the date. It is neither of the above and should never share a word with them.

Plenty of paddle shops take no deposit on a single board, and plenty of bike shops hold nothing on a hybrid, just a card or ID at the counter. That works. Then the card on file is what gets argued about, so say in writing what it can be charged for and up to how much: a late return, a lost lock or paddle, damage over a set amount.

Houseboats, jet skis, e-bikes and off-road rigs are different. The deposit there is the real exposure, and a damage claim can run past the rental price, so the wording and the pickup record matter most on exactly these.

For gear that does get a deposit, pick hold or charge, then put the same sentence on the booking page, in the terms, in the confirmation email and in what your counter staff say out loud. Wording that holds up looks like this.

"We place a $100 hold on your card at pickup. This is not a charge, and the $100 is released when the board comes back as it went out. Your bank may take three to five business days to show the released amount."

Or, if you are actually capturing it:

"We charge a $500 refundable security deposit on the pontoon at pickup. This is a real charge and will show on your statement as HARBORPADDLE MONTEREY. It is refunded in full within two business days of return if there is no damage."

Authorization hold, captured charge and booking deposit compared side by side

If you take a hold, release it the day the gear comes back. The customer who still sees $500 blocked on Thursday phones you, and if that call goes badly, they phone the bank next.

And keep deposits on a real payment card, not on a gift card or voucher balance. It's the same rule that applies when you run a gift card program: mixing the two turns a cancellation into an argument about which pot the money came from.

Fix Three: Build the Evidence Trail Before You Need It

If a record takes more than a minute at the counter on a busy Saturday, staff stop doing it by July. These four records take less than that and do the work.

An accepted rental agreement or waiver with a timestamp. Not a policy page on your website. A record that this customer, on this date and time, accepted these terms, including the cancellation policy and the damage and cleaning fees. A digital waiver or agreement signed on the customer's phone before they arrive produces exactly that.

With the rental agreement switched on, EquipDash emails it when the booking is made, it can be signed from that email, the confirmation page or at the counter, and the signed PDF sits on the booking. A guest who never opened the email, or has no signal on the beach, signs at the counter before the gear goes out. If you already use Smartwaiver or another waiver app, that timestamped record counts too; the hard part is matching it to the right booking inside nine days.

For groups and minors, each participant signs their own, and an adult signs for anyone under your age limit. EquipDash waivers can require an authorized adult for participants under an age you set, and record that adult's name, email and relationship to the child. That's your answer to the parent who says "we never signed that."

If you still collect signatures on paper, moving waivers online is the change that does most for your dispute file. Paper waivers still count as evidence. The trouble is finding one August sheet in a binder inside nine days.

A hand-over record that doesn't slow the line. Nobody shoots five angles of every board with a line at the dock on a July Saturday and teenagers working the launch. What works at volume depends on what you rent:

  • Boards and kayaks: one phone photo of the boat or board with its paddle and PFD in the same frame, existing dings on the board tag or a clipboard sheet, and a count of life jackets and dry bags out and back.
  • Bikes: a drive-side photo with the bike's number tag in frame, existing frame scrapes noted, and the battery serial on e-bikes, since "the battery was already dead" is the expensive claim.
  • Boats, jet skis and off-road rigs: a walk-around with the customer (hull and props, or the four corners), engine hours and fuel level on the sheet, both of you sign, and a short phone video of the walk-around.
  • Dive gear: the serial number and last service date of each regulator, BCD and computer on the gear sheet, and tanks checked for current hydro and visual inspection stickers.
  • Guided sessions and courses: the safety briefing sign-off with the guide's initials, and the vehicle or harness number each guest used.

Then have the customer initial the gear sheet. Whatever broke, they will say it was already like that, and a dated pickup record ends the argument.

Kayak renter heading to the water with paddle and life jacket

In EquipDash, each tracked item has its own code, so the bike's number tag or the e-bike's serial can be the unit code. The pickup screen has a condition report for each tracked item, with a rating, a note and up to five photos, stamped with the time and the staff member's name.

A return condition report. Logged when the gear comes back, with the damage noted and photographed and the staff member's name on it. In EquipDash a Damaged rating needs at least one photo, and the report pushes the unit into the workshop so it stops showing as bookable. It also builds the item's maintenance and condition history, so you can show the board had no ding the rental before.

When you add a damage charge to the report, the customer's email carries the pay link and a link to a read-only page with the return photos, times and staff notes. They see the evidence before they think about calling their bank.

Proof the customer was actually there. For rentals: the signed agreement, the check-in time and, if they paid at the counter, the card terminal receipt.

For lessons: the sign-in sheet with the instructor's name.

For tours and ropes courses: the manifest with each guest checked in and the time, the guide's roster or headcount, and the briefing sign-off. On an EquipDash manifest, each participant's check-in is stamped with the time.

For dive courses and charters: the boat manifest with the divemaster's initials, the signed medical questionnaire, a copy of the cert card, the dive log entry, and the pool sign-in sheet for confined-water sessions. For a dispute coded as fraud, proof the cardholder showed up and took part is the strongest thing you can send.

If the booking was made over WhatsApp, export the chat the day a dispute lands. The thread shows what the customer asked for and agreed to.

Try it on a rental from last month. Give the newest person on staff the booking number and see whether they can put the file together in ten minutes.

If they have to ask someone what happened, it depends on memory, and memory doesn't win disputes. Start with pickup photos on your three most expensive items.

Fix Four: Write Policies That Can Be Enforced

In a dispute, the reviewer doesn't ask whether your policy was fair. They ask whether this customer accepted it.

Is it specific? "Cancellations within 48 hours incur a 25% fee" survives review. "Cancellations may incur a fee" does not.

Is it accepted, not just published? The customer has to have ticked, signed or clicked through it, and you have to be able to produce the record. A policy in a footer link is not acceptance.

Is it applied consistently? If you waive the late fee for regulars and charge visitors, the visitor who finds out has a real argument, and the reviewer sees a rule you don't actually apply.

Does it cover the day you cancel? Most policies cover the customer canceling and say nothing about you canceling.

When you cancel for weather

Weather calls need their own lines in the policy, and the trigger depends on where you run: wind and a small craft advisory for a paddle shop, lightning for a ropes course, a tropical storm on a Florida houseboat weekend, a trail closed after rain for a Jeep tour. Outside the US, point to your national service, such as the Bureau of Meteorology warnings in Australia.

Write what happens when you call off a rental, tour or lesson for weather or a short group: rebook, credit or refund, and how soon. If you hold a group for lightning and then cancel, say what they get for the session they started.

Credit-only is the hardest version to defend, because the customer's claim that the service didn't happen is true. If you keep it, it has to be in the terms they accepted at booking, and your rebook offer has to be on record with a date.

A rebook is worth nothing to a visitor who flies out Friday. For them, offer a slot later the same week, and a refund if there isn't one. Our rain and weather policy guide has wording you can adapt.

Lessons, sessions and courses need two more lines. One covers a no-show. The other covers someone who can't finish: a guest who quits partway through a ropes session (partial refund, credit or nothing), or a dive student who answers yes on the diver medical questionnaire and can't get in the water without a physician's sign-off: is the course moved, or refunded less the e-learning or certification fees you've already paid the agency?

Dive travel packages need a line on money you've already paid out. Name the resort or liveaboard deposit, the date it became non-refundable, and what that means for the customer's refund. Without it, "we already paid the resort" reads to a reviewer as your cost to carry.

In EquipDash, when you confirm a weather closure, every affected customer can get an email and a text with a reschedule link and no change fee, so the record shows you offered a new date the day you called it.

The mechanical part is worth automating. Set the refund windows, cancellation percentages and partial refund rules once, and the amount comes out the same for every booking, whoever is on the counter.

Refund and cancellation rules in EquipDash work this way, and the refund record names the policy and tier that set the amount. Taking these off the whiteboard and into rules means the new hire charges the same fee you would.

The Dispute Response Playbook

When one arrives, work it in this order.

Step one: read the reason code, not the customer's story. The code tells you what the reviewer will check. Stripe groups the network codes into categories with the evidence each one needs. For a rental shop, four come up most:

  • Product not received (Visa 13.1): proof the rental or session happened, such as the check-in time, sign-in sheet or manifest.
  • Product unacceptable (Visa 13.3): the pickup and return condition records.
  • Credit not processed (Visa 13.6, and 13.7 for canceled services): the cancellation policy they accepted, plus your rebook or credit offer. A weather-canceled session can land here or under not received.
  • Fraudulent (Visa 10.4 for online sales): proof the cardholder booked, signed and showed up.

Send what the code asks for. Damage photos don't answer a "not received" claim; a check-in time does.

Step two: pull the file in one pass. The booking record, the signed agreement or waiver with its timestamp, the pickup and return records, the payment record with the descriptor, and any messages with the customer. All of it, from the booking, without hunting through folders.

Step three: write a short cover summary. Dates, amounts, what was booked, what was delivered, which policy applied and when the customer accepted it.

Write it the way you'd explain it to a new hire, and leave out how long you've been in business. In the Stripe Dashboard you respond by dispute type and upload files. On Square in the US it's Orders & payments, then Disputes, and you have seven days from the first email to send your side.

If the form gives you a text box, the summary goes there; if it only takes files, make the summary the first one. Put the dates at the top. The reviewer won't read page two.

Step four: attach the documents in the order the summary references them. Label each file for what it proves: "signed rental agreement, accepted Aug 14, 9:12 a.m.", "SUP board at hand-over, Aug 16, 8:41 a.m." A reviewer shouldn't have to work out why a photo is there.

Step five: submit inside the window and record the outcome. Log the reason code, what you sent and whether you won. After a dozen disputes that log shows where your process leaks, which is worth more than any single case.

When to Fight and When to Refund

Under about $100 with thin evidence, refund it, note why, and move on. On Stripe a fight costs the $15 you've already lost, another $15 to counter (back if you win), and an hour or two of your time, so a $60 dispute with no pickup photo isn't worth it.

With the pickup photo and the signed agreement, a $600 damage charge is worth the hour. Without them, refund it and fix the counter step that skipped the photo.

Multi-day rentals, packages and weekend houseboat bookings usually run to several hundred dollars or more, so with the file in place they are nearly always worth fighting. A damage claim on an engine, a hull or a jet ski is where the walk-around sheet you both signed earns its keep.

Courses are worth it for another reason. By the time a student disputes a dive course, you have often paid the agency for their e-learning or certification and paid an instructor for the pool sessions, so the chargeback costs you more than the card total. Fight it with the signed medical questionnaire and the dive log.

Small ones can be worth fighting too. If you see repeat disputes from the same names, or the same pattern across different customers, conceding teaches them that a chargeback works. That's the case for contesting a $90 dispute you'd otherwise write off.

The cheaper move is a phone call before anyone files. When a customer emails angry, often still in town or on the flight home, whoever handled the booking calls them that day. Often the money isn't what upset them, and a five-minute call ends it.

If the complaint is about conditions and they're still in town, offer a slot later that week. If they've flown home, a rebook is useless to them, so offer a partial refund fast. If it's a damage charge and there's any doubt, send the photo and offer a partial refund.

A $40 partial refund still beats losing a chargeback, which takes the whole charge, adds the fee and counts toward your dispute rate.

Stripe users get one more early signal. Card issuers send early fraud warnings on some payments, and Stripe's own analysis is that refunding a flagged payment makes sense when it's about the size of the dispute fee or smaller.

Keeping Your Dispute Rate Down

Processors and card networks track disputes as a share of your transactions, month by month, and won and lost disputes both count. Stripe says the industry treats dispute activity above 0.75% as excessive, and a sudden spike can draw attention sooner.

The networks' own programs sit higher. Visa's Acquirer Monitoring Program counts fraud reports plus disputes against settled card-not-present sales, which means your online bookings. Its "excessive merchant" line in the US dropped to 1.5% on April 1, 2026, with a floor of 1,500 cases a month.

Mastercard's Excessive Chargeback Merchant level starts at 1.5% and 100 chargebacks a month. A small shop won't reach those counts, but your processor is held to Visa's portfolio limits of 0.5% and 0.7%, so it will act on your rate well before the networks would.

For a shop taking 400 card payments a month, 0.75% is three disputes. At 2,000 card payments a month in season, it's 15.

One bad month with a confusing new deposit process can get you there. Cross the processor's line and it can hold back part of your payouts as a reserve, add fees and, at worst, stop you taking cards.

Once a month, count your disputes against your card payments, because that ratio is what the processor sees. If your processor ever calls about a spike, that count is the first thing to have ready.

When the number jumps, check what changed in the shop before blaming customers: a new descriptor, a new hire skipping pickup photos, a policy change that went out without an acceptance step. More on preventing disputes is in Stripe's own checklist.

Change the descriptor first. It takes ten minutes and stops the disputes that start with "I don't know this charge."

If your records live in a mix of paper, a shared drive and one person's memory, that's the gap a dispute finds. In EquipDash the payment, the signed agreement, the condition reports and the refund rule sit on the same booking. See pricing for what each plan includes.

FAQ

What is a chargeback and how is it different from a refund?

A refund is you returning money to a customer. A chargeback is the customer going to their bank instead, and the bank reversing the payment out of your account. You find out after the money has gone, you pay a dispute fee whether you win or lose, and a reviewer at the customer's bank decides based on the documents each side submits.

How long does a customer have to dispute a rental charge?

Longer than most operators expect. Card networks typically allow 120 days, and for a booking paid in advance the clock usually starts on the rental or lesson date rather than the payment date.

That's why an August rental can produce a dispute notice in December. Your window to respond is far shorter, usually 7 to 21 days depending on the card network, so the evidence has to exist before the notice arrives.

Why do customers dispute charges they recognize as legitimate?

Usually they don't recognize them. A common cause of a rental chargeback is a statement descriptor that doesn't match the name on your shop front, or a balance charge that lands weeks after the booking with no warning.

The customer sees an amount they can't place and reports it as fraud in good faith. Setting the descriptor to your trading name, adding your town if there's room, and putting the exact line in the confirmation email takes about ten minutes and heads off the most avoidable kind of dispute.

Should I take a security deposit as a hold or a charge?

Either works as long as you describe accurately what you are doing. An authorization hold blocks part of the customer's available credit without moving money and usually stays valid for about 7 days on an online card payment, less for some in-person payments. A captured charge actually takes the money and is refunded on return.

The disputes come from calling a charge a hold, or from a hold that sits on the card days after the gear came back. Pick one for each kind of rental, use the same wording on the booking page, the terms, the confirmation email and at the counter, and release holds the day the item is returned.

What evidence wins a damage chargeback?

A dated record of the item at pickup, a signed rental agreement showing the customer accepted the damage and cleaning fees, and a return condition report naming the staff member who logged the damage. The pickup record doesn't need five photos: one photo of the item with its accessories, or existing dings noted on a gear sheet the customer initials, does the job.

Photos taken only on return prove damage exists but not when it happened, which is usually not enough. Written explanations without documents almost never win.

Is it worth contesting a small chargeback?

Compare the disputed amount against the dispute fees (on Stripe in the US, $15 to receive and another $15 to counter, the second refunded if you win) plus an hour or two of your time. Under about $100 with thin evidence, conceding is usually cheaper. Two things override that math: strong evidence makes a case quick to win at almost any amount, and a repeat pattern from the same customer or scenario is worth contesting regardless of size, because conceding teaches the behavior.

Course and package payments are usually big enough to fight. Also watch the count, not just the cost, since disputes are measured as a share of transactions.

What dispute rate do card networks consider too high?

Stripe calls dispute activity above 0.75% of transactions excessive, and processors often step in before that. Visa's Acquirer Monitoring Program flags merchants in the US at 1.5% of card-not-present sales from April 2026, with a floor of 1,500 fraud and dispute cases a month, and Mastercard's excessive chargeback level starts at 1.5% and 100 chargebacks.

For a shop taking 400 card payments a month, 0.75% is three disputes. Track the rate monthly, and when it moves, look for a process change first: a new descriptor, a staff member skipping pickup photos, or a policy that went out without an acceptance step.

Can software actually reduce chargebacks?

Yes, mostly by keeping the evidence in one place. One system holding the booking, the signed agreement with its timestamp, the pickup and return condition records and the payment means the evidence for any rental in the last few months comes together in minutes, not from memory.

It also applies the same refund, cancellation and weather rules to every booking, so the policy you point to in a dispute was applied the same way each time. In EquipDash, a damage charge email also links the customer to the return photos, so they see the evidence before they call their bank.

Does ChatGPT send customers to you?
See who AI recommends when people in your town ask. Free, in about a minute.
Manage your business
in one place
Start your free 21-day trial and see how EquipDash's AI-native platform (with Dash AI and Dash Bots) simplifies your operations.
EquipDash Dashboard