Skip to main content

Consumer Chargeback Rights

TL;DR
  • Got a dispute? Match the claim to the table below
  • Cardholders have a legal right to dispute charges under the Fair Credit Billing Act (FCBA) - you cannot stop them from filing
  • The 60-day dispute window runs from the billing statement, not the transaction date
  • "Not as described" and "not received" disputes are the most common winnable categories; fraud disputes from stolen cards are nearly impossible to win without 3DS
  • Knowing which disputes are legally mandated vs. network policy determines your response strategy

Your customers have legal rights to dispute charges. Understanding these rights helps you know what you're fighting against and why some disputes are unwinnable from the start.

CP vs CNP

Consumer rights apply to card-present and card-not-present alike, but CNP merchants carry more exposure. Without a signature or a chip read, you've got less proof the cardholder authorized anything.

The Fair Credit Billing Act (FCBA)​

The FCBA is a 1974 US federal law that gives credit card holders the right to dispute billing errors. That's why chargebacks exist at all. The networks built their dispute processes on top of it.

Consumer liability cap: Under the FCBA, consumers are liable for a maximum of $50 in unauthorized credit card charges (15 U.S.C. 1643). In practice most issuers waive even the $50 and run zero-liability policies. So on a fraud chargeback the consumer doesn't pay anything, which is worth remembering when you wonder why they filed.

The uncomfortable truth: The law was designed to protect consumers, not merchants. The burden of proof falls on you.

What Customers Can Dispute​

The FCBA covers these "billing errors":

Dispute TypeWhat It MeansMerchant Impact
Unauthorized chargesCharges customer didn't makeHard to win without 3DS
Wrong amountCharged $150 instead of $15Check your systems
Goods not receivedCustomer never got the orderNeed delivery proof
Not as describedProduct different from listingSubjective, hard to win
Damaged on deliveryArrived brokenCarrier issue, still your problem
Credit not processedRefund promised but not givenCheck refund logs
Calculation errorsMath wrong on statementRare, easy to verify

The 60-Day Window​

Customers have 60 days from the statement date to dispute a charge under the FCBA. This is the legal minimum.

But here's what matters for you: Card networks extend this.

NetworkDispute WindowNotes
Visa120 daysFrom transaction or expected delivery
Mastercard120 daysFrom transaction or expected delivery
American Express120 daysSometimes longer for certain disputes
DiscoverNot publishedNetwork filing window not published

Discover doesn't publish its dispute windows. For your own response, work to the date on your notice.

Scale callout: High-value or delayed-delivery businesses (furniture, custom orders, travel) see disputes months after the sale. That's a cash flow problem, so plan for it.

How the Dispute Process Works (Customer Side)​

Understanding the customer experience helps you anticipate disputes:

  1. Customer notices charge - On statement or in banking app
  2. Customer contacts bank - Through app or phone, one-click dispute
  3. Bank issues provisional credit - Customer gets money back immediately
  4. Bank investigates - Must acknowledge within 30 days
  5. Bank decides - For a qualifying US credit-card billing-error notice, resolve within two complete billing cycles, and no later than 90 days after receipt
  6. Merchant notified - You get the chargeback notification

Key insight: The customer doesn't have to contact you first. They can go straight to their bank. Many banks actively encourage this with "Dispute this charge" buttons in their apps.

What the Bank Must Do​

Under FCBA, the issuing bank must:

RequirementTimeframeWhat It Means
Acknowledge dispute30 daysWritten confirmation to customer
InvestigateTwo complete billing cycles, no later than 90 days after receiving the billing-error noticeReview evidence
Don't collect disputed amountDuring investigationCustomer doesn't pay
Report as disputedIf reporting to bureausCan't just report as delinquent

What This Means for Merchants​

You Start at a Disadvantage​

The FCBA creates an asymmetric system:

CustomerMerchant
One-click disputeMulti-step representment
Immediate provisional creditMoney held for months
No proof required to fileFull evidence burden
60 days under federal law, longer through the card networkThe date on your notice (Stripe's usually runs 7 to 21 days)

Some Disputes Are Unwinnable​

When the customer has a statutory right you can't overcome:

ScenarioWhy You Lose
No 3DS on fraudUnauthorized charge, no authentication proof
No delivery confirmationGoods not received, no proof otherwise
No refund processedCredit not issued, system logs will show
Signature not obtained (CP)Authorization issues

Where You Can Win​

Disputes where evidence can overcome the claim:

ScenarioWinning Evidence
Friendly fraud with 3DS3DS authentication + delivery proof
"Not received" with trackingSigned delivery confirmation
"Not as described" with specsProduct listing matching delivery
Prior customer relationshipCE 3.0 matching device/IP

Beyond FCBA: Other Consumer Protections​

Regulation E (Debit Cards, ACH, P2P)​

Regulation E covers electronic fund transfers: debit cards, ACH debits and P2P payments. It isn't the same rulebook as credit, and it doesn't hit you the same way.

Why merchants care: The dispute process works differently, and your ability to fight back varies by payment type.

Payment TypeDispute MechanismCan You Fight It?Merchant Impact
Credit cardNetwork chargebackYes - full representmentFCBA rules, 7-45 days to respond
Debit cardNetwork chargebackYes - similar to creditUS Regulation E investigation and provisional-credit rules, with conditional extensions
ACH debitReturn codes (R10, R29)No card-style appeal at Stripe or Square for an ordinary timely returnAuthorization inquiries and separate bank claims can still matter
P2P (Zelle)Bank-to-bank pushNoIrrevocable once sent
P2P (Venmo/Cash App)Platform disputeLimitedPlatform decides, not network rules

The practical differences:

US debit cards: Regulation E generally starts with 10 business days to determine whether an error occurred. An institution meeting the provisional-credit and other conditions can extend the investigation, generally to 45 days or 90 days for specified cases, including point-of-sale debit transactions. Credit-card billing errors use two complete billing cycles, capped at 90 days. These are bank-to-consumer duties, not your merchant response deadline. CFPB debit rule and credit rule, opened 2026-10-22.

ACH debits: Stripe and Square don't offer a card-style appeal of an ordinary timely ACH return. Contact the customer about the unpaid invoice. Supply authorization records if your provider requests them for an inquiry. Separate bank warranty claims can still follow; see ACH return timing.

P2P payments: Zelle is a push payment - once the customer sends, it's gone. Venmo and Cash App have dispute processes, but they're platform-specific, not network-governed. If you accept P2P, understand you're outside the card network chargeback system entirely.

What to do differently:

If You Accept...Adjust Your Approach
Debit cardsSame fraud prevention as credit; disputes work similarly
ACH for subscriptionsVerify bank account ownership; have clear authorization records
ACH for one-timeHigher risk; consider only for trusted/verified customers
P2P paymentsTreat as cash-equivalent; no dispute protection for you

Received an app or bank notice as a seller? Check the account, transaction and response route.

State Laws​

Some states add protections:

  • California: Additional consumer rights
  • New York: Specific disclosure requirements
  • Various states: Subscription cancellation laws

Practical note: These rarely change your chargeback strategy, but they affect customer communication and refund policies.

Test to Run​

Pull your last 20 chargebacks. For each one:

  1. Did the customer contact you first? (Expect: no)
  2. Was the dispute filed within the applicable legal or network window? Amex has exceptions; Discover's network filing window isn't published.
  3. Did you have evidence that could overcome their claim?

If customers never contact you first and you're losing disputes past 60 days, you're seeing the FCBA in action.

Where This Breaks​

Long delivery windows: If you sell furniture that takes 12 weeks to deliver, customers can dispute well after you've fulfilled. Visa and Mastercard allow 120 days from expected delivery; don't assume that starting point for Amex. Amex has exceptions; Discover's filing window isn't published.

Digital goods: The FCBA covers "goods not received" but digital delivery is hard to prove without proper logging. See Digital Goods Evidence.

Subscriptions: Customers dispute months of charges at once. Check the window for each transaction. Visa and Mastercard generally allow 120 days; Amex has exceptions, and Discover's filing window isn't published. See Recurring Billing Compliance.


What This Means for Your Business Type​

Business TypeKey Right to KnowPractical Implication
SaaS / DigitalVisa/Mastercard: 120 days; Amex up to 120, with exceptions; Discover: Not publishedKeep login/usage logs for 120+ days minimum
Physical Goods"Not received" disputes valid until delivery confirmedAlways use trackable shipping with delivery confirmation
Services"Not as described" disputes have broad interpretationDocument scope in writing BEFORE starting work
SubscriptionsCancellation disputes valid if process was unclearMake cancellation as easy as signup

Discover doesn't publish its dispute windows. For your own response, work to the date on your notice.

Work Within the Rules

Consumer protection laws exist to protect consumers, not merchants. You're working inside those rules, not around them. What wins is evidence and documentation, so see compelling evidence.

Next Steps​

Understanding disputes better?

  1. Learn the chargeback lifecycle - Full process flow
  2. Study reason codes - Why disputes are filed
  3. Review evidence requirements - What wins

Reducing disputes?

  1. Enable 3D Secure - Shift liability, prove authorization
  2. Fix your descriptors - Prevent "don't recognize" disputes
  3. Set up alerts - Resolve before chargeback

Already in a dispute?

  1. Check reason code guide - Specific response requirements
  2. Build evidence package - What to submit
  3. Submit representment - Fighting the chargeback

Something wrong on this page? Email matt at paymentsandrisk.com and say what needs fixing.