Is It Legal to Charge Customers a Credit Card Fee? A State-by-State Guide

Short answer: passing a credit card fee to customers is legal in most of the United States, subject to card brand rules and disclosure requirements. Passing a debit card fee to customers is not legal anywhere, in any state, because federal law prohibits it.

That second sentence is where businesses get into trouble. State-level attention has focused on credit surcharging, so owners assume that once their state allows it, all card fees are fair game. They are not. Below is how the rules actually stack up, and why dual pricing avoids most of the complexity.

This is general information, not legal advice — state rules change and litigation continues. Check your own state before you launch anything.

Layer one: federal law on debit cards

The Durbin Amendment to the Dodd-Frank Act prohibits surcharging debit and prepaid card transactions. This is federal, it applies in all fifty states, and no state law overrides it.

The important detail: it follows the card, not the network the transaction runs on. If a customer presents a debit card and the cashier runs it as credit, it is still a debit card, and it still cannot be surcharged. Any program that tells you "run it as credit and the fee is fine" is describing a violation.

This is precisely why terminal configuration matters more than policy language. A compliant surcharge program has to identify card type at authorization and suppress the fee on debit and prepaid cards, every time, without staff intervention.

Layer two: card brand rules on credit cards

Visa, Mastercard, Discover, and American Express all permit credit card surcharging, with conditions that apply regardless of your state:

• A cap on the amount. The surcharge cannot exceed your cost of acceptance for that transaction, and the brands set a ceiling — historically 3% for Visa and Mastercard, with Visa having lowered its cap to 3% from an earlier 4%.
• Disclosure at the entrance and the point of sale. Clear signage before the customer commits.
• Itemization on the receipt. The surcharge appears as its own line, not folded into the total.
• Advance notice. Merchants are expected to notify the card networks and their acquirer before beginning to surcharge.
• Consistent application. You cannot surcharge one brand and not another in a way that discriminates between them.

Break a brand rule and the consequence is not a lawsuit — it is fines passed through your processor, or loss of acceptance. Quieter than a legal problem, and faster.

Layer three: state law on credit surcharges

Most states permit credit card surcharging when the card brand rules and disclosure requirements are met. A small group either restrict it or impose specific requirements, and this is the group to check carefully:

• Connecticut and Massachusetts maintain prohibitions on credit card surcharges.
• Puerto Rico likewise prohibits surcharging.
• New York allows surcharging but requires that the total price a card customer will pay be posted — a fee disclosed only as a percentage added at checkout does not satisfy it.
• Maine requires specific disclosure of the practice.
• California, Florida, Texas, New York, Kansas, and Oklahoma all had surcharge bans that were struck down, narrowed, or left unenforced following First Amendment litigation. Surcharging generally proceeds in these states, but the framing of your disclosure matters more here than almost anywhere else.
• Colorado caps surcharges at 2% or the actual cost of processing, whichever is lower — tighter than the card brand ceiling.

Everywhere else, surcharging with proper disclosure is generally permitted. But "generally permitted" is doing real work in that sentence: these rules move, they get litigated, and a multi-location business can straddle two different regimes.

The distinction nobody explains clearly

Put the two layers together and you get four cases:

• Credit card, permissive state: surcharge allowed, within brand caps and disclosure rules.
• Credit card, restrictive state: surcharge not allowed, or allowed only with total-price posting.
• Debit card, permissive state: surcharge not allowed. Federal law controls.
• Debit card, restrictive state: surcharge not allowed, twice over.

A business that reads "my state allows card surcharges" and applies a flat fee to every transaction has just violated federal law on roughly half its volume, and will not find out from the state — it will find out from a card brand review, or from a customer who knows the rule.

Why dual pricing avoids most of this

Dual pricing does not add a fee. It posts two prices — a cash price and a card price — and lets the customer choose before they commit. That structural difference is what makes it cleaner:

• No credit-versus-debit trap. You are not adding anything to a debit transaction; you are publishing a card price. The federal debit prohibition targets surcharges, and it is not triggered the same way.
• Total price is always posted. The requirement New York imposes and other states favor — the customer sees the actual amount they will pay — is satisfied by the design, not by a workaround.
• Nothing appears after the decision. Most disclosure rules exist because fees surprise people at checkout. Dual pricing removes the surprise, which removes most of the exposure.
• It travels. A single, consistent structure across locations in different states, instead of one policy in Ohio and a different one in Connecticut.

That is not a claim that dual pricing is unregulated. Signage requirements apply, the price difference must reflect real acceptance cost, terminal configuration still has to be right, and some states have display rules that need to be honored. It is a claim that the compliance surface is smaller and steadier — which is why we lead with it. See our complete guide to dual pricing for how it works day to day, and our comparison of all three models for how it differs from cash discounting and surcharging.

Before you launch anything

• Confirm your state's current position, for every state you operate in.
• Verify your terminal distinguishes debit and prepaid cards at authorization.
• Get signage up at the entrance and every point of sale before day one.
• Make sure the receipt shows what the customer actually needs to see.
• Confirm who handles card brand notification — you or your processor.
• Script one sentence for your staff, and make sure everyone uses the same one.

We will check your setup

If you are already passing a fee to customers, it is worth confirming that debit is handled correctly — that is the item we most often find wrong on programs set up elsewhere. If you are considering it, we will show you what a compliant dual pricing program looks like for your business and your state.

Send a recent processing statement through our contact form and we will tell you your real effective rate and what we would change. Our FAQ answers the compliance questions most owners raise first.