Blog · Merchant Economics
Passing Credit Card Fees to Customers: What's Legal, and How to Do It Right
Quick answer: Passing credit card fees to customers is legal in most US states, but only for creditcards, only up to your actual cost of acceptance (and under the card-network cap), only after registering with the card brands, and only with clear disclosure before payment and an itemized line on the receipt. Debit and prepaid cards can never be surcharged, anywhere. A handful of states restrict or ban the practice, and adding a manual “3% processing fee” line to invoices, the way most businesses try it first, violates the rules almost by construction.
The short answer
Card acceptance costs 2–3.5% of every sale, and the question every margin-conscious business eventually asks is whether the customer who chose the expensive payment method can carry that cost. The answer is yes, in most states, through three legal structures: a surcharge (a fee added to credit transactions), a cash discount (a posted card price, discounted for cash), or dual pricing (both prices shown up front). We've compared the three models in depth in our surcharging vs dual pricing vs cash discount guide; this article is about the passing-the-fee decision itself, the rules that make it legal, and the mistake almost everyone makes when they try to do it inside their invoicing software.
The five rules that make it legal
- Credit only, never debit. Debit and prepaid cards cannot be surcharged in any state, even run-as-credit debit. Your checkout has to detect card type in real time; a human adding a line item can't.
- Register before you start. Visa and Mastercard require the surcharge program to be registered before the first surcharged transaction. Skipping this is a violation even if everything else is perfect.
- Cap it at your cost. Never more than your actual cost of acceptance, never more than the network cap (confirm the current figure with your processor, it has changed over time), and never more than your state allows.
- Disclose twice. At the point of entry (site, door, invoice) and at the point of payment, with the fee as its own line on the receipt. A fee the customer discovers on the receipt is the single biggest generator of “I didn't agree to this” chargebacks.
- Check your state. Most states permit compliant credit surcharging; a few restrict or ban it, and several impose specific display rules (New York, for example, requires showing the higher total price). Our state-by-state surcharging guide tracks where each state stands.
The QuickBooks problem
Here's where most small and mid-size businesses actually attempt this, and where it goes wrong. QuickBooks has no built-in compliant surcharging program, so the workaround everyone reaches for is a manual invoice line: “Credit card processing fee, 3%.” That line breaks the rules three ways at once:
- It applies to whatever card the customer uses, including debit, which is prohibited everywhere.
- It was almost certainly never registered with the card brands.
- A flat 3% frequently exceeds the actual cost of a given transaction, violating the cap.
And on QuickBooks Payments' pricing there's a second irony: the fee you're trying to recover, roughly 2.99% on invoiced cards and 1% uncapped on ACH, is itself higher than it needs to be for most invoice-heavy businesses (we've broken that down line by line in the QuickBooks Payments fee guide). The compliant route is processor-level: the payment page behind your invoice detects card type, applies the surcharge to credit only, discloses it before confirmation, itemizes the receipt, and then the transaction, surcharge included, syncs back into QuickBooks by API or QuickBooks-format CSV. You get the recovery; your books stay clean; nobody surcharges a debit card.
The B2B version: steer to ACH instead
If your customers are businesses paying invoices, there's a structure that recovers more than a surcharge does and annoys nobody: dual pricing with ACH as the low price. The payment link on the invoice offers two options, pay by card at the card price, or pay by bank transfer at a lower price. Both prices are disclosed up front, so most surcharge-specific rules never trigger; there's no debit-detection problem because there's no fee; and every customer who picks the bank option moves a large invoice onto a rail that costs you a flat few dollars instead of a percentage. On a $30,000 invoice, that's the difference between recovering ~$800 of card cost and never incurring it.
The compliant setup, end to end
- Decide the model: surcharge (credit-heavy volume, surcharge-friendly state), cash discount (small-ticket in person), or dual pricing (online, invoices, B2B, the safest default). The 60-second framework walks through it.
- Verify your state in the state-by-state guide, then re-verify before any expansion, this law moves.
- Run it at the processor level. Card-type detection, conditional application, disclosure, receipt itemization, and card-brand registration are all things a payment platform does and an invoice line item doesn't. We configure compliant surcharging and dual-pricing programs as part of boarding.
- Sync it back to your books. The surcharge or dual-price outcome flows into QuickBooks with the rest of the transaction data, so recovery shows up in your accounting without manual journal entries.
FAQ
Passing credit card fees FAQ
Is it legal to pass credit card fees to customers?
In most US states, yes, for credit cards, subject to strict conditions: you must register the surcharge program with the card brands before starting, cap the fee at your actual cost of acceptance (and under the network cap), disclose it before and at checkout, itemize it on the receipt, and never apply it to debit or prepaid cards. A few states restrict or ban credit surcharging and several add disclosure requirements, so check your state's rules before launching, and re-check them periodically, because this area of law keeps moving.
How do I pass credit card fees to customers on an invoice?
The compliant pattern is processor-level, not manual: your payment link or checkout detects the card type, applies the surcharge to credit cards only, shows it before the customer confirms, and itemizes it on the receipt. The common shortcut, adding a 3% 'processing fee' line item to every invoice by hand, is where businesses get into trouble, because it surcharges debit cards (prohibited everywhere), skips card-brand registration, and often exceeds the actual cost of acceptance. Alternatively, dual pricing (showing a card price and a bank-transfer price) avoids most surcharge rules entirely.
Can I add a credit card surcharge in QuickBooks?
Not automatically, QuickBooks has no built-in compliant surcharging program. You can manually add a fee line to an invoice, but a manual line can't detect card type, so if the customer pays that invoice with a debit card you've surcharged a debit transaction, which card-brand rules prohibit in every state. The compliant route is to run the payment through a processor whose checkout applies the surcharge conditionally, and sync the transaction back into QuickBooks. That's how our QuickBooks integration handles it.
How much can I charge customers for using a credit card?
Never more than your actual cost of acceptance, and never more than the card networks' cap, whichever is lower, with some states imposing lower limits or specific display rules. The network cap has changed over time, so confirm the current figure with your processor rather than a number from an old article. Practically, most compliant programs land in the 2–3% range.
Is dual pricing better than surcharging for a B2B business?
Often, yes. For invoice-based businesses the cleanest structure is showing two prices on the payment link, a card price and a lower bank-transfer (ACH) price, and letting the customer choose. It sidesteps most surcharge-specific rules because both prices are disclosed up front, it never touches the debit-card problem, and it steers large invoices toward ACH, which on a flat-fee processor costs you a few dollars instead of a percentage. You recover the fee difference without ever charging a 'fee.'
Recover the fee without breaking the rules.
Surcharging, dual pricing, or ACH steering, we set up the compliant version for your state and your invoices, synced to QuickBooks.