What Is Surcharging
Definition
Surcharging is the practice of adding a fee to a transaction when a customer pays with a credit card, passing some or all of the card processing cost to the cardholder. The surcharge is disclosed at the point of sale and appears as a separate line item on the receipt.
How It Works
The merchant sets a surcharge percentage (capped at 3% by Visa and Mastercard, or the merchant's actual cost of acceptance, whichever is lower). When a customer chooses to pay by credit card, the surcharge is added to the total. Debit card transactions cannot be surcharged under the Durbin Amendment. The merchant must notify their acquirer, card networks, and post signage at the store entrance, point of sale, and on receipts.
Why ISVs Care
ISVs building POS, checkout, or invoicing software need surcharging capabilities to serve merchants in industries where processing costs are a major concern. Offering compliant surcharging as a built-in feature increases software value and can drive payment processing adoption. ISVs must ensure their implementation handles state-by-state legality, debit card exclusions, and disclosure requirements correctly.
Surcharging lets merchants add a fee to credit card transactions, passing the cost of card processing directly to the customer who chooses to pay with a card.
How Surcharging Works
When a merchant surcharges, the customer sees the base price plus a separate line item for the credit card fee. For example, a $100 purchase with a 3% surcharge totals $103 on the receipt.
The Rules
Card networks impose strict requirements:
- Cap: The surcharge cannot exceed 3% (Visa/Mastercard) or the merchant’s actual cost of acceptance, whichever is lower
- Disclosure: Merchants must post signage at the entrance, at the point of sale, and include the surcharge as a separate line item on the receipt
- Credit only: Surcharges can only be applied to credit card transactions — debit cards (including debit cards run as credit) are excluded under the Durbin Amendment
- Notification: Merchants must notify their acquiring bank and card networks at least 30 days before starting a surcharging program
- State compliance: Several US states ban or restrict surcharging (as of 2024, Connecticut, Massachusetts, and Puerto Rico have active bans)
Surcharging vs. Cash Discount vs. Dual Pricing
| Feature | Surcharging | Cash Discount | Dual Pricing |
|---|---|---|---|
| Listed price | Base price (no fee included) | Includes non-cash adjustment | Two prices shown |
| Fee visibility | Added at checkout | Discount at checkout | Upfront on all signage |
| Debit cards | Cannot be surcharged | Discount applies to all cash/debit | Lower price for cash/debit |
| State bans | Yes (CT, MA, PR) | No state bans | No state bans |
| Customer perception | Negative (feels like a penalty) | Neutral to positive (feels like a reward) | Neutral (transparent) |
Why ISVs Need Surcharging Capabilities
Merchant Demand
Merchants lose 2-4% of every card transaction to processing fees. For businesses with thin margins — restaurants, gas stations, professional services, medical practices — surcharging is one of the most effective ways to recover these costs.
ISVs that build compliant surcharging into their POS or invoicing software make their platform more valuable to cost-conscious merchants.
Implementation Complexity
Surcharging isn’t as simple as adding a percentage. ISVs must build logic for:
- BIN identification: Distinguishing credit from debit cards in real-time to avoid surcharging debit (which is illegal)
- State detection: Blocking surcharges for transactions in states where it’s banned
- Rate capping: Ensuring the surcharge never exceeds 3% or the merchant’s actual cost
- Receipt formatting: Displaying the surcharge as a separate, clearly labeled line item
- Notification workflows: Helping merchants notify their acquirer and card networks
Compliance Risk
Incorrect surcharging implementation exposes merchants (and potentially the ISV) to:
- Card network fines ($1,000-$25,000 per violation for Visa)
- State attorney general enforcement actions
- Class action lawsuits (surcharging litigation has generated hundreds of millions in settlements)
This compliance complexity is actually an opportunity for ISVs. Merchants need software that handles surcharging correctly — and they’ll pay for it.
Surcharging Economics for ISVs
When an ISV’s merchant surcharges, the merchant’s effective processing cost drops to near zero. This creates interesting dynamics:
- Higher merchant satisfaction: Merchants keep more revenue, reducing churn from “processing costs are too high” complaints
- Processing volume growth: Merchants are more willing to accept cards when they’re not absorbing the cost
- ISV revenue preservation: The ISV still earns its revenue share on every transaction — the surcharge covers the merchant’s portion, not the ISV’s
For ISVs evaluating whether to build surcharging support, the ROI is clear: it’s a feature that directly reduces merchant objections to embedded payment processing.