Surcharging legally
in 2026

Surcharging — adding a fee when a customer pays with a credit card to recover your processing cost — is one of the most misunderstood tools in payments. It is broadly legal today, the result of a 2013 settlement that ended Visa and Mastercard's old no-surcharge rules. But "legal" is not "do whatever you want." Surcharging lives at the intersection of network rules, state law, and disclosure mechanics, and all three change. This piece maps the structure so you can implement it cleanly — and tells you exactly where to go confirm the current rules before you flip the switch.

Surcharging is not the same as cash discounting

The two get used interchangeably, and that confusion is where compliance problems start. They are different programs with different rules.

• Surcharging adds a fee on top of the listed price when a customer chooses to pay by credit card. The card price is the base price plus the surcharge. This is the program governed by the network caps, debit rules, and disclosure requirements below.
• Cash discounting works the other way: you post a single price that already assumes a card payment, then take money off for customers who pay with cash or check. Structured correctly, a true cash discount is generally treated differently from a surcharge — but only if it is genuinely framed as a discount, not a surcharge wearing a disguise.

Regulators and the networks look at substance, not labels. Calling a credit-card add-on a "cash discount" while charging the same base price to everyone does not make it one. Decide which program you are actually running, then follow that program's rules.

The network rules: caps, debit, disclosure, registration

Even where state law permits surcharging, you still answer to Visa and Mastercard. Their rules are national, they apply regardless of where you operate, and they are the part most merchants get wrong. The core constraints have historically included the following — but treat each as something to verify against the current network manuals, because the networks revise them:

• A cap on the surcharge. The networks have long limited credit surcharges to your actual cost of acceptance, subject to a maximum percentage. You cannot turn surcharging into a profit center — it is cost recovery, not revenue.
• Debit and prepaid cannot be surcharged. Period. This is the single most common violation. You may surcharge credit cards only. Surcharging a debit or prepaid card — even a debit card run as "credit" at the terminal — is not allowed. Your system has to distinguish card types correctly.
• Disclosure at the door and online. Customers must be told about the surcharge before they pay — at the point of entry or store entrance, at the point of sale, and on any e-commerce checkout page.
• Disclosure on the receipt. The surcharge must appear as a separate, clearly labeled line item on the transaction receipt — not folded into the total.
• Registration with the networks. Before you start, you are generally required to notify Visa and Mastercard (and your acquirer or processor) of your intent to surcharge, typically a set number of days in advance. Skipping this step is what gets programs shut down.

Surcharging is cost recovery, not a revenue line. The moment your fee exceeds your cost of acceptance, you are out of bounds.

The state landscape: it varies, and it moves

Here is the part that demands the most caution, so we will be direct about the limits of any general guidance: state law on surcharging varies, and it has changed repeatedly. Surcharging is permitted in most states, but a handful of states and jurisdictions have historically restricted, prohibited, or litigated it, and several of those restrictions have been challenged in court — sometimes successfully, sometimes leaving the law in flux.

Because of that history, we are deliberately not naming specific states as "banned" or "allowed" here, and you should not rely on any blog — including this one — for that determination. A state's posture can turn on a single court ruling or a new statute, and what was true last year may not be true today. Some states also layer in their own disclosure or signage requirements on top of the network rules.

What is durable is the workflow:

• Confirm current law for every state you operate in. Verify with your state's statutes, your attorney, or your processor's compliance team before launching — and re-check periodically, not just once.
• Treat the strictest rule as the binding one. If you operate across state lines, your program has to satisfy the network rules and the most restrictive applicable state law.
• Document your basis. Keep a record of the cap you applied, the disclosures you posted, and the date you confirmed the law. If anyone ever questions the program, that paper trail is your defense.

How to implement it cleanly

Done right, surcharging is unremarkable — customers see a clearly disclosed fee, choose how to pay, and move on. Done sloppily, it generates chargebacks, complaints, and exposure. The difference is process.

• Confirm eligibility first. Check current network rules and current state law for your locations before you build anything.
• Register and notify. Give the networks and your processor the required advance notice. Make sure your processor's surcharging product is actually enabled on your account.
• Configure card-type detection. Your terminal or gateway must reliably separate credit from debit and prepaid so the fee never touches an ineligible card.
• Cap to cost. Set the surcharge at or below your cost of acceptance, within the network maximum — never above it.
• Disclose everywhere. Signage at entry and point of sale, a notice at online checkout, and a separate line item on every receipt.
• Review on a schedule. Re-verify state law and network rules at least annually, and any time you expand into a new state.

None of this is exotic. It is the same discipline that separates a clean payments program from a messy one: know the rule, configure to it, disclose it, and keep a record.