TLDR
- A flat surcharge applied to every card transaction violates Visa and Mastercard rules. Card-brand compliance requires you to surcharge at the card type level, not the transaction level.
- Surcharging is prohibited by state law in Connecticut, Massachusetts, and Puerto Rico as of current card-brand guidance, and rules shift by jurisdiction, requiring market-specific logic rather than a single global setting.
- Disclosure requirements, surcharge caps, and commercial card eligibility differ between Visa and Mastercard, meaning your rules engine must handle both independently.
- The platforms compared here differ meaningfully on whether they handle disclosure rendering, card-type detection, and jurisdiction suppression out of the box or require your team to build that logic separately.
- Payment reconciliation for surcharged transactions adds complexity that most billing stacks are not set up for without additional tooling.
B2B credit card surcharge management software allows merchants to recover card acceptance costs by passing a fee to the paying business, but only when the software can detect the card type, apply jurisdiction-specific suppression, cap the surcharge at card-brand maximums, and render required disclosures before the transaction authorizes. Three platforms purpose-built for this workflow are Zift, CardX (now part of Stax), and Paysign’s commercial surcharge module. Each handles the rules engine and disclosure layer differently, and the right choice depends on how your payment flow is structured and whether you need API control or a hosted checkout.
Why Can’t You Just Add a Fixed Fee to Every B2B Card Transaction?
The assumption that surcharging is a simple line-item addition breaks down fast once you read Visa’s and Mastercard’s surcharging rules. Both card networks cap surcharges at a specific percentage of the transaction, and that cap is tied to the merchant’s actual cost of acceptance for that card category, not a number you choose. Per Visa’s publicly posted surcharging guidelines, Visa caps surcharges at 3%; per Mastercard’s published surcharging rules, Mastercard caps them at 4%. Both sets of rules are subject to change, so merchants should verify the current caps directly with each network before configuring a surcharge program.
Beyond the caps, surcharging is only permitted on credit cards, never on debit cards or prepaid cards, even when those cards run on a credit card network. A corporate Visa debit card looks identical to a Visa credit card at the checkout unless your system performs real-time card-type detection through a BIN lookup. Charge a surcharge on a debit card and you are out of network compliance immediately.
State law adds another suppression layer. Connecticut and Massachusetts prohibit credit card surcharges by statute. Puerto Rico also prohibits them. Any surcharge software that does not suppress the fee for transactions originating in those jurisdictions is exposing the merchant to legal liability, not just a card-brand violation. This is the core reason a rules engine exists: not to calculate a number, but to decide whether to apply any fee at all given the card type, the issuing geography, and the merchant’s registered state.
What Does a Surcharge Rules Engine Actually Do?
A surcharge rules engine is the decision layer that sits between card authorization and fee application. It runs at minimum four checks before any surcharge is added: BIN-based card type identification (credit vs. debit vs. prepaid), jurisdiction eligibility based on merchant state and sometimes the cardholder’s billing address, card-brand rule compliance including the merchant’s registered surcharge rate on file with Visa and Mastercard, and disclosure triggering to surface the required pre-transaction notice.
Merchants who want to surcharge must notify Visa and Mastercard at least 30 days before they begin surcharging, per both networks’ published requirements. That notification registers the merchant’s intended surcharge rate. If the software later charges a different rate, the merchant is non-compliant. A proper rules engine holds that registered rate and applies it consistently, with no manual override at the transaction level.
The disclosure requirement is the piece most teams underestimate. Visa requires that the surcharge be disclosed at the point of entry and on the receipt. Mastercard has similar requirements. A platform that only shows the fee on the final receipt fails compliance. This matters operationally because it means the checkout UI, the invoice, and the confirmation all need coordinated disclosure copy, something a rules engine must drive rather than leaving to your team to bolt on manually.
For B2B SaaS teams thinking about how payment fees affect gross margins, the hidden costs killing fintech SaaS margins breakdown is a useful reference for where card acceptance costs show up in the P&L before and after surcharge recovery.
Surcharge Rules and Disclosure Requirements by Market
| Jurisdiction | Surcharging Permitted? | Key Rule or Restriction | Disclosure Required? |
|---|---|---|---|
| United States (federal) | Yes, on credit cards only | Cap of 3% (Visa) or 4% (Mastercard); debit and prepaid cards excluded | Yes, at point of entry and receipt |
| Connecticut | No | State statute prohibits surcharges | N/A |
| Massachusetts | No | State statute prohibits surcharges | N/A |
| Puerto Rico | No | Surcharges prohibited | N/A |
| All other US states | Yes, on credit cards only | Must notify card networks 30 days before surcharging begins | Yes, pre-transaction and on receipt |
| Canada | Yes (permitted following a 2022 Visa/Mastercard class action settlement) | Rules mirror US caps; prohibition on surcharging debit transactions applies | Yes, at point of sale |
Canada’s surcharging rules became active following a Visa and Mastercard class action settlement. Canadian merchants can surcharge credit card transactions under rules that largely parallel the US framework, including the prohibition on surcharging debit transactions. If your B2B customer base spans both countries, your software must handle the Canadian rules set as a distinct configuration, not an extension of US rules.
Platform 1: CardX by Stax

CardX, acquired by Stax, is the most widely deployed purpose-built surcharging platform in the US market. Its core design premise is full rules-engine automation: the merchant sets no surcharge rate manually because CardX detects the card type, applies the network-compliant rate, suppresses the surcharge for prohibited states, and handles the pre-transaction disclosure display automatically. The merchant registers their surcharge program with Visa and Mastercard, and CardX manages ongoing compliance from there.
CardX operates on a model where the merchant pays no credit card processing fees when the surcharge program is active on credit card transactions. Cash and debit card transactions are processed at a flat rate. The platform provides hosted checkout pages, virtual terminals, and API access, making it usable for both invoice-based B2B billing and embedded payment flows. CardX does not publicly list per-transaction pricing on its website; teams should request a quote directly for current rates.
The jurisdiction suppression logic is automatic. When a cardholder’s billing ZIP code resolves to Connecticut or Massachusetts, CardX does not apply the surcharge. This is the platform’s strongest differentiator for teams that do not want to maintain their own state-level eligibility logic. The disclosure rendering is handled by CardX’s hosted elements, which means if you are building a custom checkout, you need to use their UI components for the disclosure layer rather than writing your own copy.
Who CardX Fits Best
CardX is the right call for merchants who want compliance automation with minimal engineering overhead. If your team is not staffed to maintain a BIN lookup layer and a state eligibility matrix, CardX handles both. It is a weaker fit for teams that need deep API control over the checkout experience or that run complex multi-entity billing where the surcharge logic needs to vary by payer segment.
Platform 2: Zift

Zift positions itself as a surcharge-first payment platform built specifically for B2B merchants who want to recover card acceptance costs through compliant surcharging rather than absorbing fees. The platform includes BIN-based card type detection, automatic suppression for prohibited jurisdictions, and pre-built disclosure templates that satisfy Visa and Mastercard requirements. Zift’s customer-facing portal lets payers see the surcharge amount before confirming payment, which satisfies the point-of-entry disclosure requirement without requiring custom UI work.
Zift supports both credit card surcharging and dual pricing, where the merchant displays a cash price and a card price simultaneously. For B2B contexts, dual pricing can be more palatable than a surcharge label because it frames the difference as a discount for non-card payment rather than an added fee. Whether that framing is appropriate depends on your customer relationships and how your contracts define payment terms.
Pricing is not publicly listed on Zift’s website; teams should contact Zift directly for current rates. The platform targets small to mid-market B2B merchants and professional services firms, and their sales process is quote-based. Teams running high-volume commercial card programs should ask specifically about their handling of Level 2 and Level 3 card data, since optimizing interchange on commercial cards alongside surcharging is a separate but related workflow. For context on how B2B interchange optimization tools handle Level 3 card data, that comparison covers the mechanics in detail.
Who Zift Fits Best
Zift is a strong match for professional services firms, field services companies, and B2B merchants who bill primarily through invoices or a customer portal. If you want dual pricing as an option alongside traditional surcharging, Zift is one of the few platforms that supports both under the same account. Teams that need a deep payment API for embedded billing should evaluate whether Zift’s integration surface covers their use case before committing.
Platform 3: Payroc with Surcharge Module

Payroc is a payment processor that offers a compliant surcharge module as part of its merchant services stack. The surcharge module handles BIN lookup for card type detection, rate application bounded by card-brand caps, jurisdiction suppression, and receipt disclosure. Payroc’s approach differs from CardX and Zift in that surcharging is one feature of a broader payment processing relationship rather than the organizing principle of the platform.
This distinction matters operationally. With Payroc, your surcharge configuration sits inside a merchant account that also handles all other payment types, reconciliation, and reporting. If you are already running card processing through a Payroc relationship or evaluating them as a primary processor, the surcharge module integrates without adding a separate vendor. If you are evaluating surcharge software independently of your processor, you would be switching processors to access the module, which is a larger change than adding a point solution.
Payroc does not publish surcharge module pricing separately from its broader merchant services pricing; merchants should request a full fee schedule that breaks out the surcharge program costs alongside base processing rates to compare total cost accurately. Teams running complex multi-entity setups should also review how Payroc handles payment reconciliation across surcharged and non-surcharged transactions, since the reporting structure for surcharge recovery differs from standard processing reports.
Who Payroc Fits Best
Payroc makes the most sense for merchants who want to consolidate surcharge management with their primary processor rather than layer a separate platform on top of an existing stack. It is a reasonable choice for mid-market B2B companies already in or evaluating a Payroc relationship. Teams that want processor-agnostic surcharge software should look at CardX or Zift instead.
The FintechSpecs Surcharge Stack Diagnostic: Four Checks Before You Choose
Most vendor comparison frameworks for surcharge software focus on features. This one focuses on the four points where a misconfigured surcharge program generates legal or financial exposure, because those are where the real decision criteria live.
Check 1: BIN resolution speed and fallback behavior. Ask each vendor what happens when their BIN lookup returns an indeterminate result. The correct fallback is to not apply the surcharge. A fallback that defaults to applying the fee exposes you to surcharging a debit card, which violates network rules.
Check 2: Jurisdiction suppression ownership. Confirm in writing whether the platform automatically suppresses surcharges for prohibited states or whether your team must configure and maintain that suppression logic. If it is your responsibility, you need an internal process to update the list when state laws change.
Check 3: Disclosure rendering control. If you are building a custom checkout, verify that the platform’s disclosure components can be embedded in your UI without requiring the payer to leave your flow. Some platforms require redirect to a hosted page, which can interrupt embedded payment experiences.
Check 4: Network registration support. Surcharging merchants must register with Visa and Mastercard before they begin surcharging. Ask whether the platform handles this registration on your behalf or whether you file it independently. Missed registration is one of the most common surcharge compliance failures.
How Do Surcharge Programs Affect Payment Reconciliation?
When a surcharge is applied, the transaction settles in two logical parts: the base invoice amount and the surcharge fee. Most payment processors net these together in settlement, but your accounting records need to separate them. The surcharge is revenue-neutral by design, it offsets the card acceptance cost, but it still flows through your books as both an income line and a corresponding expense. Getting that reconciliation wrong creates overstated revenue and incorrect cost-of-goods reporting.
This is where teams frequently underestimate implementation effort. Standard billing platforms, including Stripe Billing and Chargebee, do not natively model a surcharge as a separate fee line that ties to a card acceptance cost offset. You either need a custom line item on your invoice template or a middleware reconciliation layer that tags surcharged transactions separately at settlement. Platforms like CardX and Zift generate their own reporting on surcharge amounts recovered, but that data needs to flow into your general ledger structure, which is a finance operations task, not a configuration toggle.
Frequently Asked Questions About B2B Credit Card Surcharge Management Software
Can you surcharge commercial credit cards differently than consumer credit cards?
Yes, and this is an important distinction for B2B merchants. Card-brand rules allow surcharging at the product level, meaning you can apply different rates to different card categories such as standard credit, rewards credit, and commercial credit, as long as each rate stays within the network cap and your registered rate. Some B2B merchants choose to surcharge only commercial cards because that is where their interchange cost is highest. Your surcharge software must support product-level rate configuration to execute this correctly.
What is the maximum surcharge percentage allowed in the US?
Per Visa’s and Mastercard’s currently published surcharging rules, Visa caps surcharges at 3% and Mastercard caps them at 4%. These caps are subject to change and merchants should verify current figures directly with each network. The actual surcharge you can charge is also capped at your cost of acceptance for that card category, whichever figure is lower. A merchant with a 2.5% effective rate on Visa transactions cannot charge a 3% surcharge on those cards even though the network cap allows it. The registered rate must reflect actual cost.
Does B2B card surcharge software work with invoicing platforms like QuickBooks or NetSuite?
Integration depth varies significantly by platform. CardX has documented integrations with several popular accounting and invoicing tools. Zift and Payroc’s surcharge module integration capabilities depend on your specific invoicing setup and will require verification with each vendor. In most cases, the surcharge amount flows through the payment link or portal rather than being calculated inside the invoicing platform itself, with the reconciled amount syncing back to the ledger after settlement.
What happens if you accidentally surcharge a debit card?
Applying a surcharge to a debit card violates Visa and Mastercard network rules, regardless of whether the debit card carries a Visa or Mastercard logo. Violations can result in fines from the card network, chargeback exposure from the cardholder, and in some cases termination of your merchant account. A BIN lookup that correctly identifies debit and prepaid cards before applying any surcharge is not optional. It is the minimum threshold for running a compliant surcharge program.
How should disclosure be handled on a B2B invoice payment portal?
Visa and Mastercard both require that the surcharge amount be disclosed to the cardholder before the transaction completes. On an invoice payment portal, this means the surcharge must be visible and acknowledged before the payer enters card details or at minimum before they confirm payment. A disclosure that only appears on the receipt after authorization does not meet network requirements. CardX and Zift both include pre-built disclosure components for portal environments. If you build a custom flow, you must engineer this disclosure step independently.
Is surcharging always better than absorbing card fees for B2B merchants?
Not automatically. Surcharging shifts the card acceptance cost to your customer, which protects margin but introduces friction. B2B buyers paying with corporate cards sometimes push back contractually, and some enterprise procurement teams flag surcharges during vendor evaluation. A dual pricing model, where you offer a lower price for ACH or check and a higher price for card, can achieve the same economic result with less friction because it frames the difference as a discount rather than a fee. The right model depends on your average contract value, the payment mix you expect, and your customer base’s tolerance for surcharge language in invoices.
Which B2B Surcharge Platform Should You Shortlist?
CardX is the default choice for most B2B merchants evaluating surcharge software for the first time. Its compliance automation, including jurisdiction suppression and disclosure rendering, reduces the operational burden enough that most finance and engineering teams can run a compliant program without dedicated headcount on the rules layer. Zift is the better option when dual pricing is part of your strategy or when you serve professional services customers who respond better to cash-price framing than to surcharge labels. Payroc’s surcharge module makes sense only if you are already in a Payroc processor relationship or if consolidating vendor count is a higher priority than optimizing the surcharge feature set.
The important framing is that all three platforms are tools for executing a compliant program, not substitutes for understanding the rules. A surcharge program configured incorrectly inside any of these platforms still generates network violations. The card-brand registration, the BIN logic, the disclosure placement, and the state-level suppression all need to be verified in your specific implementation, not assumed to be handled by the software alone. Teams evaluating their broader payment infrastructure should also review how payment infrastructure tools for SaaS founders stack against each other at the processor and gateway layer, since surcharging software does not operate independently of the underlying payment stack.
The practical next step is to run the FintechSpecs Surcharge Stack Diagnostic against each vendor’s sales process. Use the four checks as your interview script. Any vendor that cannot answer the fallback behavior and jurisdiction suppression questions in writing, with specifics, is telling you that your team will own more of the compliance risk than their marketing implies.















