Glossary · Pricing & fees

What is
Surcharge program?

Complexity Basic
Shows up Monthly
Scope Optional
Operator relevance Important
Share definition X LinkedIn Reddit HN Email
Quick definition

A surcharge program adds an explicit fee to credit card transactions at checkout to recoup processing costs. Allowed on credit cards (not debit) in most U.S. states, capped at 3% by Visa and 4% by Mastercard, and requires 30-day network notification and receipt disclosure.

The short answer

A surcharge program is the practice of adding a disclosed fee to credit-card transactions to offset the merchant's processing cost. It became broadly legal in the U.S. after Visa and Mastercard's 2013 class-action settlements, but remains heavily regulated: capped percentages, state-level bans, network-notification requirements, debit-card prohibition, and strict disclosure at every step. Compared to cash discounting and dual pricing, surcharging has the most compliance surface area — and the most opportunities to get it wrong.

The rules at a glance

  • Cap: 3% or your actual cost of acceptance, whichever is lower, on Visa. Mastercard caps at 4%. Amex matches the Visa/MC rate at your discretion.
  • Credit only: Never on debit cards — this is a hard federal and network rule. Regulated debit under Durbin simply cannot be surcharged.
  • 30-day notification: Merchants must notify Visa and Mastercard 30 days before starting to surcharge. Online forms on each network's website.
  • Signage: At the point of entry to the store AND at the point of sale.
  • Receipts: Must show surcharge as a separate line item, not rolled into price.
  • Uniform rate: Same surcharge percentage across all card brands you surcharge on — you can't surcharge Discover more than Visa to punish them.

States where surcharging is restricted or banned

  • Connecticut, Massachusetts, Maine: Outright prohibition of credit-card surcharges.
  • New York: Allowed but with specific disclosure-language requirements (Expressions Hair Design v. Schneiderman 2017 and follow-ups).
  • Colorado, Kansas: Previously banned, now allowed post-court-decisions but with caps (Colorado caps at 2%).

Rules shift — always verify state-specific rules before enabling surcharging in any new jurisdiction.

What operators need to know

  • Debit-card hard stop. Processing a surcharge on a debit transaction — even accidentally — is a violation. Your gateway must be configured to detect debit BINs (via BIN lookup) and waive the surcharge automatically.
  • Signage gets audited. Processor risk teams drive past / visit surcharging merchants. Missing entry signage is the #1 audit failure.
  • E-commerce is easier to operate compliantly than card-present — disclosure can be rendered on every page, and BIN-detection prevents debit surcharging. Conversion hit is real (10-20%), though.
  • 3% feels small, 4% feels adversarial. Consumer perception tips negative around 3.5-4%. Price the surcharge at your actual cost, not "up to the cap."
  • Multi-brand, multi-state operators need jurisdiction-aware surcharging — surcharge a Connecticut customer and you've violated state law. Routing should inspect billing state and waive the surcharge dynamically.

Keep learning

Go deeper on
Surcharge program.

Related glossary terms

Processing across
multiple brands?

multiflow consolidates your ledger, keeps per-brand billing descriptors, and fans out payouts to the right legal entity.

The Operator Briefing

Twice-monthly. No fluff.

Processor shutdowns, reserve-hold playbooks, reconciliation lessons, and the merchant-account decisions that save operators six-figure years. Delivered to your inbox — never spam.

No spam. Unsubscribe in one click.

We use essential cookies · Privacy