

If you are trying to offset card processing costs, you will usually hear two options: add a credit card surcharge or offer a cash discount.
They can look similar to customers, but they are not the same operationally. The difference matters because card brand rules and some state laws treat surcharges differently than discounts.
This guide breaks down what surcharging is, how cash discount programs work, where merchants get into trouble (often by accidentally surcharging debit), and a practical checklist to launch either approach with fewer compliance headaches.
A credit card surcharge is an added fee that only applies when a customer pays with a credit card.
In practice, it is a percentage (or flat amount) added at checkout, shown before the customer pays, and listed as a separate line item on the receipt.
The important part is that it is tied to the payment method. If the fee only happens when someone uses a credit card, you are in surcharge territory, even if you label it something else.
A cash discount program starts with a single, higher posted price (sometimes called the standard price). Then you offer a discount when the customer pays with cash or another non-credit method.
That structure matters because the customer is not being charged extra for choosing a card. They are receiving a discount for choosing cash.
Merchants use cash discount programs because they can be simpler to explain at the counter, and in some places they are allowed even where credit card surcharging is restricted.
There is no one-size-fits-all answer.
At the network level, Visa and Mastercard allow credit card surcharging in the US if you follow their rules, including limits and disclosure requirements, and you do not surcharge debit or prepaid cards (Stripe).
Separately, some states restrict or prohibit surcharging, and those rules can change over time. This is why processors and POS providers often restrict surcharging availability by location (Elavon).
Practical takeaway: treat this as a compliance project, not just a pricing tweak. You need to confirm both (1) your state rules and (2) your processor and network requirements.
Start with the requirements that show up again and again across processor programs and network guidance.
This is the most common failure point.
Many checkout flows show a card as "Visa" or "Mastercard" even if it is debit. The rule is based on card type, not the logo.
If you apply your surcharge to any debit or prepaid transaction, you can end up out of compliance, even if it was accidental. POS platforms that support surcharging emphasize that debit and prepaid surcharging is prohibited (Toast Support Center).
Surcharges cannot exceed your cost of acceptance or the applicable network cap. Visa has a 3% cap in the US, and the general rule is the cap is the lower of your cost (your merchant discount rate) or the network limit (Stripe).
This is why a one-size 4% surcharge setting can be risky, even if your processor says it is "normal". You need to tie the rate to your actual processing costs, and keep documentation.
Disclosure is not just a receipt line.
You generally need clear notice at the point of entry and at the point of sale, plus disclosure in online checkout before card details are entered (Stripe).
Your receipt should also show the surcharge as a separate line item so it is not hidden in the total (Stripe).
Visa requires merchants to provide notice before surcharging starts, and many processors handle the formal steps as part of enabling a surcharge program (Stripe).
Do not assume you can simply flip a switch in your POS with no paperwork.
Most surcharge compliance issues are operational, not intent.
Here are the main ways it happens.
Some terminals allow a debit cardholder to choose "credit". That does not turn the card into a credit card.
If your setup keys off the transaction routing instead of card type, you can accidentally apply the surcharge to debit.
A safer approach is to use BIN-based card identification or a POS surcharge feature that distinguishes debit and prepaid automatically (Toast Support Center).
If a fee applies to credit, debit, and prepaid, it is not a compliant credit card surcharge.
It is also one of the fastest ways to trigger complaints and chargebacks.
If you want a universal fee, structure it as a service fee applied to all payment types (and then make sure it is allowed in your vertical and location). That is a different program with different risk.
Cash discount programs can fail when the price display and receipt language contradict each other.
Example: You post the lower cash price on the shelf, then add a "non-cash adjustment" at the register for card users. Many customers experience that as a surprise fee.
If you are doing a cash discount, the standard price should be the posted price, and the discount should be visible and applied when someone pays cash.
| Feature | Credit card surcharge | Cash discount |
|---|---|---|
| What changes for customers | Credit card payments cost more | Cash payments cost less |
| Debit/prepaid allowed to be adjusted | No, do not surcharge debit/prepaid (Toast Support Center) | Usually yes, discount can apply to cash only, but confirm local rules |
| Typical setup | POS applies a % fee only to credit cards | POS uses standard price and applies discount on cash |
| Customer perception risk | Higher if disclosed poorly | Can be lower if pricing is clearly posted |
| Processor/program requirement | Often requires enablement and compliance steps (Elavon) | Often offered as a program by processor/POS, still needs clear pricing |
Online is where merchants get tripped up, because disclosure has to happen before payment.
For ecommerce, the surcharge policy should be disclosed on the first page that references card brands, and it should show before the transaction completes (Stripe).
For invoices and B2B payment links, treat the invoice as the point of sale. The customer should see the surcharge rate and the total before they submit payment.
If you are using a third-party invoicing tool or platform (Shopify, WooCommerce, QuickBooks, etc.), check whether it supports compliant surcharging or cash discount workflows.
Your goal is not to profit from the fee. Your goal is to offset your cost of acceptance.
In practice, most merchants pick a number that approximates their effective rate. Some POS vendors even suggest a rate based on observed processing costs and warn against exceeding it (Toast Support Center).
Here is a practical method:
If you have interchange-plus pricing, your effective rate should be relatively stable. If you are on tiered pricing, it may swing more month to month, which makes surcharging harder to keep aligned.
Related read: Interchange Fees Explained: What Every Merchant Needs to Know
Even if your state allows it, disclosure is non-negotiable.
At a minimum, plan for:
Keep the language simple. Example:
"We add a X% surcharge to credit card purchases to cover processing costs. No surcharge is applied to debit or prepaid cards."
Also train staff on how to explain the fee without blaming the bank or card brand.
Neither is automatically safer. The risk depends on your business model and how well you execute.
Surcharging tends to create more complaints if customers feel surprised, so the disclosure and receipt formatting matters.
Cash discounting tends to create less friction in some retail environments, but only if your posted price and receipt match the structure.
If you have higher chargeback risk (subscription billing, continuity offers, longer fulfillment times), your processor may already be watching customer friction signals. In those cases, adding checkout friction can backfire.
Related read: Merchant Account Reserves and Holds: Why They Happen and What to Do
If you surcharge, you need to consider recurring payments. Customers are more likely to dispute when the price changes after signup.
Make sure the surcharge policy is disclosed at signup, in the terms, and on the invoice.
If you are in a tipped environment, the surcharge may apply to the total ticket, including tip, depending on how your POS calculates it. That can create awkward conversations.
Test the flow on a few transactions before you roll out.
B2B customers often accept card fees, but they expect them to be spelled out. Put the policy directly on the invoice and the payment page.
Do not let your processor treat this like a checkbox.
Ask:
If your processor cannot answer clearly, consider switching to one that has a dedicated surcharge or cash discount program.
Use this checklist whether you choose surcharging or a cash discount.
No. Surcharging is allowed in many US states, but some states restrict or prohibit it, and the rules can change.
Confirm your state rules, then confirm your processor supports a compliant program in that location.
No. Debit is still debit, and card brand rules prohibit surcharging debit and prepaid cards (Toast Support Center).
Your surcharge should not exceed your cost of acceptance or the network cap. Visa caps US surcharges at 3%, and the general rule is the cap is the lower of your merchant discount rate or the network limit (Stripe).
Yes. Disclosure should happen before the customer pays. For online checkout, that means disclosing the policy before card details are entered and showing the surcharge before the transaction completes (Stripe).
No. With a cash discount, the posted price is the standard price and you apply a discount when someone pays with cash.
With surcharging, you add a fee when someone pays with a credit card.
If you want to offset processing costs without creating compliance problems, the details matter more than the headline.
You can apply for a merchant account through Easy Pay Direct or another processor that fits your model. Other options worth a look: