Surcharging, Cash Discounting, and Convenience Fees: What's Actually Allowed

Processing costs are among the largest controllable expenses a merchant carries, and the obvious response — pass them to the customer who chose to use a card — is legal in most places and executed incorrectly by a large share of businesses that try it. The reason is that surcharge, cash discount, and convenience fee are three distinct programs with three different rulebooks, and calling one by another's name doesn't change which rules apply. Programs marketed as cash discounts are frequently surcharges in substance; surcharges are frequently applied to debit cards, which is prohibited outright. This guide covers what each program actually is, what the network and state rules require, and how to decide whether to run one at all.

Three programs, three rulebooks

	Surcharge	Cash discount	Convenience fee
Structure	Fee added to the posted price for credit card payment	Single posted price including acceptance cost, reduced for cash	Fee for using an alternative payment channel
Applies to	Credit cards only	All card payments, by structure	The specific channel, not the card type
Network registration	Generally required in advance	Not in the same form	Governed by separate rules
Cap	Capped by network rules and cannot exceed your cost	The discount is yours to set	Must be a flat amount in defined circumstances
State law	Restricted or prohibited in several states	Generally permitted more broadly	Varies
Debit cards	Never	Structure applies to all payment types	Depends on the rule set

The critical principle underneath the table: substance governs, not labels. A program where the customer sees one price and a card fee is added at checkout is a surcharge, and the surcharge rules apply — even if the provider selling it calls it a cash discount program and even if the marketing materials say it's exempt. A great many programs sold to small merchants over the past decade have been mislabeled in exactly this way, leaving the merchant carrying the compliance exposure while the provider collected the sale.

The practical test: is there one posted price that goes down for cash, or one posted price that goes up for cards? The second is a surcharge regardless of what the signage says.

Surcharging: the network rules

Card network rules govern surcharging independently of state law, and both apply simultaneously — the more restrictive one controls. The recurring requirements:

• Advance registration. Merchants generally must notify the card networks and their acquirer before beginning to surcharge, typically with a defined notice period. Skipping this is one of the most common failures and it is easily detected.
• Caps. Surcharges are capped by network rules, and separately may not exceed your actual cost of acceptance for the transaction. Profiting from a surcharge is prohibited.
• Credit only. Debit and prepaid transactions cannot be surcharged — see the next section.
• Disclosure at multiple points. Clear notice at the point of entry to the store or the website, again at the point of sale, and the surcharge itemized as a separate line on the receipt.
• Consistency across brands. Rules constrain surcharging one card brand differently from another, generally requiring either brand-level or product-level consistency in a defined way.
• Refund handling. The surcharge must be refunded proportionally when a transaction is refunded.

Two operational notes. Your processor has to support it properly — the surcharge must be applied as a separate itemized amount, not folded into the transaction total, and systems that can't do that cleanly will produce non-compliant transactions. And network rules change, including caps and disclosure specifics, which makes this a program to review periodically rather than set once.

The debit prohibition

This deserves its own section because it is absolute, it is the most common violation, and it is usually unintentional.

Debit and prepaid card transactions cannot be surcharged. Not at a reduced rate, not with disclosure, not with the customer's agreement. This holds regardless of state law and it holds even when a debit card is processed as a credit transaction, which is the specific circumstance that catches merchants out.

The operational consequence: your system must identify card type accurately before applying a surcharge. That requires proper bin identification and a point-of-sale configuration that suppresses the surcharge on debit and prepaid. A terminal that applies a flat surcharge to every card transaction is generating violations continuously, and the merchant may have no idea until an acquirer inquiry arrives.

Two related traps. Prepaid cards are covered by the same prohibition and are less obvious to detect. And a customer selecting "credit" on a debit card does not convert it into a credit card for these purposes — the underlying card type governs.

State restrictions

Surcharging is permitted in most states and restricted in several, and the landscape has shifted repeatedly through litigation over the past decade. Some states prohibit surcharging outright, some permit it with additional disclosure requirements beyond the network rules, and some have had prohibitions narrowed or struck down.

What this means practically:

• Confirm your specific state's current position before implementing, and re-confirm periodically. This is not an area where general guidance from a year ago is reliable.
• Multi-state merchants face the hardest version of this problem — the practical answer is usually either state-specific configuration or adopting the most restrictive approach nationally, and the second is cheaper to administer.
• Online sales complicate location, since the relevant state may be the customer's rather than yours, which is a question worth putting to counsel rather than resolving by assumption.
• State disclosure requirements may exceed network requirements, including specific wording and placement, so satisfying the networks is not sufficient.

The fragmentation is the same pattern our regulatory map documents across financial services — no national rule, fifty possible ones, and the strictest determining practice for anyone operating everywhere.

Cash discounting done properly

A genuine cash discount program has a specific structure, and the structure is what makes it different rather than the name.

The posted price includes the cost of card acceptance. Every price on the menu, shelf, or website is the card price. Customers paying cash — or by another non-card method you designate — receive a discount off that posted price.

Why this matters: the customer is not being charged extra for using a card. They're paying the posted price. A different customer is receiving a reduction. That's a materially different transaction structure, and it's why properly implemented cash discounting faces fewer restrictions.

What makes a program genuine rather than a mislabeled surcharge:

• Prices are posted at the card price — everywhere, consistently, including online and on any printed materials.
• The discount is applied at payment for qualifying methods, rather than a fee being added.
• The receipt reflects a discount, not a surcharge line.
• The signage is accurate and describes what actually happens.

The failure mode is common enough to name: a merchant keeps their old prices posted and adds a percentage at checkout while calling it a cash discount. That's a surcharge with different signage, it's subject to surcharge rules, and it's non-compliant in every respect the merchant believed they'd avoided. If your posted prices didn't change when you adopted the program, you don't have a cash discount program.

The honest trade-off: genuine cash discounting means your posted prices go up, which affects how you compare against competitors on price-visible items. That's a real commercial cost, and it's the reason many merchants prefer surcharging despite the heavier rules.

Convenience fees

A convenience fee is a charge for using an alternative payment channel rather than for using a card. The classic case is a merchant whose standard channel is in-person or mail, charging a fee for the convenience of paying by phone or online.

The rules that distinguish it:

• It attaches to the channel, not the card type, so it applies regardless of how the customer pays through that channel.
• There must be a genuine alternative channel without the fee — a merchant whose only channel is online cannot charge a convenience fee for using it.
• It's generally required to be a flat amount rather than a percentage, in defined circumstances.
• Network rules limit which merchant categories may use them, and the treatment varies by network.
• Disclosure before the transaction is required.

Certain sectors — government, education, utilities, and some others — have specific treatment permitting fees that would not be permitted generally, which is why merchants sometimes observe a convenience fee somewhere and conclude it's broadly available. The exception is category-specific, and assuming it applies to you is a common error.

How programs get shut down

The recurring reasons an acquirer or network intervenes:

1. Surcharging debit or prepaid, usually from inadequate card-type detection.
2. No registration with the networks or the acquirer before starting.
3. Inadequate disclosure — missing entry signage, no point-of-sale notice, or no itemized receipt line. This is the single most cited failure.
4. Exceeding the cap or exceeding actual acceptance cost.
5. Mislabeled programs, where a surcharge is run as a cash discount.
6. Not refunding the surcharge proportionally on returns.
7. Customer complaints, which are frequently the trigger that prompts the review that finds everything else.

The consequences escalate: warnings, fines passed through your acquirer, required remediation, and in persistent cases termination of the merchant account — which carries the placement and future-acceptance problems our high-risk guide describes. A program that saves two percent and costs you your processing relationship is not a saving.

One further exposure worth flagging: disputes. A customer surcharged improperly or without disclosure may dispute the transaction, which contributes to the ratio our chargeback guide identifies as the existential number in merchant processing.

Whether to do it at all

The compliance question is separate from the commercial one, and the commercial one is genuinely close for many merchants.

Where it usually works:

• B2B and professional services, where surcharging is common, tickets are large, and buyers have non-card alternatives — and where moving large invoices to bank rails is often the better answer anyway, per our ACH guide.
• Trades and contractors, where the practice is normalized.
• High-ticket, low-frequency purchases, where the customer is making a considered decision and the fee is a small proportion.
• Where competitors already do it, which removes the comparison penalty.

Where it usually doesn't:

• Retail and hospitality, where posted price comparison is immediate and the fee arrives at the moment of least tolerance.
• Low-ticket, high-frequency transactions, where the fee is proportionally large and the friction is repeated.
• Competitive markets on price, where a cash discount program's raised posted prices lose you the comparison.
• Online checkout, where a fee appearing late in the flow is among the most reliable causes of abandonment.

And the alternatives worth exhausting first, because they carry no compliance burden and no customer friction: negotiate your processing rates and understand what you're actually paying per our fees guide; route large transactions to bank rails, where the flat-fee structure produces the savings surcharging is trying to capture; capture level 2 and 3 data on B2B card transactions to reduce interchange, per our B2B guide; and improve authorization rates, since declined and retried transactions cost money that never appears on a rate sheet.

What to measure

If you implement, measure the right things — because the cost of these programs shows up in behavior rather than complaints.

• Transaction abandonment, particularly online at the step where the fee appears. This is the primary cost and it's invisible unless you look.
• Payment mix shift — how much volume actually moved to cash, ACH, or other methods, which is the benefit the program was designed to produce.
• Net savings after the shift, since a program that moves volume to a cheaper rail succeeded and one that just adds a fee to the same volume is a price increase.
• Dispute rate, watching for disputes citing unexpected charges.
• Average ticket by payment method, since customers frequently respond by changing what they buy rather than how they pay.
• Compliance sampling — pull receipts periodically and confirm the surcharge is itemized, absent on debit, and within cap.

Frequently asked questions

---

This guide is educational and does not constitute legal advice. Card network surcharge rules, caps, disclosure requirements, and state restrictions change periodically and vary by network and jurisdiction; confirm current requirements with your acquirer and counsel before implementing any program.