Is a Credit Card Surcharge Legal in Your State?

Whether a credit card surcharge is legal depends entirely on the state a business operates in, and getting it wrong can mean real liability, so the right first step is checking your specific state’s current law before enabling one, not assuming a surcharge is universally allowed or universally banned. PocketSuite powers 7,000+ service businesses, including 1,000+ pet service businesses, whose clients have collectively processed nearly $1 billion in income and scheduled over 9.2 million appointments. PocketSuite’s Surcharge feature makes the technical side of collecting a surcharge straightforward, but confirming the underlying legal question for your specific state is a step every business has to take on its own before turning it on.

Processing fees are a real cost of accepting card payments, and passing some or all of that cost to the client through a surcharge is a common way businesses try to protect their margin instead of quietly absorbing it on every transaction. The complication is that surcharge law isn’t uniform across the country, some states restrict or ban surcharging outright, others allow it with specific disclosure requirements, and the rules change often enough that a policy that was compliant two years ago isn’t automatically still compliant today.

Surcharge Is a Real, Built-In Feature, With a Compliance Checkpoint Attached

Surcharge lets a business pass along the processing fee to the client as a convenience fee for accepting credit cards, leaving the business responsible only for the flat per-transaction bank fee rather than the full card processing percentage. Turning it on is a setting inside the account; confirming it’s legal to use in your specific state is a separate step, and one worth doing before flipping that setting rather than after.

This genuinely isn’t a settled, uniform national rule, it’s closer to sales tax in that the correct answer depends on where the business is located and where the transaction occurs. A business operating in more than one state has to check the rule for each location separately rather than assuming what’s allowed in one state applies everywhere it operates. A state’s own department of revenue or attorney general’s office, or a payments attorney familiar with card-brand rules in that state, is the right place to confirm the current answer.

A Client’s Own Words on Getting Payment Structure Right

Noelle Blessey, owner of Thank Dog! Training, switched her dog training and behavior modification business onto PocketSuite and specifically praised how much simpler payment handling became after moving off a patchwork of separate tools. “It’s just much easier to use than the other, the old software was very behind what their desktop did,” she said, describing the improvement in her day-to-day payment operations broadly, a relevant comparison for any business trying to get its payment policies, surcharge included, set up correctly the first time rather than fixing them after the fact.

What to Do in a State Where Surcharging Isn’t an Option

For a business operating in a state where surcharging is restricted or banned, the processing fee doesn’t disappear, it still has to be accounted for somewhere, typically by building it into the base price rather than itemizing it separately on the invoice. POS & Payments still supports standard processing without a surcharge attached, and a business can adjust its base pricing to reflect the true cost of accepting cards, which keeps the client-facing transaction simple and compliant while still protecting the business’s actual margin.

Some businesses in restricted states choose to offer a small discount for cash or bank transfer instead, which is legally distinct from a card surcharge in most jurisdictions, effectively achieving a similar margin protection from the opposite direction. Either approach requires the same first step: confirming the actual rule for the specific state before building a pricing policy around it.

This Is a Legal Question First, a Software Question Second

This article is background, not legal advice for any specific business’s situation. Surcharge law can vary by more than just state, some jurisdictions have county or city-level rules layered on top, and a business with any doubt about its specific situation is better served checking with a payments attorney or its processor’s compliance team than relying solely on a general summary, however well-sourced.

What software can reliably do is make compliance easier once the legal answer is settled: turning surcharge on or off, setting the exact percentage allowed, and keeping the client-facing disclosure clear and consistent across every transaction. Getting the legal answer right is the business’s responsibility; PocketSuite’s role is making the technical implementation straightforward once that answer is known.

Disclosure Matters as Much as Legality

Even in a state where surcharging is fully permitted, most rules also require clear disclosure to the client before the charge is applied, a sign at the point of sale, a line item on the invoice, or both, rather than a surprise fee discovered only after the fact. A surcharge that’s technically legal but poorly disclosed can still generate client complaints and, in some states, still violate the letter of the law if disclosure requirements aren’t met alongside the rate cap itself.

Building that disclosure into the checkout flow itself, rather than relying on a hand-written sign near the register, is part of what makes a surcharge policy durable as staff change and locations multiply. A client who sees the fee clearly itemized on their invoice, described plainly as a card processing fee, is far less likely to dispute it than a client who discovers it buried in a total they didn’t expect.

A business operating in more than one state should also expect to run two different policies simultaneously rather than picking one rule for the whole company, surcharging at a compliant location and absorbing the fee into pricing at a restricted one. That inconsistency between locations can feel awkward internally, but it’s the accurate reflection of genuinely different legal environments, and it’s better handled explicitly than by defaulting to whichever rule is simplest to administer regardless of where a given location actually falls.

Revisit the Rule Periodically, Not Just Once

Surcharge law isn’t static; state legislatures periodically revisit these rules, sometimes tightening disclosure requirements, sometimes changing the allowed rate cap, sometimes lifting or introducing a restriction altogether. A business that checks its state’s rule once, sets up surcharge accordingly, and never revisits the question risks operating under an outdated assumption years later. Building a periodic check into an annual business review, alongside other compliance items like insurance or licensing renewals, keeps the policy current rather than frozen at whatever was true the day it was first set up.

A business weighing whether surcharging is worth the complexity at all can also consider Buy Now Pay Later as an alternative or complementary lever on the payments side: rather than passing along a processing fee, offering an installment option on higher-ticket services addresses a different friction point, cost as a barrier to booking at all, rather than cost as a margin question on every transaction. The two aren’t mutually exclusive, but they solve different problems and are worth evaluating separately rather than treating payments strategy as a single decision.

Whatever a business ultimately decides, documenting the decision internally, which states allow surcharging, at what rate, with what disclosure, and which locations are excluded, protects against the kind of drift that happens when the original research lives only in one person’s memory. A written policy that a new manager or a new location can follow accurately is worth the modest time it takes to put together.