JTJuris Tflow Direct
Guides › Legal Operations

Seven Online Payment Mistakes Law Firms Make, From Trust Commingling to Card Fees

Card payments into a client account usually go wrong in the same few ways: fees taken from trust money, chargebacks pulled from the wrong account, and payouts nobody can reconcile. Here's the fix for each.

Juris Tflow Direct editorial team · November 2026 · 8 min read

Why card payments break client-account rules

Clients expect to pay online. Your decision is how the money moves, so that client funds never cover the firm's costs. Most problems with law firm payment processing start the same way: someone sets up a generic merchant account the way a retail shop would. Everything lands in one deposit account, fees come out of each settlement, and refunds and disputes are pulled from wherever the money happened to land.

That works for a café. A firm holding client money is in a different position. The governing rules might be the SRA Accounts Rules in England and Wales, ABA Model Rule 1.15 as each US state has adopted it, provincial law society rules in Canada, state and territory trust-accounting legislation in Australia, or the Legal Practice Act and Legal Practice Council rules in South Africa. Under any of them, a retail-style setup can breach the rules on its first transaction. Each mistake below comes with a configuration or vendor fix. Details vary by jurisdiction and change over time, so check your regulator's current guidance or ask a qualified compliance adviser.

Advertisement

Mistake: letting processing fees come out of client money

Here's a hypothetical. A client pays a $5,000 advance by card. The processor takes 2.9% and settles $4,855 into the client account. The client's ledger shows $5,000 held, but the bank shows $145 less. That gap is other clients' money paying the firm's overhead, and most regulators treat it as a shortfall or a misuse of client funds.

What to do instead: pick a processor that settles the gross amount into the client account and takes every fee from the operating account, usually in one monthly debit. If a fee does reach the trust account, replace it from firm money straight away and record it. The SRA expects breaches to be put right promptly. Many US states let a firm keep a small amount of its own money in trust to cover bank charges, so check your state's rule. Red flag: a sales rep who can't tell you in writing which account fees are debited from.

Mistake: routing chargebacks and refunds through the trust account

Disputes often land weeks after the money has been spent on disbursements or moved out as earned fees. If the processor reverses the payment from the client account, it's taking money that belongs to other clients. A rolling reserve has the same effect, because the processor holds back part of each trust deposit.

What to do instead: make the operating account the debit account for chargebacks, reversals, dispute fees and reserves. Most legal-specific platforms are built around this split. General processors can sometimes be configured the same way, but you'll often need a separate merchant account for each bank account. Refunds of unearned funds are different. They should come out of the right client ledger through your accounting system, not through a processor clawback.

Mistake: taking earned fees and client funds through one payment route

Card payments into a client account make sense for advances, disbursement funds and settlement money. Payment of a bill for work already done generally belongs in the office account. If one payment link feeds both, you're either commingling or moving money by hand every day.

What to do instead: set up separate payment routes for trust and operating money, and let the invoice type decide where each payment goes, not the payer. If a client sends a mixed payment, handle it as your rules require. Under the SRA, that usually means paying it into the client account and moving the firm's share out promptly. Many US jurisdictions take a similar approach: mixed funds go into trust and the earned portion comes out once it's clear.

Mistake: accepting net, batched payouts you can't reconcile

Many processors bundle a day's payments into one net deposit. Say $7,320 arrives, covering three clients minus fees. Your bookkeeper now has to work out which matters it belongs to. Regulators generally require regular client-account reconciliations, often monthly, and the SRA sets its own minimum frequency. With batched net deposits, reconciliation becomes guesswork.

What to do instead: ask for gross deposits, either per transaction or per batch, with a transaction reference that shows on the bank statement. Then connect the payment software to your practice management or accounting system so each payment posts to the right matter ledger automatically. Your three-way reconciliation should match the bank balance, the client ledgers and the cash book. It shouldn't depend on processor reports that someone has to export.

Fraudsters target the payment email. They hijack the thread and send "updated" bank details or a fake payment link. Conveyancing and property teams are frequent targets in many markets, but every practice area is exposed. Taking card numbers over the phone and writing them down causes a separate problem: it pulls the firm into broader PCI DSS scope.

  • Take payments through a client payment portal that requires a login, or through invoice-specific links that expire and come from the platform's own domain.
  • Use hosted payment fields so card data never touches your systems. That usually keeps you within the simplest PCI DSS self-assessment.
  • Tell clients in the engagement letter that you'll never change bank details by email. Confirm any change by calling a number you already have on file.
  • Turn on multi-factor authentication for anyone who can issue refunds or change payout accounts.

Mistake: passing card fees to clients without checking surcharge rules

Passing on a 3% surcharge is legal in some places and banned in others. The UK and the EU ban surcharges on consumer cards. Australia has allowed surcharges limited to the cost of acceptance, but its regulator has been moving to restrict them, so check the current position. In the US, many states allow credit-card surcharges but not debit-card ones, subject to card-network caps and notice rules, and some state bar opinions add that the fee must be reasonable and disclosed in advance. Canada permits credit-card surcharges under card-network conditions, but Quebec's consumer rules restrict them.

What to do instead: set out any fee in the engagement letter, never take it from trust money, and offer a cheaper option such as ACH, EFT, pay-by-bank or open banking. For large advances, a bank-to-bank payment often suits both sides anyway.

Mistake: choosing a processor on headline rate instead of trust fit

A rate that's 0.3 points lower is worthless if the processor can't keep trust and operating money apart. Before you compare prices, confirm that the vendor:

  • offers separate trust and operating routes;
  • takes all fees and chargebacks from the operating account;
  • deposits gross amounts;
  • integrates with your practice management system;
  • is available in your country;
  • has fair reserve and termination terms and spells out PCI responsibilities.

Legal-specific options are most mature in North America. Coverage in the UK, Australia and South Africa is thinner, so you may need a general processor with a carefully structured account setup.

Cost itemTypical 2026 range (indicative)
Credit cards, US and Canada2.5–3.5% + $0.20–0.30 per transaction
Consumer cards, UK and EU (capped interchange)1.2–2.5% blended
ACH / eCheck / EFT$0.50–3 flat, or 0.5–1%
Pay-by-bank / open banking0.3–1%, or a flat fee per payment
Platform subscription$0–60 per user per month, often bundled

These are typical 2026 market ranges. They vary by contract, volume and country, so get written quotes from each vendor.

How client-account rules compare by regulator

RegulatorFees from client moneyReconciliationPractical note
SRA (England and Wales)Not permitted; replace any shortfall promptlyRegular, with a fixed minimum frequencyThe firm's compliance officer for finance and administration (COFA) is responsible for breaches
US state barsGenerally prohibited; limited firm money allowed for bank charges in many statesMonthly or quarterly, varies by stateEthics opinions on card fees differ by state
Canadian law societiesGenerally prohibitedTypically monthlyRules are set by each province
Australian law societiesGenerally prohibitedRegular, often monthlyExternal trust-account examination requirements apply
South Africa LPCGenerally prohibitedRegular, often monthlyFidelity Fund certificate depends on compliance

Treat the table as orientation only and confirm each point with your regulator.

Decision rule: before you go live, run a small test payment into the client account, refund it and let a fee post. Then check the bank statements. If anything other than the gross deposit touched the client account, fix the setup or change vendor before you take a real client payment.

Quick answers

Can a law firm accept card payments into a client account at all?

In most jurisdictions, yes, as long as client money isn't used to pay fees or chargebacks and every payment is recorded against the right client. Some regulators and state bars have specific guidance on card payments. Check yours before you set up the account.

Who pays a chargeback if the work is already done?

The firm takes the reversal from its operating account, then pursues the client for the unpaid fee under the engagement terms. A chargeback should never be met from money held for other clients. A processor that debits disputes from the operating account handles this automatically.

Can we pass card processing fees on to clients?

It depends on your country and, in the US, your state. The UK and the EU ban surcharges on consumer cards. Many US states, Canada and Australia allow them with conditions, and those conditions change. Wherever surcharges are allowed, disclose them in advance and never take them from trust money.

Is a general processor like Stripe or Square acceptable for legal work?

It can be, if you can set it up with separate merchant accounts and have all fees and disputes debited from the operating account. In practice that takes more setup and more vigilance than legal-specific payment software. Outside North America, a general processor may be the only realistic option.

What should we do if fees have already been taken from client money?

Replace the shortfall from firm money right away, record the correction on the affected client ledgers and fix the processor setup. Ask your compliance officer or a regulatory adviser whether the breach must be reported. Repeated or unremedied shortfalls are treated more seriously.

Written by the Juris Tflow Direct editorial team. Prices, features and rules change often - confirm details with the vendor or a licensed professional before you decide.