Every payment method is a trade between speed and cost. You can get your money in five seconds with a card tap and pay 3% for the convenience, or you can wait four days for a check to clear and pay nothing. The faster you need your money, the more you pay to get it.
Payment processors and the software platforms that bundle them have spent two decades making cards feel like the only option. For retail and e-commerce, they basically are. For local service businesses, they aren't. Most of your customers are fine paying by Venmo, Zelle, ACH, or check, especially on larger invoices where 3% is a real number.
This post covers two things: how to legally recover card fees without getting fined, and why the fee is 2.9% in the first place when your processor's actual cost on a debit transaction is closer to 25¢.
The Payment Menu
| Method | Fee | Speed | Friction |
|---|---|---|---|
| Credit/Debit Card | 2.9% + 30¢ | 1–2 business days | None for customer |
| ACH (bank transfer) | Often capped at ~$8–$10 | 3–5 business days | Customer enters routing/account |
| Venmo / Zelle | $0 (personal) / ~1.9% (business) | Instant to 1 day | Low if customer already uses it |
| Check | $0 | 2–5 business days to clear | You deposit it |
| Cash | $0 | Immediate | You deposit it, paper trail matters |
| Wire Transfer | $15–$30 (customer pays) | Same-day, available immediately | Customer initiates at their bank |
For a $10,000 remodel invoice, the fee math is the story: cards cost you $320, ACH costs you $8, Venmo/Zelle between friends costs you nothing. For a $150 service call, the math barely matters: $4.65 in card fees vs. the hassle of chasing a check.
Whether refusing cards costs you customers
The payment-processing industry has convinced a lot of small businesses that accepting cards is table stakes. For a coffee shop, it is. For a trade contractor sending $8,000 invoices, it isn't. You'd likely lose more business today by refusing cash than by saying "ACH, Venmo, Zelle, check, or add 3% for card." Almost every homeowner with a smartphone already has Venmo or Zelle installed.
Why "3% Card Processing Fee" Is Illegal
The obvious move is to put a line item on every invoice: "3% card processing fee, avoid by paying with check, cash, or ACH." It's honest, it's transparent, and it's against the rules. Two network rules make it wrong.
Rule 1: No surcharges on debit
Visa and Mastercard network rules prohibit merchants from surcharging debit card transactions. The Durbin Amendment's anti-discrimination framework backs this up. A flat "3% card fee" applied to debit is a violation, even if the customer tapped the exact same piece of plastic that could have been run as credit.
Rule 2: Honor All Cards
If you accept Visa credit, you must also accept Visa debit. Same for Mastercard. You can't dodge the debit problem by saying "credit only." This rule may loosen in late 2026 or 2027 under a pending settlement that would split cards into four categories, but as of today it's the rule.
Between those two rules, the common-sense "3% card fee" line item is doing two things wrong at once: it's charging debit users a surcharge they can't be charged, and there's no legal way to only accept the credit side of the network to avoid the problem. You have to be more specific than "card."
Three Legal Ways to Recover the Fee
There are three clean paths.
Credit-Only Surcharge
"3% credit card processing fee": specific to credit, not debit.
You're allowed to surcharge credit transactions. Visa caps surcharges at the lesser of your actual merchant discount rate or 3%. Mastercard's cap is 4%. The customer has to see the surcharge disclosed before they pay.
The catch: your payment processor has to correctly distinguish debit from credit and only apply the surcharge to credit transactions. Stripe itself supports this by auto-refunding the surcharge if the card turns out to be debit. The question is whether the platform sitting on top of Stripe gives you that toggle. Jobber, Housecall Pro, and ServiceTitan all use Stripe or similar processors under the hood, but not all of them expose selective surcharging as a setting. If you turn on a flat "3% card fee" and the underlying platform applies it to debit, you're the one on the hook for the violation, not them.
Before turning this on, confirm with your platform's support in writing that surcharges are applied to credit only, with automatic debit exemption.
Raise Prices, Offer a Cash/Check/ACH Discount
The discount side of surcharging. No network caps apply.
Raise your list prices by roughly your card-fee exposure, then offer a discount for paying outside the card network. A "2% cash/check/ACH discount" is fully legal on every card type, debit included. The Durbin Amendment specifically protects merchants' right to offer discounts for non-card payment methods.
Nothing caps the size of the discount. You could raise prices 5% and offer a 5% cash discount if you wanted. You'd still profit from customers who pay by card (they absorb the 5% price hike and you pay the 2.9% fee) and come out even with the ones who take the discount.
This is usually the smoothest option for service businesses. It doesn't require any special processor configuration, it works everywhere, and it reads as a discount, so customers feel like they're saving money rather than paying a fee.
Two-Price Disclosure (Cash Price vs. Card Price)
Show both numbers side-by-side. Customer picks before paying.
List two prices on the quote: "$5,000 cash / check / ACH" and "$5,150 card." The customer knows both numbers before they choose a payment method. This is dual pricing, and it's compliant because the customer isn't being surcharged after the fact. They're selecting from a disclosed menu.
The mechanics are cleaner than Option 1 because nothing has to be debit-exempt. The customer picks a price that already accounts for how they'll pay. Gas stations use this pattern. It works well on written quotes where the customer has time to think.
Which to pick
Large, quoted jobs: Option 3 (dual pricing) reads as transparent and gives the customer a real choice. Smaller recurring invoices: Option 2 (raise prices, offer non-card discount) is the lowest-friction way to do this at scale. Option 1 (credit-only surcharge) is the right pick only if your platform supports it cleanly, with that support confirmed in writing.
What Happens If You Get It Wrong
Enforcement on small merchants is inconsistent, but when it lands, the penalties escalate quickly. Visa's published schedule starts at a $1,000 initial fine for non-compliant surcharging, with fines compounding up to $25,000 per month after 180 days of ongoing violation. Aggregate exposure can reach six figures for persistent or high-volume violators.
The usual path to enforcement isn't a Visa auditor knocking on the door. It's a customer who got surcharged on a debit card they know can't be surcharged, calling their bank to complain. The bank's compliance team flags it to the acquirer, the acquirer tells your processor, and the fine shows up on your merchant statement. On small retail transactions, nobody calls. On a $12,000 home renovation bill with $360 in "processing fee" tacked on a debit payment, someone will.
Two state-level bans
As of 2026, two states outright prohibit credit card surcharges regardless of network rules:
- Connecticut: statutory ban on surcharging
- Massachusetts: statutory ban on surcharging
If you're in CT or MA, skip Option 1 entirely. The cash-discount approach (Option 2) and dual pricing (Option 3) are still allowed, since those are legally framed as discounts or disclosed prices, not surcharges.
Where You See It Done Wrong
You've probably walked into a coffee shop with a sign reading "3% card fee added at checkout." Sometimes that shop is compliant: their point-of-sale system is running a genuine credit-only surcharge and quietly skipping the fee when a debit card taps. A lot of the time, it isn't. They're charging every card the same surcharge, and they've never been called on it because nobody disputes a 12¢ upcharge on a $4 latte.
Small-dollar transactions hide the problem. Large-dollar transactions surface it. If you're running $150 service calls, you'll probably never hear about it. If you're collecting $8,000 from a homeowner, the math is visible enough that someone will eventually notice.
Why the Rate Is What It Is
The reason you pay 2.9% + 30¢ on every transaction has almost nothing to do with what that transaction costs the network.
On a regulated debit transaction (a debit card issued by a bank with over $10 billion in assets, which is most of them), the interchange fee is capped at roughly 21¢ + 0.05% of the transaction. Add a few cents of network assessment fees and the all-in wholesale cost to move $100 is around 40¢. Stripe charges your business $3.20 for the same transaction and keeps the difference. Even after Stripe's own infrastructure, fraud, and platform costs, the gross margin on regulated debit processing is substantial.
Where the debit cap came from
The 21¢ + 0.05% cap is Regulation II, which came out of the 2010 Durbin Amendment (part of Dodd-Frank). The goal was to prevent debit networks from charging merchants credit-like interchange on transactions that carry no credit risk. The cap is currently contested in federal court: a North Dakota case vacated it in August 2025, a Kentucky case upheld it in October 2025, and the Eighth Circuit is expected to resolve the split. For now, 21¢ + 0.05% is still the operative number.
The catch with Durbin is that it capped what banks can charge each other on debit. It didn't cap what processors can charge merchants. Stripe, Square, Jobber, and the rest still charge you a flat 2.9% + 30¢ whether you tap a debit card (which costs them cents) or a premium credit card (which genuinely costs them more). You pay the same rate for everything, which means you're quietly subsidizing the cost of premium rewards cards with the margin from your debit transactions.
There's pending federal legislation, the Credit Card Competition Act (often called "Durbin 2.0"), that would extend this framework to credit by requiring large-bank credit cards to be routable over at least two unaffiliated networks. It was reintroduced in January 2026. It hasn't passed, and the credit-card industry has fought this idea hard for two decades.
Even if it passed tomorrow, most small businesses wouldn't feel the benefit directly. You don't shop for a debit network, and you wouldn't shop for a credit network either, because you're not choosing a processor in the first place. You're choosing Jobber (or Housecall Pro, or ServiceTitan), and the payment processor comes bundled with it. Stripe is embedded inside the platform, and you can't separate the two.
Payment processing is the bundling trap's quiet third rail
We've written before about the bundling trap: how "one vendor for everything" turns convenience into lock-in. Payment processing is the part of that story that doesn't make it into the marketing pages. When you sign up for a field-service platform, you're also signing up for its processor. That bundling is worth 2.9% of your gross revenue. On $500k/year, that's $14,500 paid out at the highest level of your P&L, before any of it can become margin.
The Bottom Line
Three things worth acting on:
- 1Make ACH, Venmo, Zelle, and check visible on every invoice. Not as afterthoughts. If even a quarter of your revenue shifts off cards, the savings are real.
- 2If you want to recover the fee, pick Option 2 or 3. Raise prices 2–3% and offer a matching non-card discount, or list dual prices on quotes. Both work on every platform without special configuration.
- 3If you really want a credit-only surcharge, get written confirmation from your platform that debit is exempted before you turn it on. "Jobber supports surcharging" isn't enough. You need "surcharging is applied to credit transactions only, with automatic debit detection and exemption."
The 2.9% fee is the price of a specific choice: this payment channel, bundled with this invoicing software. Local customers can pay a lot of other ways, and most of them are faster and cheaper than the card rails everyone defaults to.