How to Accept Credit Card and ACH Payments at Your Law Firm Without Breaking Trust Accounting Rules: The 2026 Compliance Guide

💳 Why This Matters More in 2026

Electronic payments are no longer optional. Firms that let clients pay from their phone collect faster, write off less, and spend fewer staff hours chasing checks. But the same convenience that helps your accounts receivable can quietly violate your state's trust accounting rules if the money flows through the wrong pipes. With state bars tightening trust account oversight — California's compliance review program being the most visible example — getting the plumbing right is now table stakes.

⚖️ Rule 1: Unearned Funds Go to Trust — Even When Paid by Card

The fundamental rule of legal payments doesn't change because a card is involved: money you haven't earned yet belongs to the client, and client money lives in your trust account. A retainer paid by Visa is just as much trust money as a retainer paid by check.

That means your payment system must be able to route deposits by type. An invoice payment for work already billed goes to operating. A retainer, advance fee deposit, or settlement-related payment goes to trust. Generic processors built for e-commerce have one deposit account; legal-specific systems let you designate trust and operating destinations per payment.

🧾 Rule 2: Processing Fees Never Come Out of Client Funds

When a client pays a $5,000 retainer by card and the processor takes a 3% fee, the client's trust ledger must still show the full $5,000. The $150 fee is a firm expense, payable from operating. A processor that nets fees out of trust deposits will leave you with trust ledgers that don't match what clients are owed — a shortfall you may not notice until your three-way reconciliation breaks, or worse, until a bar auditor notices it for you.

Look for processing that debits fees from the operating account while depositing gross amounts to trust. This is a standard capability of legal-specific payment platforms and almost never the default behavior of generic ones.

↩️ Rule 3: Plan for Chargebacks Before You Have One

Chargebacks are the scenario most firms never model. A client disputes a card payment that went to trust; the processor claws the money back; but you may have already disbursed some of those funds for that client's matter. If the clawback pulls from the trust account, other clients' money is now covering the gap — an instant violation.

🏷️ Rule 4: Know Your State's Surcharging Position

Passing card fees to clients ("surcharging") is permitted in many states but restricted or prohibited in others, and card networks impose their own notice and cap requirements. Several bar opinions also treat surcharges on advance fee deposits differently from surcharges on earned-fee invoices. Before enabling surcharging, check your state bar's ethics opinions and your processor's network compliance — and disclose the practice in your engagement letter.

🔧 The Compliant Payment Workflow, Step by Step

Putting it together, a compliant electronic payments setup looks like this: First, choose a legal-specific processor that supports dual trust/operating routing and gross deposits with separately debited fees. Second, configure payment links and your client portal so each request is tagged to a destination account and a matter. Third, post every payment to the client's ledger and the GL automatically — manual re-keying is where errors breed. Fourth, fold card and ACH activity into your monthly three-way reconciliation so processor-level discrepancies surface within 30 days. Finally, document all of it in your trust accounting manual: routing rules, fee handling, chargeback procedure, surcharge policy.

🚀 The Payoff

None of these rules is a reason to avoid electronic payments — they're a reason to implement them on legal-grade rails. Firms that do see faster collections, lower days-sales-outstanding, and happier clients, with trust compliance maintained by architecture instead of vigilance.