Credit Card Surcharges and Cash Discounts — A POS Compliance Guide

A 2.5% surcharge on a $40 ticket is a dollar. A dollar for the merchant looks like a coffee. A dollar for a Massachusetts attorney general's office looks like a $1,000 fine for a banned-state surcharge that was never legal in the first place.

This is the awkward gap most US operators live in. Surcharging credit cards is legal in most states. It's prohibited in at least four. Card-network rules cap it at 3% (Visa) or 4% (Mastercard). Disclosure has to be clear and conspicuous at the entrance and at the point of sale, before the card is presented. Debit and prepaid cards can't be surcharged at all. And the rules change — Kansas legalized surcharging on January 1, 2025; California's prohibition took effect July 1, 2024.

The system that knows whether a transaction can legally have a surcharge added to it is the POS. So this is mostly a software problem. Credit card surcharge POS capability — meaning the POS itself enforces state and network rules at the moment of sale — is the missing piece for most US merchants. This guide walks through what compliance actually requires, and what changes when the engine is built into the POS instead of bolted on through a payment processor's "surcharge program."

The Two Models, and Why the Distinction Matters

There are two ways to recover credit card processing costs from a customer. They look similar on the receipt and they're often confused, but legally they're different things.

Surcharge. The merchant adds a fee on top of the listed price specifically when the customer pays with a credit card. The base price stays the same; the surcharge is itemized. Federal law allows this; state laws and card-network rules constrain how, where, and at what rate.

Cash discount. The listed price already includes the credit card cost. Customers paying with cash (or sometimes debit) receive a discount off that listed price. Mechanically the customer pays the same amount as in a surcharge model. Legally it's treated very differently — cash discounts are broadly permitted even in states that ban surcharges.

For most operators in the four states that prohibit surcharging — Massachusetts, California, Connecticut, and Maine — cash discount is the only compliant path. The point a POS has to enforce: don't try to charge the surcharge in a banned state, and don't accidentally call your cash-discount program a surcharge on the receipt, because that's the part that gets reclassified by an auditor.

POSAIC's fee domain handles both modes as separate configurations. Each outlet has a fee policy with a US state code attached. The compliance engine evaluates whether a surcharge rule can legally apply for that outlet at the moment the order rings up. If not, the rule is refused and the operator is shown why — no silent charges, no defensive position later.

State-by-State, in Brief

A condensed version of the 2026 landscape — verify against your state's specific guidance before turning anything on:

On top of the state layer, both Visa and Mastercard apply their own rules to every surcharge transaction nationwide:

• Caps: 3% for Visa, 4% for Mastercard. Whichever is lower binds you.
• Registration: Merchants must register a surcharge program with the card networks before turning it on.
• Disclosure: Required at the store entrance and at the point of sale — and per recent guidance, embedding the disclosure inside a menu or a POS screen alone is not acceptable.
• Card type: Surcharges apply only to credit. Debit and prepaid cards cannot be surcharged regardless of how the customer chooses to run them.

A POS that doesn't know the customer's card type at the moment of sale can't enforce that last rule. Most don't even try.

What Compliance Looks Like at the POS Layer

Walk through what actually has to happen when a customer hands over a credit card in a state that allows surcharging:

• Identify the card type. Credit, debit, prepaid. Surcharge applies to credit only.
• Look up the active fee policy for the outlet. State code, configured surcharge percentage, network caps.
• Verify against the network cap. A merchant configured at 3.5% for Mastercard is fine; 3.5% for Visa is over the cap and must be capped down to 3.0% or refused.
• Verify against state law. A surcharge configured at 3% in Colorado is non-compliant — Colorado caps it at 2%. POSAIC's compliance check returns a banned-or-capped result with a specific reason, not a generic refusal.
• Itemize the surcharge as its own line. Receipt clearly shows "Credit card surcharge: $1.20" — not buried in tax, not folded into subtotal.
• Record the surcharge as an event. When the labor board or the IRS asks how a $1.20 fee was calculated for a March 14 transaction, the answer comes from the event-sourced ledger, not from a current-state report that might have been edited since.

POSAIC's fee domain returns all this in a single real-time calculation call, given outlet ID, subtotal, and payment method. A 22% auto-grat is 2200 bps; a 3% surcharge is 300 bps. The basis-point precision matters when you're multiplying by thousands of transactions a year — rounding to the nearest cent on each transaction can drift a quarter-percent over a quarter without anyone noticing.

Why Most POS Systems Punt on This

There's a structural reason no major cloud POS owns this end-to-end: surcharging is usually packaged with the payment processor, not the POS. Stax, Dual Pricing, and similar processors sell "compliance programs" as a paid add-on bundled with their processing services. The pitch is convenient: "we'll handle disclosure language, the registration with Visa and Mastercard, and the percentage." The catch is that you're paying again for compliance enforcement that should belong to the POS, and you're tied to a specific processor.

For a free POS like POSAIC, the calculus is different. The compliance engine is in the box because the POS is the right place for it — it's the system that knows the card type, the state, the subtotal, and has the audit trail. Adding a built-in fee engine costs nothing per merchant per month because there's no per-merchant infrastructure. Either the rules and state list are correct in the binary, or they're not — and they get updated when state laws change, the same way the rest of the application gets updated.

A side-by-side, with no marketing weight on the scale:

The Disclosure Problem (and Why It's Not Just a POS Problem)

Compliance has two halves. The POS handles the math and the rule-enforcement at the moment of sale. The operator still has to handle disclosure — physical signage at the entrance, a specific notice at the register, often a separate notice on the receipt.

POSAIC can print the surcharge line on every receipt with the configured display label ("Credit Card Surcharge — 3%"). It cannot put a sign on the front door of the restaurant. Operators in actively enforced jurisdictions — California (until the recent ban), Mass, parts of New York — have been fined for situations where the math was right but the signage was missing or unclear.

The practical sequence: turn on the fee policy in the POS after you have the entrance signage printed and posted, after you've registered the program with Visa and Mastercard, and after you've confirmed your state's specific disclosure rules with a merchant-services advisor or legal counsel. The POS is necessary, not sufficient.

Cash Discount as the Default in Banned States

For Massachusetts, California, Connecticut, and Maine — where surcharging is illegal — cash discount is usually the right structure. Mechanically:

• Reprice the menu to include credit-card processing cost in the listed price.
• Configure POSAIC's fee engine in cash-discount mode for that outlet.
• Cash, check, and (where eligible) debit transactions automatically deduct the discount at checkout.
• Receipt shows the discount as a line item — not as a "surcharge avoided."

The state-aware enforcement matters here too: if the operator accidentally configures a surcharge rule in a banned state, the engine refuses to apply it and surfaces a compliance error instead of silently charging the customer. The Massachusetts AG isn't going to be impressed by "the integration was misconfigured." A POS that fails closed instead of failing open is the structural fix.

When You Don't Need This

Honest section:

• A merchant in a state without surcharge restrictions, with one fixed processing rate from a single processor, can run a surcharge through the processor's own program and skip POS-level enforcement. The compliance burden is lower than it looks if your geography and rates are simple.
• A small operator who isn't planning to surcharge or run a cash-discount program at all doesn't need any of this — list the cash-inclusive price and accept the cost.
• A merchant deeply embedded in a payment processor's surcharge program with full disclosure handled may not see enough marginal benefit from POS-level enforcement to justify the migration.

The case for a POS-native fee engine is strongest when you operate in multiple states, when you switch processors periodically, when you need an audit trail for a state-level inquiry, or when you've ever been surprised by a chargeback that originated in a fee dispute.

Closing Out

Three things worth keeping:

• Surcharging and cash discounts are POS-layer concerns, not just processor concerns. The system that knows the card type and the state is the right place for the rule.
• State law is the ceiling; network rules are the next ceiling. Whichever is lower binds — and a compliant POS enforces both.
• The audit trail is the real product. The math is easy; defending the math two years later, after the rule changed twice and the rate was edited three times, is what compliance actually means.

POSAIC's fee domain ships with the banned-state list, network caps, and cash-discount mode in the box. Pricing doesn't change with the number of fee rules or the number of outlets. If you're running surcharges through a processor's bolt-on program, downloading POSAIC and running a side-by-side calculation against your last month of transactions will show you whether the math has been clean or whether it's drifted — without any switching commitment.

Sources:

• NFIB Credit Card Surcharge and Cash Discount Laws Guide 2025 (PDF)
• Merchant Cost Consulting — Credit Card Surcharge Laws by State
• Stax — State-by-State Credit Card Surcharge Guidance