Card surcharges: state rules and network rules collide

Two approvals, not one

Whether you can add a credit card surcharge turns on two separate approvals, not one, and both have to line up before you turn a program on. Your state's own law is the first gate, and it varies enough that there is no single national answer — some states prohibit surcharging outright, others allow it only with specific disclosure requirements, and the rule for a small clinical practice isn't always identical to the rule written for general retail.

Assuming your state follows whatever a colleague in another state does is the single most common way this goes wrong. The card network's own operating rules are the second gate, layered on top of whatever your state permits — and a program that clears your state's law can still violate your processor's agreement if you skip the network's separate registration and disclosure steps.

State law is the first gate, and it varies widely

Because state surcharge law varies this much and changes over time, the right first move is checking directly with your own state's attorney general's office or the state agency that regulates consumer payment practices, not relying on a general web search or a rule you half-remember from a different state.

A rule that was accurate for your state two years ago may not be current, and a rule that's accurate for a neighboring state may not apply to yours at all. Some states that once banned surcharging outright now permit it with conditions, following federal court rulings that treated flat bans as a restriction on how merchants communicate pricing — which is exactly why "check your own state, today" matters more than any summary a page like this one could give you. Treat any card-surcharge decision as one you confirm fresh, not one you carry forward from what used to be true.

The card network layer sits on top of the state layer

Even in a state that allows surcharging, your card network's own operating rules — Visa's, Mastercard's, and each other network's, accessed through your card processing agreement — impose their own separate conditions: registering the surcharge program before you start, disclosing it clearly at the point of sale and on the receipt, and capping how it can be applied. Clearing state law doesn't clear this second layer on its own.

Network rules also typically draw a hard line between credit and debit: surcharging a debit card is usually barred even in states that permit surcharging credit cards, and whether the same rule applies to hsa/fsa cards specifically is worth confirming too, since some networks treat them like standard debit for surcharge purposes. A single flat "we surcharge all cards" policy can violate network rules the moment a patient pays with the wrong card type, regardless of what your state allows for credit. Your payment processor's own compliance documentation is the authoritative source for your specific network requirements — read it before enabling anything, not after a patient or your processor flags it.

Surcharge, convenience fee, cash discount — not interchangeable

A surcharge, a convenience fee, and a cash-discount program are three different structures, not interchangeable labels for the same idea, and mislabeling one as another is a common source of noncompliance even when the underlying economics are similar. A surcharge is an add-on charged specifically for paying by credit card; a convenience fee typically applies to a specific non-standard payment channel, like an online portal or phone payment, and carries its own separate rules.

A cash-discount program instead prices every service at the card-inclusive rate and discounts patients who pay by cash or bank transfer, which some states treat differently from a true surcharge even when a patient ends up paying the identical amount either way. Naming your program correctly on your financial policy, your posted pricing, and your processor's registration matters on its own — a program built as a cash discount but described to patients as a "surcharge," or the reverse, can fail on the labeling alone even if the underlying structure would otherwise have been permitted.

Where the No Surprises Act still reaches this

If you plan to surcharge a self-pay or uninsured patient's card payment, that added amount is part of what the patient will actually owe — and the good-faith estimate you're already required to give that patient before a scheduled service has to reflect it 1Ref 1Centers for Medicare & Medicaid Services (2026).No Surprise Billing.That the No Surprises Act requires a good-faith estimate of expected charges for self-pay/uninsured patients and creates the patient-provider dispute process an unreflected surcharge can trigger2Ref 2Office of the Federal Register (2026).45 CFR Part 149 — Surprise Billing and Transparency Requirements.The operative regulation text for what a good-faith estimate must contain and the dispute process that follows an underestimate. A surcharge added after the estimate went out, without the estimate being updated to match, is exactly the kind of gap the patient-provider dispute resolution process exists to catch 1Ref 1Centers for Medicare & Medicaid Services (2026).No Surprise Billing.That the No Surprises Act requires a good-faith estimate of expected charges for self-pay/uninsured patients and creates the patient-provider dispute process an unreflected surcharge can trigger2Ref 2Office of the Federal Register (2026).45 CFR Part 149 — Surprise Billing and Transparency Requirements.The operative regulation text for what a good-faith estimate must contain and the dispute process that follows an underestimate.

Building your surcharge into the estimate template itself, rather than adding it at checkout as a separate line the patient hasn't seen coming, keeps the two documents consistent and removes the most common way a technically legal surcharge still generates a complaint.

Medicare and Medicaid patients: caution before you apply it there

Practices that accept Medicare or Medicaid assignment generally treat those patients as outside any card-surcharge program. The enrollment agreement's language about accepting the assigned amount as payment in full is commonly read to bar an add-on fee tied to how the patient pays, even a small one — confirm this reading against your own enrollment agreement and your payer contracts before applying a surcharge broadly rather than assuming it clears the same way a self-pay charge would.

The safer default many solo practices land on is excluding Medicare, Medicaid, and any in-network payer's assigned patients from the surcharge program entirely, and applying it only to genuinely self-pay balances where no assignment or network agreement is in play. An unregistered or improperly disclosed surcharge is also a common trigger for chargebacks, separate from whatever your state's law ultimately says about it — a patient who disputes the amount with their bank doesn't wait for a regulator to weigh in first. A surcharge program is also a different mechanism from deposits and pre-payment policies you might already run; the two can coexist, but each carries its own separate rules and disclosure requirements.

The four-step check before you turn it on

Before you turn a surcharge program on, run four checks in this order, and don't skip ahead based on what you found for a different state, a different processor, or a different point in time — surcharge rules are exactly the kind of thing that changes without much notice.

• Confirm your state's current rule directly with your state attorney general's office or its consumer-payment regulator — not a summary page, since this is exactly the kind of rule that changes.
• Confirm your card processor's specific program requirements — registration, point-of-sale disclosure, receipt language — from their own compliance documentation.
• Exclude debit cards and any Medicare, Medicaid, or in-network assigned patient from the program unless you've separately confirmed otherwise.
• Update your self-pay good-faith estimates and financial policy to reflect the surcharge before you turn it on, not after the first patient asks why the total changed.

A surcharge program built in this order survives scrutiny from a patient, a processor audit, and a state regulator at the same time; one built backward tends to survive none of them.