Is It Legal to Add a Credit Card Surcharge?
Surcharging is legal in most states, but four layers of rules apply at once and the debit exclusion is where most operators are quietly out of compliance.
Food Truck or Restaurant Owner? Sign up for the Culinary Entrepreneur Newsletter!
Short answer: in most of the United States, yes — with conditions, and the conditions are where operators get in trouble.
Longer answer, and the one I'd give you across a table: surcharging is permitted in most states, the card networks impose their own rules on top of state law, a few states restrict or prohibit it, and that list has moved more than once in recent years because it keeps getting litigated. Anyone who hands you a laminated map of banned states is selling you certainty they don't have.
So instead of a map that goes stale, here's what actually governs your sign and your receipt — and how to do this in a way that survives someone challenging it.
What a surcharge actually is
A surcharge is an extra amount added to the price when a customer pays by credit card. That's the whole definition, and every rule below follows from it.
Two things it is not:
A cash discount is not a surcharge. In a cash discount model your posted price is the card price and you take money off for cash. Different mechanism, different rules.
A convenience fee is not a surcharge either. That's a charge for using an alternative payment channel — paying by phone instead of in person, say — and it carries its own separate network rules.
Operators use these three words interchangeably. The rules do not.
The four layers of rules you're subject to at once
This is the part almost nobody lays out, and it's exactly why "is it legal" has no one-word answer. All four apply simultaneously, and the strictest one wins.
State law. Most states permit surcharging. A small number restrict or prohibit it, and that set has shifted as cases move through the courts. Your state attorney general's office is the authority here — not your sales rep.
Card network rules. Visa, Mastercard, and the rest each publish surcharging rules that apply regardless of your state: how much you can add, what you must disclose, and where. They bind you through your merchant agreement.
Your merchant agreement. Your processor is allowed to be stricter than the networks, and some prohibit surcharging outright. Read yours before you print a sign.
Debit is treated differently. Federal law handles debit separately, and surcharging debit and prepaid transactions is generally not permitted even in places where credit surcharging is perfectly fine.
That last point deserves its own paragraph. If your POS adds a percentage to every card transaction without distinguishing debit from credit, you may have a problem right now — and almost nobody who has this problem knows it. It's a configuration mistake, not a decision anyone made.
The rules that bite most often
Assuming your state allows it and your processor permits it:
There's a cap, and it's tied to your actual cost. Network rules limit the surcharge to what it genuinely costs you to accept that card. You can't surcharge above your cost of acceptance, and you can't run it as a profit center.
You must disclose before the transaction. At the entrance, at the point of sale, and again on the receipt as its own line. Not revealed at the end.
It has to be a separate line item. Bundling the cost into your item prices is legal — but then it isn't a surcharge and you can't describe it as one.
You generally must notify your processor first. Some require written notice with lead time.
Debit and prepaid are excluded, per above.
How to do it without getting a letter
Confirm your own state. Ask your state attorney general's office or your attorney. Not a blog, and not a rep who's compensated on the sale.
Read your merchant agreement for a surcharging clause.
Notify your processor in writing and keep the confirmation.
Compute your real cost of acceptance — your effective rate, total fees divided by total card volume. Your surcharge cannot exceed it.
Configure your POS to exclude debit and prepaid. Then test it with an actual debit card and read the receipt.
Post signage at the entrance and at the point of sale, and confirm the receipt shows the surcharge separately.
Re-check annually. State law and network rules both move.
Should you do it at all?
Here's the part the processor blogs skip, because they're compensated on volume.
Surcharging moves your processing cost onto the customer. It doesn't eliminate the cost, and it isn't free to you — you're trading margin for friction. Three things I've watched matter more than the compliance question:
It changes your card mix. Some customers switch to debit or cash to dodge the fee. That's fine, except debit can't be surcharged, so your actual savings come in smaller than the sales sheet promised.
It shows up in reviews. Not always, not fatally, but it does.
It's an operational cost. Your staff will be asked about it at the window, mid-rush, by somebody who's annoyed. That's training time, and it's real.
None of that means don't. Plenty of operators surcharge and are glad they did — particularly thin-margin, high-ticket, card-heavy operations. It means treat it as a pricing decision with a downside rather than as free money.
Here's the version I'd test first: raise your prices enough to absorb the cost and skip the surcharge entirely. It's simpler, it has no compliance surface at all, and customers react to a posted price far more calmly than to a fee. Sometimes that's the better trade. Sometimes it genuinely isn't. Run the math both ways before you print anything.
Where doing this yourself breaks down
Compliance here isn't a one-time setup. It's a thing you have to keep true. The debit exclusion has to still work after your next menu change, and your surcharge has to stay under a cost of acceptance that drifts every time your card mix moves.
Verifying that means knowing your effective rate continuously, which means your processing costs and your transaction data have to live in the same place. That's how we built Avocado — payments and orders in one system, so what you actually paid to accept cards last month is a question you ask rather than a number you reconstruct from a PDF. Our rates are published, so the cost you'd be surcharging against isn't a mystery either.
And if you ask us whether you should surcharge, you'll get the honest answer, which is frequently no.
Avocado is a POS built for independent restaurants and food trucks. We're operators first, and we'd rather tell you the honest version than the version that closes faster.
This is operator experience, not legal advice. Surcharging is governed by state law, card network rules, and your own merchant agreement at the same time; the rules differ by state and change often, and several are actively being litigated. Confirm your specific situation with your processor and your attorney before adding any fee, and do not treat this post — or any published list of states — as authority.