Convenience fee vs. surcharge vs. service fee: three different rulebooks

Why do these three fees keep getting confused?

A diner who sees "3% card fee" on a restaurant bill, a parent who pays a 2.5% fee to settle a tuition balance by phone, and a renter who's charged a flat $3.95 for paying rent online are all looking at a line item that functions as "more money because you used a card." The receipts look interchangeable. The rules behind them are not. Visa and Mastercard operating rules — and, in the background, FTC and state guidance on deceptive fee disclosure — treat a surcharge, a convenience fee, and a service fee as three structurally distinct categories, each with its own conditions for when it's allowed, how it has to be disclosed, and what happens when a merchant gets it wrong.

The confusion isn't accidental. Surcharging rules tightened materially after the 2013 Visa/Mastercard interchange litigation settlement, and most of the public conversation since has focused on surcharge caps and bans. That's left convenience fees and service fees — both older, narrower, and in some ways less restricted — poorly understood by merchants who assume any card-acceptance fee falls under the same surcharge umbrella. It doesn't, and the differences matter enough to build a compliance program around.

What exactly is a surcharge, and what rules actually govern it?

A surcharge is a fee added specifically because the customer chose to pay by credit card, calculated as a percentage of the transaction. Under Visa's US merchant surcharging rules, the surcharge is capped at 3% of the transaction amount; Mastercard's cap sits at 4%. Where a merchant accepts both brands — nearly everyone — the lower 3% cap binds in practice, since charging different surcharge rates by card brand at the same transaction is itself restricted under both networks' rules. A merchant intending to surcharge must give the card networks' required advance written notice through its acquirer — 30 days under Visa's rule — before the program goes live, and it must disclose the surcharge clearly at the point of entry and again on the receipt.

The debit and prepaid exclusion is absolute under both networks: a surcharge cannot be applied to a debit or prepaid card transaction, even if the cardholder's bank processes it on the credit network's rails (a "run as credit" debit transaction). This is a bright line, not a judgment call, and it's the single most common compliance failure MidPay sees in merchant surcharge programs that weren't configured to detect card type at the terminal before applying the fee.

Geography adds another layer. Connecticut, Massachusetts, Maine, and Puerto Rico maintain outright surcharge bans. Colorado caps surcharges at 2% regardless of the card network's own ceiling. New York requires the posted price to equal the cash price, which functionally bans the kind of surcharge disclosure most merchants default to. California's and Texas's surcharge bans have each been ruled unconstitutional in court, but enforcement in both states remains inconsistent — contested, not settled — so a merchant operating there should consult counsel rather than treat either state as simply open.

What makes a convenience fee different from a surcharge?

A convenience fee is a flat fee charged for the convenience of paying through an alternative channel that the merchant offers in addition to its standard payment channel — the classic example is a government agency, utility, or school that normally takes checks or in-person payment but also offers phone or online card payment for an added flat fee. Card network rules require three things that a surcharge doesn't: the fee has to be a fixed dollar amount, not a percentage; it has to apply only to the alternative channel, not to the merchant's regular point of sale; and it has to be offered as a genuine option, with the standard channel still available without the fee.

That channel requirement is why a convenience fee generally can't be bolted onto an ordinary in-person card swipe at a retail counter — there's no "alternative channel" being used; the card is simply the customer's normal way of paying in that setting. A merchant who labels an in-store card fee a "convenience fee" while charging a percentage of the sale isn't using the term correctly under network rules, and the mislabeling doesn't exempt the fee from surcharge treatment — it just means the merchant never did the surcharge paperwork.

Because a convenience fee isn't a card-brand surcharge by definition, it isn't subject to the 30-day acquirer notice or the percentage cap that governs surcharges. It still needs clear, upfront disclosure of the exact flat amount before the customer commits to paying through that channel — silence or a buried fee discovered only on the final confirmation screen is a disclosure failure regardless of which of the three fee types is actually in play.

Fee type	Structure	Applies to	Governed by
Surcharge	Percentage of transaction, capped at 3% (Visa) / 4% (Mastercard)	Credit card at the standard point of sale; never debit/prepaid	Visa/Mastercard surcharge rules, state surcharge statutes
Convenience fee	Flat dollar amount, same regardless of transaction size	An alternative payment channel (phone, mail, online) beyond the merchant's standard channel	Visa/Mastercard convenience fee rules
Service fee	Flat or itemized charge tied to a real service performed	A bona fide service distinct from simply accepting a card	General disclosure law; not a card-brand surcharge category

What qualifies as a legitimate service fee, and how is it policed?

A service fee compensates the merchant for a distinct, identifiable service rendered — a convenience store charging to cash a check, a restaurant's separately disclosed "kitchen service charge" on large parties, or a ticketing platform's processing and handling fee layered onto the price of a seat. The defining test under card network guidance and FTC deceptive-practices principles is whether the fee corresponds to something real that was done, not whether a card happened to be used. A fee that only appears when the customer pays by card, and disappears entirely when they pay cash, looks like a surcharge wearing a different name no matter what the receipt calls it.

The receipt wording never controls the classification — the structure and the trigger do.

Because a genuine service fee isn't a card-brand surcharge, it doesn't carry the percentage cap, the 30-day acquirer notice, or the automatic debit exclusion that a true surcharge does. That's exactly why regulators and card networks scrutinize the substance behind the label: a merchant that renames its card surcharge a "service fee" to dodge the cap and the debit exclusion hasn't actually changed what the fee does, and both the card networks' compliance reviews and the FTC's approach to deceptive fee practices look past the label to the underlying mechanics. Our cash discount vs. surcharge breakdown covers the closely related trap of structuring a fee as a "discount for cash" without actually restructuring the underlying pricing.

How does a merchant decide which one actually applies to their fee?

Three questions settle the classification in nearly every case. First: does the fee scale with the transaction amount, or is it a flat number regardless of the sale size? A scaling fee is either a surcharge or, in rare itemized-service cases, a percentage-based service charge — but it is never a convenience fee, which must be flat under network rules. Second: is the fee tied to using a specific alternative channel the merchant offers beyond its normal one, or does it apply across the board including the standard point of sale? Only the former can be a convenience fee. Third: would the fee exist if the customer paid cash instead? If the fee only shows up because a card was used, it is functioning as a surcharge or convenience fee depending on the first two answers — it is not a genuine service fee, because a bona fide service charge is owed regardless of payment method.

Running an existing fee program through those three questions is also the fastest way to catch a classification drift that happened gradually — a convenience fee that started flat and got switched to a percentage during a system migration, or a service fee that quietly became card-only without anyone updating the signage. Our surcharging rules 2026 reference covers the current caps and state-by-state status in more depth for the surcharge branch specifically.

What happens when a merchant gets the classification wrong?

A mislabeled fee doesn't become legal because the receipt uses a less-regulated word. If a percentage-based, card-only fee gets challenged — by a customer dispute, a card network compliance review, or a state consumer-protection inquiry — the reviewing party looks at what the fee actually does, not what it's called. A "convenience fee" that was really a surcharge in disguise gets evaluated against the surcharge cap, the advance-notice requirement, and the debit exclusion, and it will typically fail all three, because none of that paperwork was ever done under the surcharge name.

That's a materially worse position than if the merchant had surcharged correctly from the start: beyond the underlying violation, the mislabeling itself can read as an attempt to evade disclosure rules, which tends to harden a network's or regulator's response rather than soften it. The fix isn't complicated, but it does take an actual audit: pull every fee the business charges, run each one through the flat-vs-percentage and channel tests above, and rename or restructure anything that doesn't match its label — before a customer dispute forces the question.

If your processor can't walk you through which of these three categories your current fees actually fall into, or hasn't flagged a drift like the ones above, that's a sign your program needs a second set of eyes. See your rate and get a straight answer on how your current fee structure compares to a transparent, correctly classified program.

Frequently asked

Can a merchant charge a percentage-based convenience fee?

No. Card network rules require a convenience fee to be a flat, fixed amount regardless of transaction size, not a percentage of the sale. A fee that scales with the purchase amount is functioning as a surcharge and must follow surcharge rules — disclosure, the network cap, and the debit exclusion — not convenience fee rules.

Does a service fee need the same advance notice as a surcharge?

No. A bona fide service fee compensates for a distinct service actually rendered, so it isn't a card-brand surcharge subject to the 30-day acquirer notice or the percentage cap. It still needs to be clearly disclosed as a separate line item before the sale, and it has to correspond to a real service, not just a relabeled cost of accepting a card.

Can a convenience fee apply to an in-person, face-to-face transaction?

Generally no. Card network rules tie convenience fees to an alternative payment channel the merchant offers beyond its standard channel — commonly phone, mail, or online payment for a business that primarily transacts in person. A fee added to a normal in-store card swipe doesn't meet that alternative-channel condition and functions as an undisclosed surcharge instead.

Which of the three fee types can be charged on a debit card?

A surcharge can never apply to debit or prepaid cards, even when the transaction is processed as credit, under both Visa and Mastercard rules. A properly structured convenience fee or genuine service fee is not a card-brand surcharge and isn't automatically barred on debit, but it must still be a flat amount tied to a real alternative channel or service, not a disguised percentage card fee.

What happens if a merchant mislabels a surcharge as a convenience fee?

The label doesn't control the classification. If the fee is actually percentage-based and tied to using a credit card at the regular point of sale, card networks and regulators look at the structure, not the receipt wording, and treat it as a surcharge. That exposes the merchant to the same surcharge disclosure, cap, and debit-exclusion rules it was trying to avoid, plus a weaker position in any dispute because the labeling itself looks evasive.