Yes, you can charge a convenience fee or surcharge in the United States, but only within tight limits set by three overlapping authorities: your state’s statute, the card network’s operating rules, and your payment processor’s registration requirements. A convenience fee applies when you offer a genuine alternative payment channel; a surcharge applies specifically to card payments instead of cash. Before you flip the switch, confirm your state permits it, register your intent with the applicable card networks, and verify your processor supports single-transaction fee capture.

TL;DR:

  • Merchant eligibility depends on having a genuine alternative payment channel for convenience fees or specific card use for surcharges, with strict compliance to disclosure rules.
  • Visa requires a formal registration 30 days before surcharge implementation, and fees must not be applied to debit or prepaid cards, with strict single-transaction processing.
  • State laws vary widely, with some explicitly banning surcharges and others allowing them under specific disclosure and cap conditions, requiring ongoing verification.
  • Card network rules enforce pre-disclosure, non-discrimination, and single authorization, with violations often caused by split transactions or late customer notice.
  • Proper setup involves comprehensive documentation, gatekeeper configuration, and regulatory research to avoid fines, chargebacks, or account termination.

Table of Contents

Convenience Fee Rules: The Fast Facts You Need First

Before you build anything, know the numbers and the traps. Card networks cap what you can charge and dictate how you disclose it, and getting either wrong triggers fines or account termination.

  • Cap context: Visa limits surcharges to your actual cost of acceptance, commonly cited as up to 3%, and convenience fees are typically flat dollar amounts rather than a percentage.
  • Debit is off-limits: you cannot surcharge debit or prepaid cards under any card network’s program, even in states that allow credit card surcharging.
  • Disclosure timing matters: customers must see the fee before they authorize payment, not buried in a receipt or a follow-up email.
  • Brand-by-brand differences: Visa, Mastercard, American Express, and Discover each set their own registration windows and fee-structure rules, so a program compliant on one network can violate another.
  • Split transactions kill compliance fast: if your gateway processes the base charge and the fee as two separate authorizations, you’ve violated the single-transaction requirement even if the total is accurate.
  • Uneven treatment invites complaints: charging a fee on one card brand but not another, or on some transactions but not others in the same channel, is one of the most common triggers for chargebacks and regulator inquiries.

These aren’t bureaucratic footnotes. Acquirers reverse surcharges and freeze accounts over exactly these details.

What Convenience Fees and Surcharges Actually Mean

The core distinction is simple once you see it: a convenience fee is tied to the payment channel, while a surcharge is tied to the payment method. Stripe’s guidance on convenience fees frames it plainly. A convenience fee applies when a customer chooses a non-standard way to pay, such as phone or online, while a mail-in check remains available at no extra cost. A surcharge, by contrast, applies specifically because the customer used a credit card instead of cash or debit, regardless of channel.

Government agencies use convenience fees constantly. A county tax office might waive fees for mailed checks but add a flat charge for online card payments, because the county still offers a “standard” channel free of charge. An insurance company might charge a fee for phone payments but not for its mailed-invoice option.

Eligibility hinges on two things: your merchant category code (MCC) and whether you have a genuine alternative channel to point to. A business that is exclusively card-not-present, meaning it has no cash or check option at all, generally cannot claim the convenience fee exemption, because there’s no “standard” channel to compare against. That business would need to pursue surcharging instead, subject to its state’s rules on credit card surcharges.

Common examples that clarify the split:

  • Convenience fee, valid: a utility company charges $3.95 for online bill pay but accepts mailed checks free.
  • Convenience fee, invalid: an online-only subscription box tries to charge a “convenience fee” on every order, with no alternative channel to justify it.
  • Surcharge, valid: a retail shop adds a percentage fee specifically for credit card use, disclosed at the point of sale, in a state that permits it.
  • Surcharge, invalid: that same shop applies the fee to debit card transactions too.

Pro Tip: If you can’t name the free, standard payment channel your convenience fee is an alternative to, you probably don’t qualify for a convenience fee program. You’re looking at surcharge rules instead, and those come with a stricter set of state law questions.

There’s no single federal law that blanket-bans convenience fees or surcharges. Instead, you’re navigating three layers that all have to line up: federal consumer protection law, card network contracts, and state statutes. Miss any one layer and you’re exposed, even if the other two are satisfied.

Federal layer. 15 U.S.C. §1693o-2 addresses reasonable fees and rules for electronic payment transactions, and it underlies the framework regulators use to evaluate whether a fee practice is fair. The Federal Trade Commission enforces against deceptive fee practices more broadly under Section 5 of the FTC Act, which means a merchant that hides a fee until the final checkout screen, or advertises one price and charges another, risks an FTC complaint regardless of what your state statute says about surcharging specifically. Federal law sets the floor for honesty in pricing disclosure. It doesn’t grant blanket permission to surcharge.

Card network layer. Visa, Mastercard, American Express, and Discover each operate under their own merchant agreements, and those agreements function as binding contracts, not suggestions. A merchant that surcharges without registering, or that surcharges above the permitted cap, isn’t just risking a customer complaint. They’re risking a direct violation of their merchant services agreement, which can lead to fines assessed against your acquiring bank, and your acquiring bank passing that cost straight to you, sometimes alongside account termination. Card network rules are frequently stricter than state law, which means passing your state’s legal test doesn’t guarantee you’re compliant with the network you’re actually running transactions through.

State layer. States can and do restrict or ban surcharging entirely, and where they allow it, they often set their own caps or disclosure requirements independent of the card networks. A handful of states have historically prohibited surcharges outright, and even where the practice is legal, states frequently require specific language on receipts or signage disclosing the exact fee amount before the transaction completes. NCSL’s summary of state surcharge statutes tracks this state by state, and it changes as legislatures act, so treat any static list, including this one, as a starting point rather than a final answer.

If federal disclosure guidance says “before authorization” and your state says “on the receipt,” disclose before authorization, because that satisfies both.

A few operational habits keep you defensible if a dispute ever surfaces:

  • Keep dated records of your state law research, including the specific statute or AG guidance you relied on.
  • Save your card network registration confirmations and the date you filed intent to surcharge.
  • Screenshot your checkout disclosure language as it appeared to customers, not just the final version in your codebase.
  • Log any changes to your fee percentage or amount, since caps can shift and you need proof you adjusted in response.

None of this documentation prevents every dispute. It’s what turns a customer complaint or acquirer inquiry into a quick resolution instead of a drawn-out investigation.

Which States Allow Surcharges, and Which Ban Them?

State law is the layer most likely to trip up a merchant expanding into new territory, because it varies by where your business is registered and sometimes by where the transaction occurs. A handful of states have historically prohibited credit card surcharges outright, including Connecticut, Massachusetts, and Oklahoma, though litigation and legislative changes have narrowed some of these bans in recent years. Other states once on restrictive lists, like New York and Texas, have shifted toward permitting surcharges under specific disclosure conditions after court challenges argued that outright bans violated merchants’ free speech rights around pricing.

This is exactly why a static “banned states” list is dangerous to rely on without verification. NCSL’s state-by-state summary is built to track these changes as they happen, and it’s the resource to check before you assume your state’s rule hasn’t moved.

Where surcharging is allowed, states typically layer on their own conditions beyond what the card networks already require:

  • Disclosure requirements that go further than “before checkout,” sometimes mandating specific font sizes or exact wording on signage and receipts.
  • Caps that mirror or sit below the card network cap, often in the 2% to 4% range, meaning a state cap can be more restrictive than Visa’s cost-based limit even when both technically allow surcharging.
  • Registration or notice requirements at the state level, separate from anything you file with your card network or acquirer.
  • Exemptions for certain transaction types, such as government fee payments or specific industries, that don’t follow the general state rule.

The practical takeaway: your registered business location determines which state’s rule governs your surcharge program, not necessarily where your customer lives. A merchant based in a permissive state selling to customers nationwide generally follows their own state’s rule for surcharge legality, though card network rules still apply universally regardless of geography. That said, if you have a physical retail presence in a restrictive state, transactions at that location typically fall under that state’s ban, even if your online store operates under a different state’s more permissive rule.

Where to confirm current status, every time you launch or expand:

  • Your state’s own statute text, searchable through your state legislature’s website.
  • Your state Attorney General’s consumer protection page, which often summarizes surcharge rules in plain language.
  • NCSL’s tracking summary, updated as legislative sessions close.
  • Your acquiring bank or processor’s compliance team, who deal with state-level surcharge questions across their entire merchant portfolio and often catch changes before they hit the news.

Don’t treat any blog post, including this one, as your final legal confirmation. State surcharge law has moved substantially over the past decade, largely through court challenges, and it will keep moving. Verify against a primary source before you launch, and check again if you expand into a new state or open a new physical location.

Card Network Rules: Visa, Mastercard, American Express, and Discover

Each card network runs its own program, and the differences between them are exactly where most merchants get tripped up. Passing Visa’s requirements doesn’t automatically mean you’ve satisfied Mastercard’s, even on the same transaction.

Close-up of payment terminals with blurred logos

Visa requires pre-disclosure of the exact fee before the customer authorizes payment, single-transaction processing so the fee and the purchase amount combine into one authorization, and formal registration of your intent to surcharge. That registration typically needs to happen 30 days before you launch, and failing to file it is one of the most common reasons acquirers reverse a surcharge program after the fact. Visa also caps the surcharge at your actual cost of card acceptance, with 3% referenced as the outer limit in Visa’s own guidance.

Mastercard permits a broader set of fee structures in some programs, including flat, percentage, and tiered arrangements depending on merchant category, and it publishes separate rules for government and education-sector merchants that differ from its general commercial guidance. That means a school district charging a tuition convenience fee may operate under different permitted structures than a retail merchant surcharging card transactions.

American Express and Discover both enforce non-discrimination requirements, meaning if you surcharge one network’s cards, you generally need to apply the same treatment across all card brands you accept, and both require clear disclosure before the transaction completes.

The technical detail that catches merchants across every network: the fee has to be part of the same authorization as the purchase, not a second, separate charge. Processor guidance on split-transaction failures identifies this exact failure mode as one of the most frequent causes of surcharge program violations, often because a gateway’s default settings process the base amount and the fee separately without the merchant realizing it.

The 30-day registration window that trips up most new surcharge programs: Visa requires merchants to notify their acquirer and, in many cases, formally register intent to surcharge a full 30 days before launch. Skip this step and your acquiring bank has grounds to reverse every surcharge you’ve collected, retroactively, even if your fee amount and disclosure were otherwise compliant.

Processor manuals reinforce a related point that’s easy to miss: equal treatment across card brands within a single channel isn’t optional, and customers generally need a clear option to cancel the transaction before the fee is finalized. A program that surcharges Visa and Mastercard but quietly exempts American Express, because your negotiated Amex rate happens to be lower, is a violation waiting to surface the first time a customer or competitor notices.

How to Roll Out a Compliant Fee Program

Treat this as a launch sequence, not a checklist you fill in after the fact. Each step depends on the one before it.

  1. Confirm program eligibility. Decide whether you qualify for a convenience fee (you need a genuine alternative channel) or need surcharge rules instead (you’re charging specifically for card use). Your MCC and whether you’re card-not-present-only will determine which path applies.
  2. Check your state’s current rule. Search your state’s statute text directly and cross-reference against NCSL’s tracking summary. Document the date and source you checked.
  3. Notify your acquirer and register with card networks. File your intent to surcharge with sufficient lead time, generally around 30 days for Visa, and keep the confirmation. Ask your processor directly whether Mastercard, American Express, or Discover have separate registration steps for your merchant category.
  4. Select the correct fee structure. A flat dollar amount fits most convenience fee programs. A surcharge needs to be calculated against your actual cost of card acceptance and stay under both your card network’s cap and your state’s cap, whichever is lower.
  5. Configure your gateway for single-transaction processing. Confirm with your payment processor, in writing, that the fee and the purchase amount combine into one authorization. Ask specifically about this if you’re integrating a new gateway or switching platforms, since default settings vary.
  6. Build pre-payment disclosure into your checkout flow. The exact fee amount needs to display before the customer authorizes payment, not on the receipt afterward.
  7. Test with sandbox transactions before going live. Run test payments, screenshot the disclosure screen and receipt, and confirm the authorization total matches what the customer saw.
  8. Schedule a recurring compliance audit. State caps shift, card network cost-based limits move with your processing costs, and legislative sessions change the rules more often than most merchants expect. Quarterly is a reasonable cadence for a growing business.

Pro Tip: Keep every registration confirmation, screenshot, and dated compliance note in one folder, not scattered across email threads. If a customer files a chargeback dispute or your acquirer flags your account for review, having that documentation ready in minutes instead of days is often the difference between a quick resolution and a frozen account.

For a broader look at how payment compliance programs get built and maintained across a business, this guide to payment processing compliance walks through the operational side in more depth.

The Mistakes That Trigger Fines and Chargebacks

Four mistakes account for the overwhelming majority of convenience fee and surcharge violations, and every one of them is preventable with the checklist above.

  • Split transactions. Your gateway processes the purchase and the fee as two separate authorizations instead of one combined charge, violating the single-transaction rule even when your disclosed total is accurate.
  • Surcharging debit or prepaid cards. No major card network permits this, regardless of what your state allows for credit cards specifically.
  • Disclosing the fee too late. Showing the fee on the receipt, in a confirmation email, or anywhere after the customer has already authorized payment fails every network’s pre-disclosure requirement.
  • Double-fee errors. A software bug or a gateway misconfiguration that charges the fee twice, or applies it to a transaction that should have been exempt, generates chargebacks fast and erodes customer trust even faster.

When one of these surfaces, three enforcement routes typically follow. Customers dispute the charge directly with their card issuer, triggering a chargeback that lands on your processing statement. Your acquiring bank, having its own liability under the card network agreement, can sanction your account, reverse the fees, or terminate your merchant agreement if violations repeat. State regulators or the FTC can act on consumer complaints, particularly where the practice looks deceptive rather than accidental.

Remediation moves fastest when you act before a regulator does. Refund or adjust the improper fee immediately once you spot it. Respond to chargebacks with documentation showing your disclosure screen and registration status. File a correction notice with the card network if a misconfiguration caused a systemic issue, rather than waiting for individual disputes to pile up. For a program that’s already drawn regulatory attention, or where the exposure spans thousands of transactions, bring in counsel before you respond rather than after.

Why Compliance Expertise Beats Guesswork for Regulated Merchants

Most convenience fee violations I’ve seen aren’t the result of merchants trying to cut corners. They’re the result of a gateway’s default settings quietly splitting a transaction into two authorizations, or a merchant assuming their state’s rule is the only rule that matters. The card network layer gets ignored constantly, because it’s buried in a merchant agreement most business owners never read line by line.

That gap matters more for merchants in nutraceuticals, telehealth, supplements, and other regulated or high-growth categories, where chargeback ratios are already under scrutiny and a fee violation adds fuel to an existing fire. A subscription supplement brand running recurring billing can’t afford a surcharge misconfiguration triggering disputes on top of the return-rate issues that high-risk categories already fight.

Davincipay works with acquiring relationships and gateway integrations built for exactly this kind of complexity, including the technical detail of combining a base charge and a fee into a single authorization instead of two. The fixes are rarely dramatic. They’re usually a registration filed on time, a gateway setting corrected before launch, and documentation kept in order so a dispute resolves in days instead of dragging into an account freeze.

— Peter

Get Your Fee Program Set Up Right the First Time

Building a compliant convenience fee or surcharge program from scratch means juggling state law, four different card network rulebooks, and your gateway’s transaction settings, all before you process a single dollar. Davincipay handles that groundwork directly, combining acquiring relationships with gateway configurations built to process fees as a single authorization instead of a compliance risk waiting to surface.

Davincipay

For merchants in nutraceuticals, supplements, telehealth, and other regulated or high-volume categories, that means underwriting support and fraud tools built around the chargeback pressure these industries already face, not a generic setup borrowed from low-risk retail. Davincipay’s team helps confirm your registration requirements, checks your fee structure against the applicable caps, and configures your gateway before you ever risk a split-transaction violation. If you’re ready to launch a compliant fee program or need your existing setup reviewed, start your application and a specialist will walk through your specific channel and category. Merchants in supplements and nutraceuticals can also see how Davincipay structures processing for their exact regulatory profile.

Where to Verify the Rules Yourself

Confirm every claim in this guide against the primary source before you rely on it, since state law and card network programs change:

Keep a bookmarked checklist of your specific state’s Attorney General page and your acquirer’s compliance contact. Rules move faster than most merchants expect, and the primary source always beats a summary, including this one.

This article is general information, not a substitute for advice from a qualified financial advisor. Consult a qualified financial professional about your own circumstances before acting on anything here.

Sources