Surcharging credit card transactions is legal for most U.S. merchants in 2026, but three constraints determine whether your program holds up: state law, the network cap tied to your actual cost of acceptance, and a hard ban on surcharging debit or prepaid cards.
A handful of states still prohibit or tightly restrict surcharges outright, and even where it's allowed, Visa and Mastercard cap the rate at whichever is lower: the network ceiling or what you actually pay to accept that card brand. Charge more than your documented cost, and you're exposed even if you're under the network's headline percentage.
Before you touch your point-of-sale settings, confirm four things:
- The law in every state where your transactions occur, including the cardholder's billing state for ecommerce
- Your processor's per-brand cost-of-acceptance figures, not a blended industry average
- Whether your terminal or gateway can reliably tell a credit card from a debit or prepaid card
- Your acquirer's notice requirements, since most networks expect advance registration before you flip the switch
Quick fact: Visa's commonly cited surcharge ceiling sits at 3%, while Mastercard allows up to 4%, but neither cap matters if it exceeds your real processing cost for that card. That "whichever is lower" test is the rule most merchants get wrong, and it's the one enforcement teams check first.
Key Takeaways
Compliant surcharging in 2026 requires matching your rate to documented per-brand acceptance cost, never exceeding the network cap, and never applying it to debit or prepaid cards.
| Point | Details |
|---|---|
| Check state law first | Confirm legality based on where the transaction occurs, including the cardholder's billing state for online sales. |
| Apply the lower-of test | Set your surcharge at whichever is smaller: the network cap or your documented cost of acceptance for that brand. |
| Never surcharge debit or prepaid | This is a bright-line rule enforced through POS card-type detection, with no exceptions. |
| Document and notify properly | Notify your acquirer in advance, post signage at entry and checkout, and itemize the fee on every receipt. |
| Use PaySec for cost accuracy | Network Offset Pricing and real-time reporting give merchants the brand-level cost data compliant surcharging depends on. |
Table of Contents
- What You Need to Check Before Adding a Surcharge
- How Do Card Network Surcharge Rules Actually Work?
- Which States Allow Credit Card Surcharges in 2026?
- Surcharging vs. Cash Discounts vs. Convenience Fees
- Step-by-Step: Setting Up a Compliant Surcharge Program
- Avoiding the Most Common Enforcement Traps
- How PaySec Supports Compliant, Cost-Accurate Surcharging
- Sources
- FAQ
What You Need to Check Before Adding a Surcharge
A surcharge program built on guesswork is a liability waiting to surface; before you configure anything, work through this sequence.
- Confirm legality where the transaction happens. For in-person sales, that's the state where your terminal sits. For ecommerce, it's typically the cardholder's billing address, not your business location, so a Texas-based online store selling into Massachusetts needs to know Massachusetts rules too.
- Test your point-of-sale system's card-type detection. Terminals read the first six digits (the issuer identification number) to classify a card as credit, debit, or prepaid. If your system can't distinguish reliably, you risk surcharging a debit transaction by accident, which is a violation regardless of intent.
- Request itemized cost-of-acceptance data from your processor. Ask for numbers broken out by card brand and, where possible, by product category. A blended "average cost" figure won't hold up if a network or acquirer asks you to justify a specific surcharge percentage.
- Decide between brand-level and product-level surcharging. Brand-level pricing is simpler to administer but assumes uniform cost across your catalog. Product-level pricing, made more viable by 2026 interchange settlement developments, better matches cost to charge but demands more granular reporting and reconciliation.
Skipping any one of these steps is how well-intentioned merchants end up with a surcharge program that looks compliant on paper and fails the moment a network audits it.
How Do Card Network Surcharge Rules Actually Work?
Visa and Mastercard both publish headline caps, but the cap is only half the rule. Neither network lets you charge that full amount if your actual cost of accepting that card is lower. The surcharge must equal whichever figure is smaller: the network cap or your documented acceptance cost for that specific brand.
That distinction is where most merchants get tripped up. Networks expect the surcharge to track cost, not to function as a flat revenue add-on.
Registration and notice. Most acquirers require merchants to notify them, and in some cases the card networks, before turning on surcharging, typically 30 days in advance. Equal-treatment rules also apply: if you surcharge Visa, you generally must surcharge Mastercard at a comparable rate for the same transaction type. You can't cherry-pick one network to surcharge while leaving another untouched.
Debit and prepaid are off-limits. This is a bright-line rule with no gray area. Terminals identify card type through the issuer identification number embedded in the card data, and a compliant POS setup should flag and block surcharge application on any card coded as debit or prepaid before the transaction completes.
Enforcement typically comes through the acquiring bank rather than a knock from the network directly. Common triggers include:
- Surcharging debit or prepaid cards due to misconfigured POS settings
- Failing to register or notify the acquirer before going live
- Missing or incomplete signage and receipt itemization
- Charging a rate that exceeds documented cost of acceptance for that brand
Penalties range from fines levied against the acquirer (often passed to the merchant) to a network requiring the surcharge program be shut down until corrected. Implementation failures like these are the most frequently cited cause of merchant enforcement action, more so than the surcharge amount itself.
Which States Allow Credit Card Surcharges in 2026?
Surcharge legality is a patchwork and changes with enough frequency that relying on outdated blog posts is a real risk. The table below reflects the general posture of commonly referenced states; always confirm current status against your state's statute before rollout.
| State | Surcharging Status | Notable Restrictions |
|---|---|---|
| California | Allowed with conditions | SB 478 requires advertised total prices, which effectively restricts surcharging unless the fee is embedded in the posted price |
| Connecticut | Restricted | Historically among the strictest states; surcharge disclosure and notice rules are tightly enforced |
| Massachusetts | Prohibited | One of the states with a direct statutory ban on credit card surcharges |
| Colorado | Allowed, capped | State statute caps the surcharge at 2%, below the network ceiling |
| Texas | Allowed | Surcharging permitted under state law, subject to standard network rules |
| Kansas | Prohibited | State law bars surcharging outright |
| Maine | Prohibited | State law bars surcharging outright |
For multi-state and ecommerce merchants, apply the law of the state where the transaction occurs, which for online sales generally means the cardholder's billing address rather than your headquarters or fulfillment location. A single online store selling nationwide may need separate surcharge logic by customer state, not one blanket policy.
The NCSL's state-by-state surcharge statute summary is the most reliable ongoing reference, since state legislatures revisit these laws more often than most merchants expect. Treat any state law table, including this one, as a starting point for verification rather than a final answer.
Surcharging vs. Cash Discounts vs. Convenience Fees
These three pricing models solve similar problems but carry different legal footing, and confusing them is one of the fastest ways to end up noncompliant without realizing it.
A surcharge adds a fee specifically for using a credit card, calculated as a percentage of the transaction and disclosed at checkout. A cash discount, sometimes called dual pricing, works in reverse: you post a higher "regular" price and a lower cash price, framing the card price as the standard and cash as the discount. A convenience fee applies only in specific remote or non-standard payment channels, such as phone or online bill pay where card acceptance isn't the merchant's default channel, and it applies regardless of payment type, not just to cards.
- Use dual pricing where your state restricts or bans surcharging outright, since cash discount programs are generally permitted even in surcharge-restricted states as long as both prices are fully and clearly advertised.
- Use a convenience fee only for genuinely non-standard payment channels, not as a rebrand of a surcharge on your normal checkout flow.
- Use a true surcharge where your state allows it and you can document cost of acceptance per brand.
Pro Tip: A cash discount program only holds up legally if both prices are advertised with equal visibility. Quietly marking up the "card price" while calling it standard, with the cash price hidden in fine print, is functionally a surcharge wearing a different label, and regulators read it that way.
Step-by-Step: Setting Up a Compliant Surcharge Program
Building this right the first time saves you from unwinding a broken program later.
- Pull per-brand cost data from your processor. Request a breakdown by card brand, and by product category if you plan to surcharge at that level. Blended averages won't satisfy the "whichever is lower" test.
- Calculate your compliant surcharge percentage. Compare your documented cost against the network cap for each brand, and set your rate at the lower of the two. Save the calculation in writing.
- Notify your acquirer. Most acquirers want written notice, commonly 30 days before your go-live date, and some networks require separate registration.
- Post signage at your entrance and point of sale. NFIB's guidance is specific here: customers need advance notice before they reach checkout, not just a line item after the fact.
- Itemize the surcharge on every receipt. The fee needs its own line, clearly labeled, separate from the base transaction amount.
- Test before you go live. Confirm POS card-type detection blocks debit and prepaid cards, verify receipt formatting prints correctly, and check that your online checkout displays the surcharge before payment confirmation.
Ongoing monitoring matters as much as setup. Schedule a recurring internal audit, monthly is reasonable for most merchants, to reconcile surcharge revenue against documented acceptance cost per brand. If your processor's fee structure shifts, your surcharge rate needs to move with it, not sit static for a year.
Avoiding the Most Common Enforcement Traps
Most surcharge violations aren't willful. They're the result of a program that was compliant on day one and drifted out of alignment as costs or circumstances changed.
- Recalculate whenever your processor changes rates. A surcharge set correctly six months ago can become noncompliant the moment your negotiated rate shifts, even without you changing anything on your end.
- Keep a paper trail. Retain your acquirer notice, network registration confirmation, and every cost-of-acceptance calculation. If a network or acquirer ever questions your program, documentation is your defense.
- Train front-line staff. Employees should be able to explain the surcharge in plain terms and know how a customer can pay by another method if they object.
- Respond quickly to inquiries. If your acquirer flags an issue, treat it as a compliance event, not a billing dispute. Delayed responses tend to escalate penalties.
- Loop in counsel for edge cases. Multi-state operations, high transaction volume, or any prior enforcement history are good reasons to get legal review before scaling a surcharge program further.
Pro Tip: Run a simple monthly check: total surcharge revenue collected per card brand against total documented acceptance cost for that brand. If revenue is running ahead of cost, adjust the rate immediately and keep a dated record showing you caught and corrected it. That single habit is the difference between a minor compliance note and a real penalty.
How PaySec Supports Compliant, Cost-Accurate Surcharging
Getting the "whichever is lower" calculation right depends on having real numbers, not estimates. Paysec's Network Offset Pricing gives merchants a clear, brand-level view of acceptance cost, which is exactly the input the compliance test requires.
- Detailed, per-brand transaction reporting that documents cost of acceptance for the "whichever is lower" comparison
- Transaction-level traceability that supports audit response if an acquirer or network raises a question
- Guidance on receipt line-item formatting and checkout signage placement to match disclosure requirements
- No long-term contracts or hidden fees, so the cost figures merchants use for their surcharge math stay stable and transparent
Merchants across 18-plus industries using PaySec's approach report measurable processing cost reductions, in some cases cutting effective costs by roughly 30 to 60%, which directly changes what a compliant surcharge percentage even needs to be.
A Note From the PaySec Marketing Team
Merchants tend to treat surcharge compliance as a one-time setup task. It isn't. Cost of acceptance shifts, state laws get amended, and a rate that was correct in January can be wrong by summer. The businesses that stay out of trouble are the ones that keep records, recalculate on a schedule, and treat transparency with customers as protection rather than a formality.
If you're unsure whether your current program still lines up with your actual acceptance cost, that's worth checking now rather than after an acquirer flags it.
— PaySec Marketing Team
Get Your Surcharge Numbers Right With PaySec
Most merchants trying to build a compliant surcharge program run into the same wall: their processor gives them a blended rate instead of the brand-level cost breakdown the "whichever is lower" test actually requires. Paysec closes that gap directly. Network Offset Pricing gives you documented, per-brand acceptance costs and real-time reporting, so your surcharge calculation is based on your actual numbers instead of a guess, with no long-term contract locking you into the wrong rate if your costs change.
If your point-of-sale setup also needs to reliably separate credit from debit and prepaid before you can safely surcharge, Paysec's mobile payment processing and real-time reporting dashboards give you both the transaction accuracy and the documentation trail in one place. Request a cost breakdown from Paysec to see exactly what your current acceptance costs look like by brand before you set your next surcharge rate.
Sources
- Credit card surcharging guide — NFIB Legal Center (PDF)
- Card network surcharge rules: caps, disclosures, and penalties — LegalClarity
- What Is a Convenience Fee? — Discover
FAQ
Is it legal to charge a 3% credit card fee?
It depends on your state and your documented cost of acceptance.
What states ban credit card surcharges?
Massachusetts, Kansas, and Maine are commonly cited examples of states with statutory bans, while others like Connecticut and California impose significant restrictions. Check the NCSL state summary before implementing, since state laws change.
Is it legal to charge 4% on a debit card?
No. Surcharges apply only to credit card transactions under network rules; debit and prepaid cards cannot be surcharged under any circumstance, regardless of the percentage.