Filing is not winning
Opening a dispute takes a client one phone call. Deciding it is the card issuer's job, and the issuer decides on evidence, not on who complained first. That is why sellers with good records win disputes that sellers without them lose. The contract cannot stop the call, because the bank is not a party to it, but it is what the bank reads when it decides. Two sets of rules apply:
- The law. In the US, Regulation Z treats a charge for services "not delivered to the consumer [...] as agreed" as a billing error the cardholder can raise within 60 days of the statement (12 CFR 1026.13). A separate rule lets a credit cardholder assert against the issuer the same claims and defences they have against you, after a good-faith attempt to settle with you (12 CFR 1026.12(c)).
- The card network. Visa and Mastercard run their own dispute systems on top of the law. Under Visa's rules, most service disputes can be raised up to 120 days after the service was, or should have been, delivered.
The network rules also close the obvious loophole. Most coaches and consultants take cards through Stripe, Square or PayPal, which generally act as payment facilitators. Visa's rules require every payment facilitator to agree that it will not let its sellers shift their liability "by asking or requiring Cardholders to waive their dispute rights" (Visa Core Rules, section 5.3.1.1, April 2026). A clause in which the client promises never to dispute is exactly that kind of request. So the way to protect yourself is not to forbid the dispute. It is to make sure that when one arrives, your file wins it.
What the bank checks your contract for
Once a dispute is open, the issuer's analyst compares the client's claim with your evidence. For services, the contract is the yardstick for almost every claim the client can make:
- "It was not what I was promised" (Visa 13.3, not as described). Visa defines the claim as services that did not match the description presented at the time of purchase. Your scope of work is that description. A vague scope ("business coaching") leaves the analyst to take the client's word for what was promised; a specific one ("six 60-minute calls and a written 90-day plan") lets you show each item was delivered.
- "I cancelled and was not refunded" (Visa 13.7). Here the question is whether your cancellation terms were properly disclosed and accepted when the client paid. If they were, the analyst applies them.
- "I never received it" (Visa 13.1). The contract sets what "delivered" means and when. Without delivery dates in writing, you cannot show that nothing was late.
Visa's rules add two limits that work in your favour. For a not-as-described dispute about a service, the client must first try to resolve it with you and, if the service was already rendered, ask you for a credit. And the disputed amount is capped at the unused portion of a cancelled service, not the whole fee. A contract that splits the work into dated stages makes "the unused portion" easy to calculate.
One limit works against you. Visa's own merchant guide says a merchant's return policy "has no bearing" on a not-as-described dispute (Dispute Management Guidelines for Visa Merchants, June 2024). A "no refunds" line does not defend you against a client who says the work was not what you sold. Only proof of delivery against a clear scope does.
Contract clauses ranked by what they do in a dispute
The table is our reading of the Visa rules and Regulation Z, applied to service work. It is not legal advice, and the issuer decides each case.
| Clause | Where it counts | What makes it work |
|---|---|---|
| Scope of work with named deliverables | Not as described (13.3), not received (13.1) | Countable items, formats and dates the client can tick off |
| Delivery and acceptance terms | Not received (13.1), not as described (13.3) | A stated delivery channel (for example the client's own email) and a sign-off step per stage |
| Cancellation and refund terms | Cancelled services (13.7), cancelled recurring (13.2) | Shown and accepted at checkout, before payment, in the way Visa requires (see below) |
| Staged fees or milestones | Any service dispute | Limits a dispute to the unrendered stage instead of the whole fee |
| "Contact us first" clause | Every service dispute | A named channel and a response time; a silent client then has to explain why they skipped it |
| Identity of the signer | Fraud (10.4) | Name, email and ID matched to the card that pays |
| "No chargebacks" clause | None | Unenforceable against the bank; on Visa it conflicts with the waiver rule above |
| Chargeback penalty fee | None in the dispute itself | Charging it to the same card invites a second dispute; if you keep it, bill it by invoice |
The pattern is simple. Clauses that describe the work help you. Clauses that try to forbid the dispute do nothing, and can make the analyst read your file as the work of a seller with something to hide.
How the contract must be signed to count
A strong contract signed the wrong way is weak evidence. Three things decide whether it carries weight.
- Before payment. Terms accepted after the card was charged were not "presented at the time of purchase". Send the agreement first and take payment only once it is signed.
- In the place Visa expects. For online sales, Visa's merchant guide says the refund or cancellation policy must appear either in the pages before final checkout with a "click to accept" button, checkbox or signature space, or on the checkout screen near the submit button. A link is fine if it is part of the click-to-accept wording. A policy in your website footer is not disclosure.
- With a record you can produce. Keep the exact version the client saw, the time, the email address and the IP address of the acceptance. In the US, an electronic signature has the same legal effect as ink (15 U.S.C. 7001), but the analyst can only weigh what you can show.
Our before-the-chargeback page sets out the full order of records, from agreement to completion.
Worked example: the same dispute, two contracts
Illustrative example. The coach, clients and figures are invented to show the method. This is not a real case.
A career coach sells a US$2,400 package by card. Two clients pay, take part, then dispute the charge as "not as described" after the fourth of six sessions.
Client A signed a one-page agreement by email after paying. It says "career coaching package, non-refundable, client agrees not to file chargebacks". The coach has the agreement, the invoice and some calendar invites. The analyst sees terms accepted after the charge, no description to test the claim against, and a waiver clause the network does not recognise. The coach has nothing that answers the complaint.
Client B accepted, by click-to-accept before checkout, an agreement listing six 60-minute calls, a written CV review and a 90-day plan, priced as three stages of US$800. Each stage has a sign-off. The coach has sign-offs for stages one and two, call summaries emailed the same day, and no message from the client before the dispute. The response shows stages one and two were delivered and accepted, argues that any refund is limited to the unused third stage, and points out that the client never contacted the coach before going to the bank.
Same coach, same work, same complaint. The difference is entirely in how the agreement was written and when it was signed.
When a dispute arrives: using the contract to win
- Read the reason code, not the processor's label. It tells you which clause matters. Our guides on not-as-described and cancelled-services disputes show what each one needs.
- Check your deadline. Processors give you days, not weeks. The response deadline calculator works it out from your processor and the dispute date.
- Contact the client once, factually. Ask what went wrong and offer to fix it. Do not threaten them with the contract. A calm message becomes evidence that you tried to resolve it; a threat becomes evidence for them.
- Answer with the contract and the proof of delivery together. The contract shows what was promised; delivery records show it was kept. Either one alone is half an answer. The evidence checklist lists what to include.
- If you lose, the contract still exists. A lost dispute ends the card process, not the client's obligations to you. Whether recovering the fee is worth pursuing, through an invoice or a small-claims court, is a question for a local lawyer.
How Winning Disputes handles this
Winning Disputes makes the contract part of the payment flow. The client signs your agreement before any invoice is issued, and the record keeps the version, time, email and IP address. The scope is broken into deliverables, each with a delivery log and a one-click completion confirmation from the client. If a dispute arrives, the pack sets the signed scope next to the record of what was delivered, which is the comparison an analyst needs. It does not guarantee outcomes; the card issuer decides. See plans and pricing.
Questions
Is a no-chargeback clause illegal?
Writing one is not usually illegal, but it does not bind the bank and cannot remove a cardholder's rights under Regulation Z. For Visa payments taken through platforms such as Stripe, Square or PayPal, Visa's rules require the platform not to let sellers ask cardholders to waive dispute rights, so the clause can put your account at risk while doing nothing for you in a dispute.
Does a signed contract help with a fraud chargeback?
Only if the signature ties the person to the card. A fraud dispute says the cardholder did not make the payment. A contract signed with the same name and email as the cardholder, an ID check that matches, and earlier undisputed payments on the same card are what answer it. A signature from an unverified email does little.
Can I charge a client a fee for filing a chargeback?
You can put a fee in the contract, but charging it to the same card is likely to be disputed too, and it can look punitive to the analyst. If you keep a clause like this, recover the amount by invoice after the dispute closes, and take local legal advice before relying on it.
Is an e-signature as good as a wet signature for disputes?
Legally, yes, in the US under the ESIGN Act. In a dispute, what matters is the record behind it: which version was signed, when, from which email and IP address, and that it happened before payment. A typed name in a reply email is weaker than a click-to-accept record with those details.