You held the date. You turned down two other inquiries for that Saturday, told your assistant to keep the morning clear, maybe already ordered materials. Then, eleven days out, the email arrives: "We've decided to go in another direction." You point to the line you both signed — the deposit is nonrefundable — and the client seems to accept it. Three weeks later, Stripe notifies you of a dispute. The client didn't argue with your contract. They went around it, to someone who has never read it: their bank.

"Nonrefundable" is a claim, not a setting

Here is the uncomfortable mechanics of it. There is no such thing as nonrefundable money inside the card networks. "Nonrefundable" is not a property you attach to a charge the way you attach a billing descriptor; it is a claim you make about an agreement — and when a cardholder disputes the deposit, you are the one who has to prove that claim.

Deposit disputes usually arrive under a cancellation reason code — Visa's 13.7, "Cancelled Merchandise/Services," or its Mastercard equivalent. Under those codes, the bank is not asking whether your policy exists. Almost every merchant has a policy. The bank is asking whether the cardholder knew about it and agreed to it before they paid.

That distinction decides these disputes, because the network rules put the burden squarely on you: a cancellation or no-refund policy only binds the cardholder if it was properly disclosed at the time of the transaction. Buried on page four of a contract they signed after the charge went through? Weak. Sitting on your website's FAQ page? Weaker. Printed on the receipt? Nearly worthless — disclosure after payment is not disclosure at all.

Most merchants who lose deposit disputes don't lose because their policy was unreasonable. They lose because they can't prove the customer ever saw it.

Why deposits get disputed more readily than finished work

It's worth understanding why a customer who wouldn't dream of disputing your finished work will dispute a deposit without blinking. The mechanism is what behavioral economist Richard Thaler called mental accounting: people don't evaluate money in the abstract, they file each transaction into a mental ledger of what went out and what came in.

A deposit on a cancelled service lands in the worst possible cell of that ledger: money out, nothing in. From where you sit, the deposit bought something concrete — exclusive claim on a date, your refusal of other work, hours of preparation. But opportunity cost is invisible to the buyer. They never see the inquiries you declined or the Saturday you can no longer sell. To them, they paid and received nothing they can point to, and a payment with no perceived value in return doesn't feel like a policy being enforced. It feels unfair — and people are remarkably willing to reclassify an unfair-feeling charge as an illegitimate one. That's how honest customers talk themselves into disputes: not "I'm going to steal this back," but "they shouldn't get to keep money for doing nothing."

Loss aversion finishes the job. The cancellation itself is already a loss — the event is off, the plans collapsed — and the deposit is the one piece of that loss that looks recoverable. The dispute button is one form away.

You can't remove that psychology. But you can write your deposit terms so they answer it, which turns out to be exactly what wins the dispute too.

What the reviewer actually checks

When a deposit dispute lands in front of a bank analyst, the review comes down to three questions, in order:

Was there a cancellation policy? Easy — you attach it.

Was it disclosed before payment, somewhere the cardholder couldn't reasonably miss? This is where most merchants collapse. The evidence that works is a screenshot of your actual checkout or booking page showing the policy adjacent to the payment action — near the pay button, not behind a link. If you invoice, it's the policy text inside the invoice the customer paid, above the payment link.

Did the cardholder affirmatively accept it? A required checkbox with a logged timestamp that precedes the charge. A signature on a contract dated before payment. A confirmation email restating the terms that the customer replied to. Any written moment where the customer acknowledges the deposit terms in their own words is gold.

Then add the layer most merchants never think to include: evidence of what the deposit bought. If holding the date cost you something, show it — the calendar entry created the day they booked, the inquiry you declined for that slot, the consultation you already delivered, the mockups or planning documents you produced. This does two things. It converts "merchant keeping money on principle" into "merchant already performed part of the service," and under a cancellation reason code, partial performance materially changes what the analyst is looking at.

The strongest deposit evidence is written before anyone cancels

There's a quiet upgrade available in how you word the policy itself. Most deposit language is written as a prohibition: deposits are nonrefundable. Rewrite it as a purchase: this deposit reserves your date exclusively — once it's paid, we decline all other bookings for that day, which is why it can't be returned if you cancel.

Same policy, different frame — and it works on both audiences that matter. The customer's mental ledger now has something in the "received" column: exclusivity, which they demonstrably got. And the bank analyst reads an exchange of value rather than a forfeiture clause. You are no longer arguing that you deserve to keep their money; you're documenting that you delivered what the money was for.

The last piece is the cancellation moment itself. When a client cancels, respond in writing the same day — acknowledge the cancellation, restate the deposit terms you both agreed to, and note what the deposit covered. Never handle it only by phone. If a dispute comes later, that email is the difference between "the merchant claims there was a policy" and "the cardholder was reminded of the policy and did not object."

Your next moves

  • Move your cancellation policy onto the payment page itself, in plain sight of the pay button, with a required checkbox: "I understand the $X deposit reserves my date and is not returned if I cancel." Take a dated screenshot of that page today and store it where you can find it.
  • Rewrite the policy sentence to state what the deposit buys — exclusive hold on a date, work that begins immediately — not just what it forbids.
  • Send a booking confirmation email that restates the deposit terms in plain language, and keep the thread. If the client replies at all, better still.
  • Start a "date held" log. Every time you decline or redirect work because a slot is reserved, keep the evidence — the inquiry email, a two-line note with the date. That is your opportunity-cost proof, and it cannot be reconstructed later.
  • When a cancellation comes in, reply in writing the same day, restating the agreed terms and what the deposit covered. Calm, factual, no lecture — you're writing for a future reader at a bank.

When they dispute it anyway

Even with every piece in place, some deposits will be disputed — the psychology above practically guarantees it — and when one is, Stripe gives you a window that can be as short as seven days to assemble the checkout screenshot, the signed terms, the confirmation thread, and the cancellation email into a response a bank analyst will credit. That's exactly the moment Argeback was built for: it ingests the dispute, drafts an evidence-backed response around the records you kept, and files it before the deadline — from your phone, in the middle of the workweek the dispute interrupted. If you take deposits for a living, see how it works at argeback.lumenlabs.works.