Why Law Firm Payment Processing Isn’t Like Every Other Business
Why Law Firm Payment Processing Isn’t Like Every Other Business
Law firm payment processing looks simple from the outside — run a card, get paid, move on. But a practice carries a constraint almost no other business has: much of the money a client hands you isn’t yours yet. A retainer, an advance on costs, a settlement waiting to be disbursed — that’s the client’s money, held in trust, until you’ve earned it or paid it out on their behalf.
That one fact reshapes how a firm should take cards. Under the ABA Model Rule 1.15 on safekeeping property — and the state-bar versions built on it — client funds must stay completely separate from the firm’s own money. Two accounts, two worlds: an operating account for earned fees and overhead, and a client trust account (the IOLTA, in most states) for money that still belongs to clients. The wall between them isn’t a bookkeeping preference. Breaching it, even by accident, is one of the fastest routes to a bar complaint.
Attorney payment processing carries that constraint whether you’re a solo taking a first retainer or a litigation boutique running settlements every week — which is why law firm payment processing deserves a different vetting process than picking a professional services merchant account for a consulting shop. The right question isn’t “which processor is cheapest.” It’s “which processor understands that one of my accounts is legally untouchable.”
Earned fees and overhead live in operating. Unearned client money — retainers, cost advances, settlement funds — lives in trust. The firm’s money may never sit in trust, and client money may never sit in operating, even briefly. Every payment decision has to respect that wall.
Where Most Processors Quietly Put a Firm at Risk
Here’s the failure in law firm payment processing that catches firms off guard, because nothing on the surface looks wrong. A client pays a $1,000 retainer by card. It’s unearned, so it has to go into trust. But a standard merchant account does what it does for every other business: it pulls the processing fee out of the transaction before the money lands. At a typical rate, about $980 reaches the account — and $20 has vanished as a fee.
For a coffee shop, that’s the cost of accepting cards. For a law firm, it’s a trust-accounting problem. The client’s ledger says $1,000 is in trust. The account holds $980. The trust is now short of what the records say, and the firm has let a processing cost be paid out of client money. Those trust account credit card fees are exactly what the rules forbid: processing fees and bank charges must come from the operating account, never from the principal of a trust account.
The firm can patch it by depositing $20 of its own money to make the trust whole — but now it’s moving firm funds into trust to cover a fee and chasing a shortfall the processor created. Multiply that across dozens of payments a month and law firm credit card processing built on a generic merchant account becomes a slow-motion compliance risk rather than a convenience.
When a processor skims its fee off the top of a trust deposit, the account holds less than the client ledger says it should. That gap isn’t a rounding error — it’s a reportable trust violation, and “the processor did it automatically” is not a defense a disciplinary board accepts.
What “Bar-Compliant” Actually Means for Your Processor
The fix isn’t an exotic product — it’s a processor configured to respect the wall. A compliant law firm payment processing setup does three things a generic account doesn’t. It deposits the full transaction amount into trust, so a $1,000 retainer lands as $1,000. It debits the processing fee separately, from operating, so client money is never touched. And it produces an audit trail — per-client, per-matter detail — that survives a reconciliation or a random bar audit.
That separation is the whole game. Earned-fee and invoice payments route to operating; retainers and advances route to trust at full value; fees land where they belong. A correctly configured IOLTA trust account processing arrangement means your monthly reconciliation actually matches your ledgers instead of forcing you to chase small shortfalls you didn’t create — the core of real legal payment processing compliance.
None of this means giving up cost transparency. A firm can run it on interchange-plus pricing, where the processor’s markup is a fixed, visible line rather than buried in a blended rate. If you’ve never separated the network’s cost from your processor’s margin, running a recent statement through an effective rate calculator is the fastest way to learn your real rate before you negotiate anything.
Full deposits into trust, fees pulled from operating, and clean per-matter records mean your reconciliation matches your books, your trust account is never quietly short, and you’re not fronting your own money every month to cover a fee the processor should have handled correctly.
Can You Charge Clients the Processing Fee?
Plenty of firms would rather not absorb 2 to 3 percent on every card payment, and the obvious move is to pass the fee to the client as a surcharge. This is the second place law firm payment processing diverges from an ordinary merchant account: for a law firm a surcharge is legal in some places, restricted in others, and layered with an extra rulebook the corner store never has to read. Three sets of rules apply at once: your state’s surcharge law, the card networks’ surcharge rules, and your state bar’s ethics rules — including ABA Rule 1.5, which says a lawyer’s fees and expenses must be reasonable.
Where surcharging is permitted, most bar ethics opinions let a firm pass along the actual processing cost — no markup — as long as the client agrees in advance, ideally in writing. A few states (Massachusetts and Maine among them) prohibit surcharges outright, and the landscape keeps moving: Oklahoma’s 2025 statute now caps any client surcharge at 2 percent or the processor’s actual fee, whichever is lower. The networks add their own limits, the biggest being that you can surcharge credit cards but never debit — so a compliant program has to switch off debit surcharging entirely.
The trust-account wall still applies: a surcharge can’t be pulled from trust, and surcharging a retainer headed into trust risks commingling all over again. A surcharge belongs to operating, full stop. These rules overlap with the broader world of dual pricing merchant services and cash discount programs, and which approach is even allowed comes down to where you practice — the credit card surcharge legality by state picture is genuinely a state-by-state question.
Many firms decide the client-relationship cost of a surcharge isn’t worth it and instead steer larger payments — settlements, big retainers — toward ACH and eCheck, where a flat, low per-transaction fee beats a percentage of a five-figure transfer by a wide margin. Others simply work to reduce the underlying processing rate so the absorbed cost stops stinging. There’s no single right answer — but there is a wrong one, which is bolting a surcharge onto a setup that never sorted out the trust-account mechanics first.
- Three rulebooks apply at once — state law, card-network rules, and your state bar’s ethics rules.
- Where allowed, you can generally pass only the actual cost, with the client’s advance (written) consent.
- Credit cards only — debit can never be surcharged.
- A surcharge belongs to operating; it can never come from, or be added to, a trust deposit.
What to Ask Before You Hand a Processor Your Trust Account
Whether you’re opening a first law firm merchant account or replacing a setup that never fit the practice, the vetting questions are specific. Does the processor deposit the full transaction amount into trust and debit fees from operating — in writing? Can it route earned-fee payments to operating and unearned retainers to trust without manual sorting? Does it give per-client, per-matter ledger detail and monthly reconciliation reports? If you surcharge, does it exclude debit and keep surcharges out of trust automatically?
It’s worth pulling in the people who already see the failure modes. CPAs and bookkeepers who serve law firms catch trust shortfalls at reconciliation; many state bars publish trust-accounting guidance and a list of approved IOLTA institutions; and a good processor should welcome those questions, not wave them off. The contract matters as much as the rate — before signing, look at the merchant agreement for term length, early-termination clauses, and equipment leases that can outlast the relationship.
Done right, law firm payment processing is genuinely an asset: clients pay faster, receivables turn over quicker, and trust accounting stays clean without extra effort. Done on a generic account, it’s a quiet liability waiting for an audit. The difference is almost never the rate on the first page — it’s whether the processor was ever built to respect the wall between your money and your clients’.
Frequently Asked Questions
No. Processing fees and bank charges may not come out of the principal of a client trust account — they have to be paid from the firm’s operating account. The risk most firms miss is that a standard processor skims its fee before the deposit lands, leaving the trust short of the client ledger. A compliant setup deposits the full amount into trust and debits the fee from operating instead.
Sometimes. It depends on three things at once: whether your state allows surcharging, the card networks’ rules (credit only, never debit), and your state bar’s ethics rules, which generally require that any passed-through fee reflect only the actual cost and be disclosed in advance. A few states prohibit it entirely. A surcharge can never be taken from or added to a trust deposit — it belongs to the operating account.
The trust-account requirement. A regular merchant account assumes every dollar you collect is yours; a law firm collects money that often still belongs to the client and must be held separately from firm funds. That means the processor has to deposit unearned funds into trust at full value, pull its fees from operating, and produce records detailed enough to survive a bar audit — capabilities a generic account isn’t built to provide.
Keep Reading Before You Choose a Processor
Make sure your processor respects the trust-account wall. Find out in one statement.
Send us a recent processing statement and we’ll show you your real effective rate, whether your fees are being handled correctly against your trust account, and where a compliant setup could save your firm money — no obligation, no sales pressure. Learn more about payment processing consumer protections from the CFPB.
Review My Firm’s Processing SetupNo obligation • No pressure • Response within one business day