Does the Fair Credit Billing Act protect debit card disputes?

No. The Fair Credit Billing Act, implemented through Regulation Z, governs open-end credit accounts — credit cards and revolving charge accounts. It does not cover debit cards, which fall under Regulation E. A debit merchant dispute must never be filed as a Fair Credit Billing Act claim.

I paid by debit and the item never arrived. What do I do first?

Ask the merchant first, in writing, and keep the reply or the silence. Then ask your bank in writing whether it can raise a network dispute for goods or services not provided, and ask for the network deadline in writing — this checker states no network day-count, because the network rulebooks are contractual and no deadline was verified to a primary network source for this build.

Is a wrong amount or duplicate debit charge treated the same as a merchant dispute?

Not necessarily. Regulation E defines error to include an incorrect electronic fund transfer (12 CFR 1005.11(a)(1)(ii)), so a wrong amount or duplicate charge may count as a Reg E error — but the bank decides on your facts. Send an error notice within 60 days of the statement showing the charge, and ask about the network route in the same message.

Can You Dispute a Debit Card Charge? Reality Checker

Can You Dispute a Debit Card Charge?

Short answer: not the way a credit card can. On a credit card, a merchant who never delivered, or delivered something different from what was sold, is a billing error the creditor must investigate under the Fair Credit Billing Act. On a debit card, that same complaint has no federal lane at all: Regulation E covers unauthorized transfers and bank errors, and its list of errors contains no category for a merchant who failed you. Your money has already left your account, and no federal rule makes the bank put it back while a merchant dispute is investigated. What remains is real, but it is not a right — the merchant refund, a network dispute your bank may raise, and bank goodwill. This checker routes your case by card type, authorization, and scenario, and for an unauthorized debit transfer it works out your Regulation E liability tier from your dates.

By Muhammad Umer, founder of Chargeback Clock · Updated November 2026

How the checker works

The gap, in one table

Two federal rules divide this whole question, and neither covers both card types. Credit cards run under Regulation Z and the Fair Credit Billing Act: a billing error includes property or services not accepted by the consumer or not delivered as agreed (12 CFR 1026.13(a)(3)), a written notice must reach the creditor within 60 days of the first statement showing the error, and while the error is being resolved the consumer need not pay the disputed amount (1026.13(d)). Debit cards run under Regulation E: an error means an unauthorized transfer, an incorrect transfer, an omission, a bank bookkeeping error, a wrong terminal amount, an unidentified transfer, or a documentation request (12 CFR 1005.11(a)(1)) — and a merchant who failed to deliver, delivered something different, or charged after cancellation appears nowhere in that list. That absence is not a technicality; it is the reason a debit merchant dispute has no federal investigation right, and why filing it as a billing-error claim wastes the time that should go to the merchant and the network route.

	Credit card	Debit card
Merchant never delivered / not as described	Billing error under 1026.13(a)(3); creditor must investigate	No federal billing-error right; merchant refund, network dispute, goodwill
Poor quality, accepted and kept	Not a billing error either (CFPB comment on 1026.13(a)(3)); ask about network route and claims and defenses	No federal right; merchant and network routes only
Wrong amount / duplicate charge	Billing error; raise with the creditor	May count as an incorrect transfer under 1005.11(a)(1)(ii) — bank decides
Unauthorized use	Liability capped at $50 under Regulation Z	Regulation E tiers: up to $50, up to $500, then post-window transfers uncapped
Money while the case is open	Need not pay the disputed amount during a billing-error investigation (1026.13(d))	Already left your account; no federal rule puts it back during a merchant dispute

The unauthorized debit tiers, from your dates

Only one debit lane has federal numbers, and it belongs to unauthorized transfers, not merchant disputes. Under 12 CFR 1005.6, notice within 2 business days after learning of the loss or theft of the access device caps liability at the lesser of $50 or the transfers before notice; later notice caps it at $500, provided the bank establishes the later transfers would not have occurred had notice been timely; and transfers after the 60-day statement window and before notice are added with no cap, on the same condition. This checker returns the tier band from your dates. For the dollar figure on your amounts, use the Debit Card Fraud Liability Calculator, which applies the same tiers to the amounts taken in each window and adds the provisional-credit timeline — that tool owns the dollar math, and this one deliberately does not repeat it.

What the network route is — and what it is not

The network route is the most misunderstood step in debit disputes, because it looks like a chargeback and sounds like a right. It is neither, legally. Visa and Mastercard operate consumer-dispute conditions for goods or services not provided or not as described, and your bank may raise one for your case — but the rules are contractual, the deadline is set by the network and the issuer, and the decision is theirs. That is why this checker states no network day-count, fee, or success figure: the network rulebooks are not public statutes, and no such figure was verified to a primary network source for this build. Ask your bank, in writing, whether it can raise a network dispute, which network processed your payment (a PIN-routed payment may not carry the same network rights, so ask that question too), and what deadline it applied. A bank that answers those three questions in writing has given you a route; a bank that only says "Regulation E does not cover this" has told you the law correctly and stopped one step short.

Want the full debit vs credit playbook?

The credit billing-error notice, the debit merchant ladder step by step, the unauthorized tiers with worked dates, the wrong-amount nuance, the quality-complaint trap, and the exact questions to put to your bank in writing — with the checker above the fold.

Read the debit vs credit dispute rights guide

Sources (verified November 4, 2026): 12 CFR 1005.6 (eCFR text) — liability tiers (b)(1) $50, (b)(2) $500, (b)(3) post-60-day uncapped, (b)(4) extenuating circumstances, (b)(6) state law or agreement; 12 CFR 1005.11 (eCFR text) — error definition (a)(1)(i)–(vii) with no merchant-fulfilment category, error-notice timing (b)(1)(i) 60 days after the statement, investigation and provisional credit (c); 12 CFR 1026.13 (CFPB text) — billing-error definition (a)(3) not accepted or not delivered as agreed, CFPB comment that (a)(3) does not apply to a dispute about the quality of property or services the consumer accepts, notice deadline (b) 60 days after the first statement, resolution (c) acknowledge within 30 days and resolve within two billing cycles and no more than 90 days, rules pending resolution (d) need not pay the disputed amount; Regulation Z governs open-end credit, Regulation E governs debit and electronic transfers. Network framing is stated without a day-count, fee, or success figure, because the Visa and Mastercard rulebooks are contractual and no such figure was verified to a primary network source for this build. Your bank, the network rules, and your account agreement are the final word.

General information only — not legal advice. This checker gives a general read of your situation against Regulation E and Regulation Z as checked on November 4, 2026. It does not predict whether a merchant, a bank, or a card network will return money. Your bank and your account agreement control your specific case.

← Back to homepage