Chargebacks and Payment Disputes for Small Businesses

A chargeback is not a request you can simply say no to — it's the cardholder's bank forcibly reversing a payment, and the money usually leaves your account before you get any chance to respond. The cardholder doesn't come to you first; they contact the bank that issued their card (the "issuer"), the issuer reviews the claim, and if it sides with the cardholder, it pulls the disputed funds from your merchant account through your payment processor. You often find out after the fact, with a short window to fight it. Understanding where the rules actually come from, what evidence works, and what's really at stake — your ability to keep accepting cards at all — is the difference between a manageable cost of doing business and a real threat to your business.

Where the rules actually come from

This is the part most merchants get wrong, and it matters, because the federal law everyone cites is narrower than the system you actually deal with. Three separate layers are in play:

• Credit cards — the federal floor. The Fair Credit Billing Act, implemented through Regulation Z, gives consumers "billing error" rights on open-end credit accounts. Those rights are narrower than most people assume: a billing error covers charges the cardholder didn't make, wrong amounts, accounting errors, credits you never posted, and property or services not accepted or not delivered as agreed — which the official interpretation extends to delivery of something different from what was agreed, and to late delivery. See the CFPB's text of Regulation Z § 1026.13.
• Credit cards — quality disputes are a different rule. A complaint about the quality of goods or services the customer accepted is not a billing error. It runs instead through the cardholder's right to assert claims and defenses under Regulation Z § 1026.12(c) — and that right carries real conditions: the cardholder generally must have made a good faith attempt to resolve it with you first, the transaction must exceed $50, and it must have occurred in the cardholder's state or within 100 miles of their address. (Those dollar and distance limits fall away when the issuer is effectively the seller or solicited the sale.)
• Debit cards and other electronic transfers run on an entirely separate framework, Regulation E, with its own definition of "error" and its own resolution clock — see § 1005.11 and the unauthorized-transfer liability rules at § 1005.6. A bank investigating a debit dispute may issue the customer provisional credit while it works, which is one reason debit disputes can feel like they move differently than credit disputes. Regulation E is not the Fair Credit Billing Act, and the two should not be described interchangeably.
• The card networks — Visa, Mastercard, American Express, Discover — layer their own operating rules on top of all of it. These are private contracts you agreed to when you signed your merchant processing agreement, not federal or state law. They set the reason codes, the evidence formats, the response deadlines, and the chargeback-ratio thresholds that can get an account flagged or terminated.

Here's the practical upshot: most chargebacks you see are running on network rules, not on the federal statute. The networks voluntarily let cardholders dispute things the Fair Credit Billing Act would not reach — including quality complaints, without the $50 or 100-mile conditions. So don't assume a dispute is invalid because it falls outside the federal billing-error definition. The federal law is a floor, not a ceiling, and your contract with your processor is what actually governs your day-to-day.

Why a chargeback can land months after the sale

The federal billing-error route generally requires the cardholder to notify the issuer within 60 days after the statement showing the charge. But card network rules commonly allow a considerably longer window than that federal 60 days — and the clock can run from the expected delivery date rather than the transaction date for undelivered goods or services, which is how a dispute on a long-lead custom order or a prepaid future service can surface much later than you'd expect. The exact windows are set by each network's rules and change over time, so confirm the window that applies to your account with your processor rather than assuming a number. The operational lesson: keep your transaction records, delivery proof, and customer communications well past the point where the sale feels finished.

The common reasons customers dispute a charge

Every dispute arrives with a reason code that tells you what the issuer believes happened. The categories that come up most often:

• Fraud / unauthorized transaction — the cardholder says they never made or approved the purchase.
• Product or service not received — the cardholder says nothing showed up.
• Not as described / defective — what arrived doesn't match what was advertised or agreed.
• Subscription or recurring billing — the cardholder says they canceled, never agreed to the recurring charge, or didn't get clear notice of a renewal.
• Duplicate charge or credit not processed — the same transaction was billed twice, or a promised refund never showed up.

The reason code drives what evidence will actually help. Fighting a "not received" dispute with proof of delivery works; fighting it with a copy of your refund policy usually doesn't.

Representment: what to do when a chargeback hits

You have the right to respond to most chargebacks through a process the networks call representment — re-presenting the transaction with documentation, through your processor, arguing the charge was valid. The practical sequence:

1. Read the notice the day it arrives. It will show the reason code and your response deadline. Calendar the deadline immediately — missing it usually means an automatic loss no matter how strong your case was.
2. Decide whether to fight it. If the customer already got a legitimate refund, or the charge really was an error on your end, take the loss and move on. Representment costs time and often a fee, and you won't win a case where the customer is right.
3. Pull the evidence that matches the reason code (see below) and assemble it exactly as your processor's dispute portal requests. Sloppy or incomplete packets lose otherwise-winnable cases.
4. Submit before the deadline through your processor's dispute management tool.
5. Know that representment may not be the end. Under network rules a dispute can escalate further — commonly called pre-arbitration and then arbitration — and those stages carry their own fees, which can exceed the disputed amount on a small ticket. Ask your processor what escalation costs before you chase a small sale on principle.
6. Track the outcome. A rash of "not received" disputes may mean a real fulfillment problem worth fixing, not just a bank being difficult.

The evidence that actually moves the needle

Not all evidence is created equal. What tends to work:

• Proof the cardholder authorized the charge — a signature, a recorded card-present transaction, or a timestamped checkout acceptance of your terms of sale.
• Delivery confirmation and tracking — proof the item reached the address on file, or that a service was performed, ideally tied to the order and dated.
• Communications with the customer — emails, texts, or support tickets showing what was promised, what was delivered, and any resolution you offered before the dispute was filed. For a quality-type dispute, evidence that the customer never raised the problem with you first is directly relevant, since the federal claims-and-defenses route assumes they tried.
• Your posted refund and cancellation policy — as shown to the customer at the time of purchase, not written afterward.
• Fraud-screening records — Address Verification Service (AVS) and CVV match results, and 3-D Secure (the step-up authentication branded as "Verified by Visa" or "Mastercard Identity Check") results. Beyond showing the transaction passed standard checks, network rules generally shift liability for fraud-type chargebacks to the issuer on transactions authenticated through 3-D Secure — the specifics are set by each network and change, so ask your processor how that applies to your setup.

What tends not to work: your own certainty that the customer is lying, general good-customer-service arguments with no documentation attached, or evidence that doesn't respond to the stated reason code.

Friendly fraud is real — but don't cry fraud on everything

"Friendly fraud" describes a cardholder disputing a charge they actually authorized — buyer's remorse dressed up as a fraud claim, a family member's purchase the cardholder doesn't recognize, or someone who forgot they subscribed. It's a genuine cost for merchants, and it's frustrating precisely because you know what happened and can't say so directly to the decision-maker. But treating every dispute as fraud and reflexively fighting all of them is a losing strategy: issuers see through weak or irrelevant evidence, and a habit of fighting everything burns time on cases you can't win while distracting from the ones — genuine service failures, unclear billing — where a refund up front would have been cheaper and better for the relationship.

Why your chargeback ratio is the real risk

A single chargeback costs you the sale, usually a fee, and your time. The bigger threat is cumulative: card networks track your chargeback ratio — disputes as a share of your transactions — and an elevated ratio triggers consequences that scale up:

• Chargeback monitoring programs run by the networks, which flag merchants above a threshold for closer scrutiny and remediation requirements.
• Fines assessed by the networks and passed through by your processor.
• Reserves — your processor holding back a portion of your sales as a cushion against expected disputes, which hits your cash flow directly.
• Loss of your merchant account — your ability to accept cards at all, terminated by your processor or acquiring bank. This is the outcome that can genuinely end a card-dependent business, and processors are generally not required to give you extensive warning.

Ratio thresholds, fine amounts, and program names are set by network rules and your processor's contract, and they change — so don't anchor on a fixed number you read somewhere. Ask your processor directly what your current standing is, how they calculate the ratio, and what triggers escalation under your specific agreement. The guide on choosing a payment processor covers what to look for in that contract before you sign.

Preventing chargebacks before they start

• Use a clear billing descriptor. The charge on the customer's statement should be instantly recognizable as your business — a cryptic descriptor is one of the most common triggers for "I don't recognize this charge" disputes, and it's usually a five-minute fix with your processor.
• Be reachable. A customer who can get a real person to resolve a problem is far less likely to go straight to their bank. Your phone number and a monitored inbox are chargeback prevention tools.
• Post a clear refund and cancellation policy at checkout and honor it consistently.
• Refund before it becomes a chargeback. If a customer has a legitimate complaint, a prompt refund is almost always cheaper than fighting a dispute — and a refund is not a chargeback, so it doesn't enter your chargeback ratio the way a dispute does.
• Get recurring billing right. Recurring-billing disputes are disproportionately driven by customers who felt trapped trying to cancel. Beyond the network reason codes, online recurring charges are regulated federally under the Restore Online Shoppers' Confidence Act — which broadly requires clear disclosure of the terms before you take billing information, the customer's express informed consent, and a simple way to stop recurring charges — and separately by state automatic-renewal laws that vary and have been changing. This area has also seen active federal rulemaking and litigation, so confirm the current requirements rather than relying on what was true a year ago. The guide on website terms of service goes further into disclosure and cancellation terms.

Putting it together

The instinct when a chargeback hits — that this is unfair and you should fight it — is understandable, and sometimes right. But the merchants who handle disputes well treat them as an operations problem rather than a personal one: they know the reason codes, they keep records long enough to prove delivery months later, they refund fast when the customer has a point, and they fight selectively with evidence that matches the code. Above all they watch the ratio, because the account itself is the asset worth protecting. If disputes are threatening your processing relationship, or a reserve or termination is putting real pressure on your cash flow, that's worth a conversation with a qualified attorney or CPA — and free help is available through your local Small Business Development Center or SCORE via SBA local assistance.

This is general business information, not legal, tax, or financial advice.