Surcharge Disclosure and Signage Requirements
Want your own number first? Check what you're actually paying — takes about two minutes, nothing to install.
Adding a surcharge is the easy part. Staying compliant with the surcharge disclosure requirements is where merchants actually get burned — and it almost never happens because someone did the math wrong. It happens because a sign wasn't at the door, the receipt didn't break the fee out on its own line, or nobody told the card brands before the first transaction ran.
I've looked at a lot of statements from businesses that started surcharging on their own, and the pattern is consistent. The program works fine for a few months. Then a cardholder complains, the complaint gets routed to the acquirer, and the whole thing gets shut off — sometimes with a fine attached. All of it avoidable with about an hour of setup.
Here's what the rules actually ask of you.
Disclose in three places, not one
Most merchants put up one sign and think they're covered. The card brand rules want disclosure at every point where the customer could reasonably back out of the decision:
- Point of entry. A sign at the door, or on your website's landing/checkout entry, before the customer has committed to anything.
- Point of sale. At the register, terminal, or the payment screen — wherever the card actually gets presented.
- The receipt. The surcharge has to print as its own separate line item, clearly labeled, not folded into the subtotal or buried in tax.
That third one is the one people miss. If your surcharge is baked into the item price and never appears on its own line, it isn't a surcharge anymore — it's a price increase you're describing as a surcharge, and that's the version that draws attention.
Tell the card brands before you start
Card brand rules require advance written notice to the networks and to your acquirer/processor before you surcharge your first transaction. The standard notice window is 30 days. This isn't a formality you can backfill later — if a complaint comes in and there's no notice on file, you have no ground to stand on.
If you're going through a processor that sets surcharging up properly, they handle this filing for you. If someone sold you a "surcharge program" and never asked you to sign a notice or confirm your start date, that's a flag worth asking about.
Debit and prepaid can't be surcharged. Ever.
This one has no exceptions and no state variations: you cannot surcharge debit or prepaid card transactions, even when they're run as credit. Your terminal has to identify the card type at the moment of the swipe or tap and drop the fee automatically for debit and prepaid.
That's a configuration issue, not a policy issue. If your equipment can't distinguish card types in real time, you don't have a compliant surcharge program — you have a liability. It's the first thing I check when someone tells me their surcharge setup came from a company they'd never heard of.
The ceiling: your cost of acceptance
A surcharge is allowed to recover what card acceptance actually costs you — it is not a profit center. The card brands cap surcharges at a set percentage, and separately cap you at your own cost of acceptance, whichever is lower. Both matter.
The cap figure has moved more than once in recent years, and I'd rather you confirm the current number with your processor than take a blog post's word for it. The principle doesn't move, though: if your surcharge is higher than what you actually pay to accept the card, you're over the line regardless of what the cap says this year. That means you need to know your effective rate before you set the surcharge — not your quoted rate, your effective rate.
State rules vary, and they layer on top
Card brand rules are the floor, not the whole picture. Some states cap surcharges below the brand cap. Some require specific disclosure language or sign placement. A couple have restrictions or litigation history that make the practical answer different from the statutory one. Rules also change — states have amended these in both directions.
The short version: what's compliant in one state may not be compliant across a state line, and if you operate in multiple states you may need different configurations per location. Check your specific state before you launch, and check again if you expand.
Signage language that holds up
Keep it plain. The disclosure should say that a surcharge is applied to credit card transactions, state the amount or percentage, and make clear it isn't applied to debit. Don't get clever with the wording — the goal is that a customer reading it at the door understands exactly what they'll be charged and why. Vague signage is how a program that's technically compliant still ends up in a dispute.
The honest summary
Surcharge disclosure requirements aren't complicated, but they are specific, and they're unforgiving about the details: three disclosure points, advance notice on file, debit and prepaid excluded automatically, a rate that never exceeds your cost of acceptance, and a state-level check on top of all of it. Get those right and the program is boring in the best way.
If you want to know what surcharging would actually recover for your business before you deal with any of this, run your numbers through the free surcharge calculator — See what surcharging could recover. It takes a couple of minutes and it'll tell you whether the setup work is even worth doing.
This is general information, not legal advice; surcharging rules change and vary by state.
The 12 junk fee lines to look for
The checklist we use when we read a merchant statement — what each line is, and which ones come off for free. Shown on this page as soon as you submit. No document to download.