What Is Surcharging? A Merchant Guide

What is surcharging?

Surcharging adds a fee to a credit card payment at the register. The customer pays the listed price plus that fee. Evolve reports network caps and disclosure requirements, and that surcharging does not apply to debit or prepaid cards. State rules matter, so the same setup may not fit every merchant.

That is the short answer to what is surcharging. The rest depends on where you operate, which card the customer uses, and how the price appears before payment. A surcharge is not the same as a second advertised price. It is an added amount attached to an eligible credit card transaction.

That distinction matters because a merchant surcharge carries several decisions. You must identify the payment type. You must apply the right limit. You must disclose the charge at the right points. You must also follow the registration and monitoring requirements described by the card networks.

This guide answers the surcharging question before discussing other pricing structures. It starts with the credit card surcharge itself. Only then does it compare this model with the other pricing structures merchants consider.

How does surcharging work?

Think of credit card surcharging as a sequence. Each step must finish before the next one begins.

1. Step 1: Start with the listed price. The customer sees the normal price for the product or service. That price is the starting point for the transaction.
2. Step 2: Identify the payment type. Surcharging applies to credit card payments. It does not apply to debit or prepaid cards, a rule covered in its own section below.
3. Step 3: Add the surcharge at the register. The fee sits on top of the listed price. The customer then sees the original amount and the added amount as separate parts of the payment.
4. Step 4: Apply the permitted cap. The maximum depends on the applicable state and network rules. Colorado and the states that permit surcharging do not all use the same limit.
5. Step 5: Disclose the charge before payment. The customer needs notice at entry and at the point of sale. The price cannot become a surprise at the final click or tap.
6. Step 6: Show the charge on the receipt. The surcharge appears as its own line item. That keeps the listed price, the surcharge, and the payment total distinct.

For a simple example, a listed service price remains the starting amount. An eligible credit card payment then carries the added surcharge. The receipt shows both pieces instead of blending them into one unexplained total.

The mechanic sounds simple. The hard part is keeping the same rule across signs, menus, checkout screens, and receipts. It is also easy to use the wrong rule when a debit card carries a credit card brand logo. The payment type still needs to be handled correctly.

Before choosing a merchant surcharging program, write down the full sequence. Start with the listed price. Identify the card. Check the cap. Disclose the fee. Print the line item. That order gives your team one process to follow.

Is surcharging legal, and where?

There is no single answer for every US merchant. State rules carry both bans and caps.

Arryved and Evolve each report that credit card surcharging is prohibited in Connecticut, Massachusetts, Maine, and New York. Both put the Colorado cap at 2%, and Arryved puts the cap in most allowing states at 4%.

Those state rules do not turn into a blanket approval for every location. A merchant needs the rule for the state where the transaction occurs, plus the network requirements for the program.

CardFellow presents an important counterposition about labels. It writes, If you charge more at the register than the listed price, it is a surcharge, regardless of what processors call it. That view focuses on the customer-facing price change, not the name placed on the program.

That distinction helps you inspect a proposed setup. Ask what price the customer sees first. Ask whether the register adds an amount afterward. Ask whether the receipt names that amount. The answers describe the structure more clearly than a product label.

Use those state and network rules as boundaries, not as a substitute for setup review. State restrictions and network rules work together. A program that fits one merchant may need a different configuration for another state.

Can you surcharge debit cards?

No. Surcharging debit cards is not permitted.

Evolve reports that surcharges cannot be applied to debit or prepaid cards. That rule applies even when a debit card carries a familiar card-network logo. The payment type matters for the surcharge decision.

This is a place where a register process can go wrong. A team member sees the logo and treats every card the same. The correct sequence checks the payment type before adding any fee.

Prepaid cards belong in the same no-surcharge category. Do not treat a prepaid card as eligible credit just because the customer wants to use it at the counter. The fee rule follows the card type.

Build the debit and prepaid rule into the checkout flow. Give staff a plain instruction. If the payment is debit or prepaid, do not add the surcharge. If the payment is credit, continue through the cap and disclosure checks.

Use the same explanation when a customer asks. The fee attaches only to the eligible credit card path. Staff should not improvise a different answer at the register.

Follow card-network requirements

State rules are only one part of compliant surcharging. The card networks have their own process requirements.

1. Register the practice. Evolve reports that merchants must register surcharge practices with the networks before using them.
2. Keep the cap visible to your team. Colorado is reported at 2%. Arryved reports that most states allowing surcharges cap them at 4%. Your setup must use the applicable limit.
3. Post notice at entry. The customer needs to know that the credit card path includes a surcharge before reaching the register.
4. Repeat notice at the point of sale. The final payment screen or counter disclosure should make the added amount clear before payment.
5. Print a line-item receipt. The surcharge should remain visible as part of the receipt total, rather than disappear inside one blended number.
6. Monitor the program. Evolve reports that Visa, Mastercard, and other card companies monitor surcharge practices, and that non-compliance risks fines or MID termination.

These steps are not a design exercise. They are the operating sequence for the program. Signs, checkout screens, staff instructions, and receipts should tell the same story.

Registration does not replace disclosure. A sign does not replace the receipt line item. The cap does not remove the debit and prepaid rule. Each control answers a different customer or network question.

That is why the network section deserves its own review. A merchant may understand the fee but miss the registration step. Another may register but fail to show the amount before payment. The process needs both.

Keep your review practical. Identify the person who owns the setup. Identify where the price appears. Identify how the card type is determined. Then confirm the receipt shows the same structure the customer saw before paying.

Which model fits your business?

Start with the price structure you want customers to understand.

Surcharging fits one question: can I add a fee to an eligible credit card payment? That path requires state limits and network registration. It also requires network monitoring, entry notice, point-of-sale notice, and a line-item receipt.

Dual pricing fits another question: can customers see both prices before payment? It puts that comparison in front of the customer. It also keeps the card price as the base, advertised price, according to IntelliPay. The full dual pricing guide compares the two models row by row, including the debit rule and the caps.

Cash discounting fits a third question: do I want to offer a reduction for cash? GoPayBright reports no percentage cap. It also reports cash discounting is legal in all 50 states. IntelliPay reports that the Durbin Amendment protects this right in every state. The amendment is part of Dodd-Frank from 2010.

Runs as dual pricing, not a surcharge: customers see both prices before they pay. State disclosure rules vary; we configure the disclosures and receipts for your state at setup.

Typical all-in cost with us: 2.2%-2.5%. Most software-bundled processors run 2.9%-3.6%. Want to pay near zero? Customers who pay by card cover the fee, about 3.5%.

Read the pricing details after you decide which customer-facing structure you need.

The right choice depends on the price you want to show and the process you can operate consistently. If you want a state-specific review, the call gives you a place to read through the setup with a person.