Surcharge, convenience fee, service fee: three different things

A surcharge is an extra amount added specifically because the customer is paying by credit card. A convenience fee is charged for using an alternative payment channel rather than the store's usual one. A service fee is a charge for a service, unrelated to payment method. They sound interchangeable in conversation and they are not interchangeable in the rules, which is where stores get into trouble.

Getting the label right is not pedantry. Each one carries different permissions, different disclosure requirements, and different exposure.

The fastest way to tell which one you are looking at is to ask what would change if the customer paid cash. If the charge disappears, it is about the payment method. If it stays, it is about a channel or a service.

What makes a surcharge a surcharge?

It attaches to the payment method. A store that posts one price and adds an amount at the register because the customer chose a credit card is surcharging, whatever it calls the line on the receipt.

Card network rules govern surcharging closely, and several states restrict or condition the practice. Two things are consistent across the rules: debit cards may not be surcharged, and the amount may not exceed what you pay to accept the card. Visa publishes its merchant rules and fees publicly.

What makes a convenience fee different?

It attaches to a channel, not a card. The classic case is a business whose normal payment channel is in person, charging a fee for the alternative of paying by phone or online. Every customer using that channel pays it regardless of how they pay.

The distinction collapses if the channel fee is really a card fee in disguise, which is what happens when the alternative channel accepts only cards. That is the version that draws attention, and calling it a convenience fee does not change what it is.

Where does a service fee sit?

Outside the payment question entirely. A delivery charge, a special-order fee, a fee for processing a return without a receipt — those are charges for services and are priced like anything else you sell. They apply regardless of tender and carry no card network implications.

If a store wants to recover processing cost and does not want to navigate surcharging, this is not the escape hatch. A "service fee" that appears only on card transactions is a surcharge with a different name on the receipt.

Why does the naming matter so much?

Because the substance decides, not the label. Regulators and card networks look at what the charge is actually doing: is it triggered by the payment method, and does it apply differently to cash. A program described one way and operating another way is the risk, and it is the store posting the price that carries it rather than the processor that configured the terminal.

That is the sentence worth remembering. Your provider sets up the terminal; your name is on the sign.

What should a store do before starting any of these?

Three things. Decide which of the three you are actually doing, in writing and in plain words. Confirm with your provider that your terminal is configured for that specific program, including the debit exclusion if you are surcharging. And get legal advice about your own state, because this is a genuine jurisdictional question rather than a hedge — state law varies and it varies materially.