Debit vs Credit Dispute Rights: What Changes?

The answer, first The credit side: a real billing-error right The debit gap: what Regulation E does not cover The debit merchant ladder, in order Unauthorized debit: the tiers that do exist Two nuances: wrong amounts and quality complaints The exact questions for your bank FAQ

The answer, first

Card type decides the law, and the law decides whether you have a right or only a request. Credit cards run under Regulation Z and the Fair Credit Billing Act. Debit cards run under Regulation E and the Electronic Fund Transfer Act. The Fair Credit Billing Act covers open-end credit accounts only — it never applies to a debit card, and a debit merchant dispute filed as a Fair Credit Billing Act claim is filed under the wrong law. Regulation E, meanwhile, defines "error" as an unauthorized transfer, an incorrect transfer, an omission from a statement, a bank bookkeeping error, a wrong terminal amount, an unidentified transfer, or a documentation request (12 CFR 1005.11(a)(1)). Read that list twice: there is no entry for goods not delivered, goods not as described, services not rendered, or charges after cancellation. So a debit merchant dispute is not a weaker version of a credit dispute — it is a different kind of case entirely, one the federal rules do not make the bank investigate. The routes that remain are the merchant refund, a network dispute the bank may raise, and bank goodwill, and all three are decided by the merchant, the network, or the bank — not by the law.

The credit side: a real billing-error right

On a credit card, the billing-error route is a genuine right with a deadline, an acknowledgement duty, and a resolution clock. Regulation Z (12 CFR 1026.13(a)(3)) treats a reflection of an extension of credit for property or services not accepted by the consumer, or not delivered as agreed, as a billing error. The written notice must reach the creditor at its billing-inquiries address no later than 60 days after the creditor transmitted the first statement reflecting the error (1026.13(b)). The creditor must acknowledge the notice within 30 days and resolve it within two billing cycles and no more than 90 days (1026.13(c)). And while the error is being resolved, the consumer need not pay the disputed amount, and the creditor may not collect it or report it as late (1026.13(d)). That last point is the practical heart of the credit advantage: the money is the issuer's until the case is decided, so the consumer is not out of pocket while arguing. A wrong amount or a duplicate charge is likewise a billing error to raise with the creditor. A charge after cancellation is less clean — it is not a straightforward non-delivery case — so raise it in writing inside the 60-day window and ask the issuer about the network route for a cancelled recurring charge in the same message, rather than resting the whole claim on one paragraph.

The debit gap: what Regulation E does not cover

The debit gap is best understood as an absence, not a restriction. Regulation E was written for electronic transfers that go wrong in the transfer itself — someone else moved your money, the bank moved the wrong amount, the bank's books are wrong. It was not written for merchants who fail to perform, and its error list proves it: unauthorized transfers, incorrect transfers, omissions, bank bookkeeping errors, wrong terminal amounts, unidentified transfers, documentation requests. A merchant who never shipped, shipped the wrong item, or kept charging after cancellation has committed no error in that list, so a bank owes no Regulation E investigation for a merchant dispute as such. The second half of the gap is the money itself. On a credit card, the disputed amount need not be paid during the investigation. On a debit card, the money left your account the moment you paid, and no federal rule makes the bank put it back while a merchant dispute is investigated. That is why debit merchant disputes feel so much harder than credit ones: the consumer is arguing from an empty account, under no federal deadline, for a refund the law does not require the bank to pursue.

The debit merchant ladder, in order

Work the ladder in order, because each step's evidence feeds the next. Step 1 is the merchant, in writing: state what was wrong and what you want (refund or replacement), and keep the reply or the silence — a bank that sees a merchant who was never asked is slower to help, and a merchant who refuses in writing is evidence. Step 2 is the bank, in writing, asking specifically about the network dispute route: whether the bank can raise a network dispute for goods or services not provided or not as described, which network processed the payment, and what deadline the bank applied. Visa and Mastercard operate consumer-dispute conditions for exactly these problems, but the rules are contractual, the deadline is set by the network and the issuer, and the decision is theirs — so ask for the deadline in writing on the same message, and do not accept a verbal "too late" without the date it is measured from. Ask which network processed the payment, too: a PIN-routed debit payment may not carry the same network rights as a signature-network payment, and the bank is the only party that can tell you which rail your payment used. Step 3 is bank goodwill: ask, plainly, whether the bank will help as a courtesy even though no federal rule requires it. Step 4, if the bank refuses, is to ask for its reasoning in writing — including whether it considered the network route — because a written refusal with reasons is what any later complaint or small-claims step needs, and an unwritten refusal is not a record.

Unauthorized debit: the tiers that do exist

Only one debit lane has federal numbers, and it belongs to unauthorized transfers — the lane this guide's companion checker shares with the fraud-liability calculator, which owns the dollar math. 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 institution 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. If state law or your agreement imposes less liability, the lower figure governs (1005.6(b)(6)), and if delay was due to extenuating circumstances — the regulation gives extended travel or hospitalization as examples — the institution must extend the notification times to a reasonable period (1005.6(b)(4)). An error notice is timely if received no later than 60 days after the institution sends the statement on which the alleged error is first reflected (1005.11(b)(1)(i)). Note the trap this creates: an unauthorized debit transfer reported late can be far more expensive than an unauthorized credit charge, which is capped at $50 under Regulation Z. Speed is the whole game on debit fraud, and the checker works out your tier band from your dates — the fraud-liability calculator then prices it in dollars from the amounts in each window.

When you reported (unauthorized debit)	Your maximum liability tier
Within 2 business days of learning of the loss or theft	Up to $50 — the lesser of $50 or the transfers before notice (1005.6(b)(1))
After 2 business days, inside the 60-day statement window	Up to $500 — the tier-1 figure plus later transfers before notice, if the bank establishes they would not have occurred had notice been timely (1005.6(b)(2))
After the 60-day statement window	Up to $500 plus post-window transfers with no cap, on the same establishment condition (1005.6(b)(3))

Two nuances: wrong amounts and quality complaints

Two scenarios change the answer, in opposite directions, and both are worth knowing before you file. First, a wrong amount or a duplicate charge is not a merchant-quality complaint: Regulation E defines error to include an incorrect electronic fund transfer (1005.11(a)(1)(ii)) and a computational or bookkeeping error by the institution (1005.11(a)(1)(iv)), so a charge for the wrong amount, or the same charge twice, may count as a Reg E error. The word is "may" — the bank decides on your facts — so send an error notice within 60 days of the statement showing the charge and ask about the network route in the same message, rather than assuming either lane. Second, a complaint purely about the quality of goods you accepted and kept is excluded on both card types: the CFPB comment on 1026.13(a)(3) states that paragraph does not apply to a dispute relating to the quality of property or services the consumer accepts, and Regulation E has no quality category at all. For a quality complaint, the routes are the merchant, the network dispute, and — on a credit card — the claims-and-defenses question to put to your issuer under 12 CFR 1026.12(c), whose conditions this guide does not state because they were not verified for this build. Filing a quality complaint as a billing error, on either card, is the fastest way to a correct rejection.

The exact questions for your bank

Put these in writing, in one message, and keep the reply. "Can you raise a network dispute for goods or services not provided / not as described for this charge, and what deadline applies?" "Which network processed this payment — was it PIN-routed or signature-network?" "If you decline the network route, please confirm in writing that you considered it and state the deadline you applied." "If this were an incorrect transfer under 12 CFR 1005.11(a)(1)(ii) [for a wrong amount or duplicate], would you treat my message as an error notice?" And on a credit card, additionally: "Please treat this as a billing-error notice under 12 CFR 1026.13 and confirm acknowledgement within 30 days." A bank that answers in writing has given you a route or a record. A bank that answers only by phone has given you neither — follow every call up in writing the same day.

FAQ

Can you dispute a debit card charge?

You can ask your bank about a debit card charge, but you do not have the same rights as a credit card. Regulation E covers unauthorized transfers and bank errors — it gives no billing-error right for a merchant who failed to deliver, delivered something different, or charged after cancellation. The routes are the merchant refund, a network dispute your bank may raise, and bank goodwill.

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.

What is my liability if someone used my debit card without permission?

Under 12 CFR 1005.6, notice within 2 business days after learning of the loss or theft 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.

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 guide 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.