Skip to content
Back to Blog

How to implement a compliant credit card surcharging program

November 11, 2026 Posted By yeeld
How to implement a compliant credit card surcharging program
Consulting Payment Processing payments Surcharging
Key takeaways

Your surcharge can’t exceed your cost of acceptance: In the US, Visa caps surcharges at the lower of 3% or your cost of acceptance, whichever is lower. In Canada, the cap is the lower of 2.4% or your cost of acceptance.

Every state and province sets its own rules: Surcharging is allowed in most US states and Canadian provinces, but the rules vary by jurisdiction and change often. Some prohibit surcharging, some cap it lower, and some add their own disclosure requirements. In Canada, Quebec bans credit card surcharges on consumers.

Notice rules differ by country and processor: In the US, Mastercard has suspended its registration requirement while it rewrites its surcharging rules. In Canada, the requirement remains.

Only credit cards can be surcharged: Card network rules prohibit surcharging debit and prepaid cards, even when a debit card is run “as credit.”

Customers must see the surcharge before they pay: Disclose it at entry, at checkout, and as a separate line item on the receipt / invoice.

Platforms need per-merchant controls: Rates, eligibility, locations, and rules have to be managed for each merchant, and the strictest applicable rule should apply automatically.

A 2-3% credit card acceptance cost can be one of the largest variable expenses a business carries. For a business processing $500,000 a year in card payments, fees of 2% to 3% add up to $10,000 to $15,000 a year. Surcharging lets you recover that cost by adding a fee, where eligible, when a customer chooses to pay by credit card.

The rules are the same whether you’re adding surcharging to your own payments or offering it to merchants on your platform. The difference is scale and approach. A business applies the rules to its own transactions. A platform has to apply them for every eligible merchant on every transaction.

Implementing this correctly means staying within network and jurisdictional caps, applying the surcharge only to eligible transactions, disclosing it at every step, and handling refunds and tax after the sale.

This guide walks through how to implement credit card surcharging in the US and Canada in 7 steps, with considerations for platforms along the way. If you’re new to surcharging, start with Surcharging 101.

Most compliance problems trace back to decisions made before the first transaction. Settle these three areas first.

Each card network sets its own surcharging rules and those rules continuously change. Before launch, confirm the current requirements for every card brand you accept with your processor.

Here’s where they stand today:

  • United States: Mastercard has suspended its registration requirement while it rewrites its surcharging rules, including the notification and registration process. Each acquirer has their own approach to Visa notifications.
  • Canada: Merchants must give at least 30 days’ advance notice ahead of implementing a surcharge program.

Disclosure rules apply from that first transaction as well. Our guide to credit card surcharge notice requirements covers what the language must include and where it must appear.

For platforms: Keep surcharging off by default when a merchant onboards. Turn it on only after that merchant meets the notice requirements, agrees to platform terms, and ensure your application has onboarding, payments acceptance, and refund flows set up correctly. Track each merchant’s status so a rule change can be applied across your merchant base at once.

Every surcharge has two limits. Visa caps surcharges at the lower of 3% or the merchant’s cost of acceptance, and some states set lower caps. Your rate has to stay within whichever limit is lowest.

Businesses can surcharge at the brand level (all credit cards on one network) or the product level (a specific card type within a network). Choose one approach and make sure your rate logic follows it.

For platforms: Cost of acceptance differs by merchant, so one platform-wide rate can make sense for one sub-merchant and may be over the limit for another. Set and check rates per merchant.

Most US states permit surcharging, but some do not. Connecticut, Maine, Massachusetts, and Puerto Rico prohibit it, Oklahoma and New York add their own caps or pricing display rules, and states like Oregon (Oregon’s SB 430) add pricing transparency requirements. In Canada, Quebec prohibits surcharging consumers.

These laws and the guidance surrounding them change often. Oklahoma began permitting surcharging in November 2025, Alabama stopped taxing credit card surcharges on September 1, 2026, and Louisiana’s debit card surcharge ban took effect on August 1, 2026.

For platforms: Apply rules based on each sub-merchant’s location and the customer’s location, so one rule update reaches every affected merchant.

Build Better Payment Systems: Get Started

With the rules settled, the build has one goal: every transaction gets the correct surcharge, including $0 when a surcharge isn’t allowed.

A compliant surcharge depends on three things at the moment of payment: the card type, the card brand, and where the merchant and customer are located. Surcharges apply to credit cards only, so the card’s funding type has to be identified in real time, not set as a flag in merchant settings. The same check confirms that surcharging is permitted in both the merchant’s and the customer’s jurisdictions and applies the correct rate.

When any of those checks fails, a surcharge should not be applied.

Automating this decision lets you recover processing costs on every eligible transaction without putting the rest at risk. The Yeeld surcharging engine makes this decision automatically, using a database of guidelines that covers state regulations, card brands, and funding sources.

For platforms: Run these checks centrally for every sub-merchant, so no merchant has to configure them on their own.

The surcharge must appear as a separate, clearly labeled amount before the customer confirms payment, and again on the receipt as a dollar amount. If you accept payments in person, online, by invoice, and through recurring billing, each flow needs to be considered.

Plan for coordinated updates across checkout, invoice templates, and receipts. Some states, such as New York, have specific disclosure requirements, so make sure to account for those.

For platforms: Build disclosures into the checkout and receipt templates your merchants use, so they display correctly without any merchant setup.

Recover More From Every Payment: Get Started

A program that works at checkout can still fall out of compliance afterward. Refunds and sales tax applicability are the two areas to consider.

When a surcharged transaction is refunded, the surcharge goes back to the customer with it. Partial refunds return a proportional share. For example, if a customer pays $100 plus a 3% surcharge ($103 total) and is refunded $40 of the purchase, the refund should be $41.20.

Your refund process needs to find the original surcharge and calculate the correct amount automatically. If the calculation is left to whoever processes the refund, mistakes will follow.

For platforms: Handle the calculation in the platform, so sub-merchants never work it out by hand.

Whether a surcharge is subject to sales tax depends on the jurisdiction. Some US states treat it as part of the taxable sale, and others do not. Most payment systems don’t handle this by default, so you need either a tax engine integration or jurisdiction-specific logic in your surcharge layer. Consult your tax advisor to confirm the correct treatment for your product category and jurisdiction.

For platforms: Apply the tax rule based on each transaction’s location rather than a single platform-wide setting.

For SaaS platforms and marketplaces, surcharging helps your merchants recover processing costs and can add revenue for your platform. Every requirement in this guide still applies, but it has to work for each sub-merchant on each transaction and update when rules change.

That makes the choice to build or partner a central decision. Building in-house means owning the rules engine and keeping it current as network and jurisdictional rules change. The platform opportunity in surcharging covers the commercial case and what to evaluate before you build or partner.

The cost of mistakes also grows with your merchant base. As we cover in the high stakes of credit card surcharging, one incorrect configuration can affect a large volume of transactions before anyone notices, creating compliance exposure, driving customer complaints, or impacting dispute rates.

Yeeld’s surcharging engine incorporates US state and Canadian provincial regulations alongside card network requirements, so you’re not tracking regulatory changes yourself.

  • For platforms, mid-sized business, and custom checkouts: Our Surcharging API enforces surcharging logic automatically across your stack, including a $0 surcharge where surcharging isn’t permitted.
  • For businesses on Stripe: Yeeld Surcharging for Stripe lets you recover credit card processing costs through Stripe Checkout and Payment Links. Yeeld detects the card type and client location automatically and only applies a surcharge when eligible.
Recover More on Every Payment: Install on Stripe

Credit card fees can be one of the largest variable expenses a business carries. Surcharging is one of the most direct ways to recover them, as long as it’s implemented correctly. That comes down to seven steps:

  • Confirm current card network requirements.
  • Set your rate within the cap.
  • Account for state and provincial laws.
  • Apply the surcharge only when it’s allowed.
  • Disclose it at checkout and on the receipt.
  • Refund it with the purchase.
  • Apply the right sales tax treatment.

None of these steps are a one-time setup. Card network rules are being rewritten, and state laws like Louisiana’s debit card ban keep changing what’s allowed. Your surcharging program has to keep up, whether it runs for one business or for every merchant on your platform.

Yeeld’s engine incorporates US state and Canadian provincial regulations alongside card network requirements, so you’re not tracking regulatory changes yourself. If you want to discuss Yeeld’s surcharging solutions or have any questions about your setup, contact our team.

Your surcharge can never exceed your cost of acceptance or the card network’s cap, whichever is lower. In the US, Visa caps surcharges at 3%, and Mastercard allows up to 4% only if your cost of acceptance justifies it. In Canada, the cap is the lower of 2.4% or your cost of acceptance. Some jurisdictions set lower limits or prohibit surcharging entirely.

Divide your total processing fees by your total credit card sales. For example, $3,000 in fees on $100,000 in credit card sales is a 3% cost of acceptance.

No. Card network rules prohibit surcharging debit and prepaid cards, even when a debit card is run “as credit.” Louisiana also bans debit card fees for retail businesses as of August 1, 2026. Your system should identify the card type at the moment of payment and apply a surcharge only when it’s allowed.

Yes, in most provinces. Merchants must give at least 30 days’ advance notice to Mastercard, plus any acquirer-specific requirements for notice. Quebec bans credit card surcharges on consumers but allows them in business-to-business transactions.

Refund the surcharge proportionally with the purchase, including on partial refunds. For example, if a customer paid $100 plus a 3% surcharge ($103 total) and is refunded $40 of the purchase, the refund is $41.20. Keeping the surcharge on a refunded transaction violates card network rules.

It depends on the jurisdiction. Some US states tax the surcharge as part of the sale, and others don’t. Apply the correct rule based on each transaction’s location, and confirm the treatment for your business with your tax advisor.

The requirements are the same, but a platform has to apply them per merchant, managing each merchant’s rates, eligibility, location, and rules on every transaction. A single platform-wide configuration won’t stay compliant across all merchants.

Background Pattern

Ready to work with Yeeld?

Contact Us