How to Pass Credit Card Processing Fees to Clients Without Breaking Trust Rules: The 9-Step Surcharge and IOLTA-Safe Setup for Law Firms in 2026
Card acceptance costs a typical law firm 2-3% of every dollar collected, and firms increasingly want to pass that cost along. But surcharging sits at the intersection of three separate rulebooks - state law, card network rules, and bar ethics - and one wrong configuration turns a routine payment into a trust violation. Here is the 9-step setup that keeps processing fees out of your IOLTA account.
Published: 2026-08-28T12:32:48.172Z ยท Category: Compliance ยท 10 min read
๐ณ Why This Question Keeps Coming Back in 2026
Client payment behavior has shifted decisively toward cards and ACH. That is good for collection speed - and it quietly moved 2-3% of gross collections onto the firm's expense line. On a firm collecting $6M a year with 70% of payments on card, that is roughly $126,000 in annual processing cost. It is now large enough that managing partners want it addressed rather than absorbed.
The temptation is to simply add "3% card fee" to invoices. That is where firms get into trouble, because a law firm is not an ordinary merchant. When client money passes through a trust account, the ordinary merchant playbook creates an ethics problem.
โ๏ธ The Three Rulebooks You Must Satisfy Simultaneously
๐ Rulebook 1: State law
Surcharging is prohibited or sharply restricted in a handful of jurisdictions, and several states cap the permissible amount or impose specific disclosure requirements. Multi-state firms should default to the strictest rule that applies across the states where they practice or where clients reside, rather than configuring different behavior per client. The administrative cost of a per-state surcharge matrix almost always exceeds the revenue it recovers.
๐ Rulebook 2: Card network rules
Visa, Mastercard, and the other networks permit surcharging only under conditions: advance notification to the networks and your acquirer (commonly 30 days), clear disclosure at the point of sale and on the receipt, a cap tied to your actual cost of acceptance, and - critically - no surcharging on debit or prepaid cards, even when the card is run as credit. A flat "3% on all card payments" configuration violates this on debit transactions.
๐ Rulebook 3: Bar ethics
Two model rules govern. Under Rule 1.5, a lawyer may not charge an unreasonable fee or unreasonable expense - so any pass-through should not exceed the firm's actual cost of acceptance. Under Rule 1.15, client funds in trust may be withdrawn only as fees are earned or expenses are properly incurred on that client's behalf. Your processor's fee is a firm operating expense, not a client expense chargeable against trust principal. A number of state ethics opinions go further and discourage surcharging on advance fee deposits altogether.
๐ ๏ธ The 9-Step IOLTA-Safe Setup
Step 1: Decide what you are actually recovering
Pull twelve months of merchant statements and calculate your true blended cost of acceptance - interchange, assessments, processor markup, gateway fees, chargeback fees, and monthly minimums. That blended number, not the headline rate, is the ceiling for anything you pass through.
Step 2: Confirm your jurisdiction permits it
Check your state's surcharge statute and, separately, your state bar's ethics opinions on card payments. These are two different sources and they do not always align. Where they conflict, the bar rule controls your conduct as a lawyer.
Step 3: Separate operating and trust merchant accounts
This is the structural step everything else depends on. Configure two distinct merchant accounts: one that settles to your operating account for earned-fee invoices, and one that settles to your IOLTA account for advance deposits and retainers. They must have different deposit instructions and different fee-debit instructions.
Step 4: Force all fees and chargebacks to debit operating
Instruct your processor in writing that all discount fees, monthly fees, and chargeback debits - including those arising from trust-account transactions - are drawn from the operating account. Get the confirmation in writing and keep it in your compliance file. Gross settlement into trust, fees out of operating. No exceptions.
Step 5: Do not surcharge advance fee deposits
The safest posture, and the one most consistent with ethics guidance, is to apply any pass-through only to payments of earned fees on issued invoices - never to trust deposits. Surcharging a retainer means the client's trust deposit is short by the surcharge amount, or the firm is collecting a business expense as if it were client funds.
Step 6: Exclude debit cards programmatically
Your payment configuration must detect card type at authorization and suppress the surcharge on debit and prepaid cards. If your platform cannot do this reliably, do not surcharge at all.
Step 7: Disclose in three places
The engagement letter, the invoice itself, and the payment page. Each should state the amount or percentage, that it applies only to credit card payments, and that the client can avoid it by paying via ACH or check. A documented no-cost alternative is both good practice and, in some jurisdictions, required.
Step 8: Post the fee correctly in the general ledger
The recovered amount is other income or a contra-expense - not legal fee revenue. Booking surcharge recovery as fee revenue inflates realization metrics and distorts matter profitability. Set up a dedicated GL account for it on day one.
Step 9: Reconcile monthly, three ways
Merchant statement to bank deposits to client ledgers. If the trust account was set up correctly, gross deposits into IOLTA should tie exactly to the sum of client ledger credits, with zero fee activity in between. Any difference is a red flag to resolve immediately, not at year-end.
๐๏ธ How Purpose-Built Legal Accounting Enforces This
Every step above is a policy statement until software enforces it. In practice, the failure mode is not a partner deciding to raid the trust account - it is a processor default setting that nobody reviewed, discovered eleven months later during a bar audit.
Trust and operating truly separated
LawAccounting's payment stack keeps trust deposits and operating receipts on separate rails with separate settlement instructions - the separation is structural, not procedural.
Fees posted to the right GL account
Processing costs and any recovery post automatically to designated accounts, so realization and matter profitability stay clean.
Three-way reconciliation built in
Bank balance, book balance, and client ledgers reconcile on one screen - so a netted fee against trust surfaces the same month, not at audit.
Compliance alerts
Negative client ledgers, unapplied trust, and out-of-balance conditions raise alerts rather than waiting for someone to notice.
With Fiserv, Stripe, and ProPay integrations and a branded client payment portal supporting saved cards and bank accounts, the configuration above is a setup decision rather than a monthly discipline.
- Processing fees and chargebacks must always be debited from operating - never from an IOLTA or client trust account.
- Three rulebooks apply at once: state surcharge law, card network rules, and bar ethics under Rules 1.5 and 1.15. Follow the strictest.
- Run two merchant accounts with separate settlement and fee-debit instructions: one to trust, one to operating.
- Do not surcharge advance fee deposits, and never surcharge debit or prepaid cards.
- Book any recovery as other income, not fee revenue, and reconcile merchant statements to client ledgers monthly.
- Compare surcharging against simply shifting volume to ACH - the savings are often larger with none of the exposure.
This article is general information for law firm operations, not legal or ethics advice. Surcharge law and bar guidance vary by jurisdiction and change; confirm current requirements with your state bar and your payment processor before implementing.
Payments That Cannot Touch Your Trust Account
LawAccounting separates trust and operating at the payment rail, posts every fee to the right GL account, and reconciles three ways - so card acceptance never becomes a compliance question.
Schedule Your Demo โ