14 min read ·

Credit card surcharge rules for US online merchants

Most store owners we talk to think a credit card surcharge is a simple switch: add a percentage at checkout and keep the margin. It is not. A surcharge only works if you follow your card network's notice rules, stay under its cap, skip debit cards entirely, and avoid the states that restrict or ban it.

Get one piece wrong and you risk chargebacks, processor warnings, or a legal letter. For research-use-only peptide stores, that risk is bigger. High-risk accounts get reviewed more closely, and a messy checkout is exactly what an underwriter flags.

The short answer: in the US, you can surcharge credit cards, but not debit cards. You must disclose the fee clearly before the customer pays, and the fee can never be more than the lower of your actual cost of acceptance and the network's published cap, which Visa and Mastercard set and update. Some states restrict or prohibit surcharges.

Always confirm the current numbers with your processor or a lawyer before you turn it on. Below we cover how the rules fit together and where to read the current text. This post is about US online merchants only; Australia, for example, has its own surcharge rules under the RBA.

What a surcharge actually is

A surcharge is an extra fee you add at checkout when a customer pays with an eligible credit card. The customer sees it as its own line, separate from the product price and shipping. That is the whole definition.

Credit card surcharge shown as its own line at checkout

It is not a cash discount, where you lower the price for people who pay another way. It is not dual pricing, where you post two prices up front. It is not a convenience fee, which is a charge for a payment channel. And it is not a processor fee passed through at cost. These get mixed up all the time, and the rules differ for each one.

Four layers of permission

Most store owners ask, "Is it legal?" That question has four parts, and a yes on one does not cover the others.

  • State law. Some states restrict or ban surcharges. Others allow them with conditions.
  • Visa and Mastercard rules. The card networks set their own caps, notice requirements and registration steps for merchants who surcharge.
  • Your acquirer's terms. Your processor can be stricter than the networks. Some prohibit surcharging, and many require approval first.
  • Your checkout build. On WooCommerce, the fee line, the wording and the order of the pages all have to match what the rules require. A plugin that adds a fee silently is not compliant just because the plugin exists.

A store can clear the state test and still fail on the processor agreement, or the reverse. Check all four before you change anything.

One more plain line. None of this is legal advice. Confirm the details with your processor or a lawyer before you switch a surcharge on, because a wrong setup can put your merchant account at risk.

Card network caps and notice rules

Both major networks publish their surcharge rules. We point readers to the networks' own rules pages, not blog summaries, because the wording changes. As of 2026, here is how we read them. Check the current text before you act.

What Visa and Mastercard publish

Visa's published rules (Visa Core Rules and Visa Product and Service Rules) set a ceiling on credit card surcharges. The fee cannot exceed your actual cost of acceptance for that card or the network's stated percentage cap, whichever is lower. Mastercard's published rules work the same way.

Both allow surcharging at the brand level or the product level. We are not quoting a percentage here on purpose, because the caps have changed before and can change again.

The cap figure is a number you should read on the network's page, dated, on the day you set up.

Notice requirements

Both networks require advance notice before you start. As of 2026, Visa's rules call for notice to Visa and to your acquirer ahead of your first surcharge, and Mastercard's rules call for notice to Mastercard and your acquirer.

Each network states its own lead time and its own process, so read the current wording on each rules page and confirm the dates with your processor. Do not assume one network's timeline covers the other.

Your limit is the lowest of three numbers

In practice, your surcharge is capped by whichever of these is lowest:

  • Your real cost of acceptance on that card type
  • The network cap
  • Any stricter state rule where your customer is located

Most store owners set a flat rate and stop there. That is where problems start, because a flat rate can exceed your true cost on some cards.

Who registers what

This part trips people up. Depending on the network and your setup, the merchant, the acquirer, or both may need to register or notify. We tell store owners to get the registration confirmed in writing by their processor before the first surcharged order. A verbal "you're fine" is not a record.

If you want to see your own cost of acceptance first, our credit card processing fee calculator is a good starting point.

Debit cards can’t take a surcharge

A surcharge is a credit card fee. It is not a debit fee, and it is not a prepaid fee. Visa's rules say a surcharge may only be added to credit card transactions. Mastercard's rules say the same: surcharges are allowed on credit, not on debit or prepaid.

Credit and debit cards compared for surcharge eligibility

Both networks apply this even when the customer picks "credit" on a debit card. A debit card is still a debit card. Check each network's current rules before you launch, because these documents get updated. As of 2026, that is the position we work from.

What your gateway has to do

Your gateway needs to tell the card type before it adds the fee. That means a real lookup on the card's BIN, not a guess. If the card is a credit card, the surcharge applies. If it is debit or prepaid, the fee must drop to zero.

Ask your processor these questions before go-live:

  • Does the gateway return card type (credit, debit, prepaid) before authorization?
  • Is that lookup done on every transaction, or only some?
  • What happens if the lookup fails or times out? Does the fee default to on or off?
  • Can we see a test log that shows a debit card getting no fee?

Why a plugin alone is not enough

A surcharge plugin adds a line to the cart. It does not know what card the customer will use. If the plugin applies a flat fee to everyone, or skips the card check when it gets confused, you are charging debit customers a fee you cannot charge. The plugin is only as good as the card-type data feeding it.

Where this usually breaks

Three places cause most of the trouble:

  • Mobile checkout. Wallets and one-tap flows can hide the card type until after the total is shown.
  • Saved cards. A card stored months ago may have been checked once and never again. The fee logic should re-check, or store the type with the token.
  • Subscription renewals. Renewals run in the background with no checkout screen. If the fee was set on the first order, it may carry over to a card that is really debit.

We test all three paths when we set up peptide payment processing with a backup route.

Surcharge rules sit on top of your processing costs. To compare those costs between providers, see our guide to the best high risk payment processors for peptide brands and the peptide merchant account setup we run.

States that restrict a credit card surcharge

Surcharge law is set state by state, and it moves. We do not hardcode a list in this article, because a list that was right when we wrote it can be wrong by the time you read it. What we can tell you is where to look and how to build around the problem.

Start with the official sources. Each state's statute and its attorney general's consumer protection page are the only places we trust for a rule. Massachusetts, for example, publishes its statutes on the state legislature's own website. Card network rules are separate, and Visa and Mastercard publish their own.

Before you name a state in your checkout logic, get its restriction from the statute or the attorney general, and note the link and the date you read it. If we cannot source a state to an official page, we leave it out of the list.

We would rather be silent than wrong.

The online seller problem

If you only sold from a shop counter, your own state would be the one that mattered. Online, you ship nationwide, so the customer's state may matter too. How a given state treats a seller in another state is not something we will guess at.

Ask your processor how they handle it, and ask a lawyer who knows payments. A short call now is cheaper than a complaint later.

Build the rule so it can change

Do not bury state rules inside theme code. Keep one dated state list, stored as a setting, that your checkout reads from. Then review it on a schedule, such as every quarter, and whenever your processor sends a notice. Each entry should carry its source link and the date you last checked it.

A simple setup looks like this:

  • A list of states where the surcharge is switched off.
  • A source link and a "last reviewed" date beside each state.
  • A calendar reminder to re-check the list.
  • A default for any state not on the list that you have not yet reviewed.

When the rules are unclear

If you cannot tell what a state allows, do not guess. Turn the surcharge off for that state, or offer a cash discount there instead. Both options keep you out of a gray area while you get a firm answer.

Checkout disclosure and what breaks it

Surcharge rules are mostly about what the customer sees before they pay. As of 2026, the card networks expect the surcharge to be shown clearly before the sale is completed, and many state rules say the same. The exact wording and thresholds sit in Visa's and Mastercard's published rules and in each state's statute, so read those, not a blog summary.

In practice we check four things:

  • The fee appears as its own line item, not buried in the product price.
  • The amount or percentage is stated before the customer clicks pay.
  • The receipt shows the same fee under the same label.
  • Order records in WooCommerce match what the customer saw.

A WooCommerce test list

We run every one of these before a store goes live:

  • Credit card versus debit card (debit must not carry the fee)
  • Mobile checkout, where the fee line often gets cut off
  • Full and partial refunds, so the fee is returned in proportion
  • Subscriptions and renewals, where the fee must show again each cycle
  • Tax on the fee, since some plugins tax it and some do not
  • Receipt emails and PDF invoices
  • Failed-payment recovery emails and retry links

Most surcharge bugs hide in the last four items. They only show up after launch, when a refund or a renewal runs.

What happens on a backup route

If you use payment orchestration, one order can hit two acquirers. The first declines, the order retries on the backup route, and the fee logic runs again. Does it recalculate, double, drop or stay as first shown? Any of the first three can put the customer's receipt out of line with what they were told at checkout. We test this on staging before launch, with forced declines.

Surcharging does not fix underwriting

A surcharge only moves fee cost to the buyer. It will not make prohibited product claims acceptable to a processor. We never suggest hiding product type from a processor, and we do not help with it. Merchant underwriting, site language and refund terms come first. Fix those, then decide on a fee.

Our team handles the site, the processing and the backup route together, so these tests are not left between vendors.

Surcharge, cash discount or absorb the fee

A surcharge adds a fee to the price when a customer pays by credit card. A cash discount works the other way: you set a higher listed price and take money off for a cheaper payment method.

The result can land in the same place, but the rules often treat them differently. Card network rules tend to be stricter on surcharges, and some states regulate them more tightly.

Processors and states can still attach their own conditions to either one, so confirm with your processor or a lawyer before you pick.

A simple decision tree

Work through these in order and stop at the first one that fits.

  1. Absorb the fee. If your margins are healthy and orders are small, this is the least risky option. Nothing to disclose, nothing to get wrong.
  2. Offer ACH. Push customers who place larger orders toward bank payments, which usually cost less than cards. We cover the setup in ACH payment processing for high-risk ecommerce stores.
  3. Cash discount. Reprice and reward the cheaper method, if your processor and state allow it.
  4. Surcharge eligible credit cards only. Never debit. Keep the notice and checkout disclosure exact.
  5. Reprice the offer. If none of the above fits, build the cost into your prices and leave checkout alone.

Working out break-even

Compare two things in plain terms. On one side is the fee you recover from each surcharged order. On the other is what you might lose: customers who abandon at the final step, extra refund requests and more disputes when people see a fee they did not expect.

Higher-ticket orders are where this bites hardest. A buyer spending a lot may react more strongly to a visible fee, so the recovered amount can be wiped out by a handful of lost checkouts. A credit card surcharge calculator helps here: plug your own order values, card mix and fees into our credit card processing fee calculator and see where the line falls for your store.

What to track for 30 days

After launch, watch these side by side against your prior period:

  • Authorization rate
  • Checkout conversion
  • Cart and checkout abandonment
  • Refund rate
  • Dispute rate
  • Net margin after fees

If conversion or disputes move the wrong way, roll it back and try another branch. Our job at Peptide Marketing HQ is to keep checkout, processing and compliance working as one chain, so you are not fixing one piece while breaking another.

If you want a second pair of eyes on your checkout and processing setup, get a free store audit. And if you do go ahead with a credit card surcharge, write down the network notices, the state sources and the dates you checked them.

Frequently asked questions

Can I surcharge a customer who pays with a card that I can’t tell is credit or debit?

No. If your gateway can't confirm the card type before authorization, don't apply the fee. Debit and prepaid cards cannot carry a surcharge, so the safe default when the lookup fails or times out is to set the fee to zero. Ask your processor for a test log showing a debit card getting no fee, and confirm the details with them or a lawyer before you go live.

Do I have to tell my processor before I start surcharging, or only the card networks?

Plan on telling both. As of 2026, Visa and Mastercard each publish their own notice requirements, and your acquirer's terms can be stricter than either network. Some processors prohibit surcharging outright, and many want to approve it first. Get the confirmation in writing before the first surcharged order, because a verbal "you're fine" is not a record.

What happens to the surcharge if a customer asks for a refund?

The fee should be returned in proportion to the amount refunded. A full refund returns the full surcharge, and a partial refund returns a matching share. This is one of the spots where surcharge setups break after launch, so we test full and partial refunds in WooCommerce before a store goes live, along with how the fee shows on receipts and invoices.

Will a surcharge help my store get approved or keep a merchant account?

No. A surcharge only moves some of your fee cost to the buyer. It does nothing for underwriting, and it won't make weak site language or unclear refund terms acceptable to a processor. If you're failing review, fix the site, the policies and the product pages first, then decide whether a fee makes sense.

How do I know if a surcharge is worth it for my store?

Compare what you'd recover per surcharged order with what you might lose: abandoned checkouts, extra refund requests and more disputes from customers surprised by a fee. Use a fee calculator with your own order values and card mix. After launch, track authorization rate, conversion, refund rate, dispute rate and net margin for 30 days, and roll it back if they move the wrong way.

Free store audit

Find out what is putting your store at risk.

Payments, website, compliance and rankings reviewed by a person, with a written fix list and a 30-minute call.