Payment Processing for Law Firms in San Francisco

Law firms payment processing in San Francisco has a constraint that no other industry shares: money that belongs to a client cannot have your processing fees taken out of it. That single rule, enforced through the State Bar's trust accounting requirements, shapes every decision from which processor you choose to how you handle a chargeback.

The trust account problem, plainly

When a client pays a retainer by card, the funds go into your client trust account (IOLTA for pooled small or short-term funds). The card processor's fees, however, must come out of your operating account. If a processor debits fees from the trust account, you have an ethics problem the moment it happens. Similarly, a chargeback that pulls funds from the trust account can leave another client's money short.

The processor setup has to do three things: deposit trust payments to the trust account, debit all fees from the operating account, and handle chargebacks against operating funds first. Not every processor can split this correctly. Ask for it in writing and test it with a small transaction before you rely on it. Confirm your configuration with the State Bar's guidance and your ethics counsel.

San Francisco's legal market

The city's firms range from the large offices around Embarcadero Center and the Financial District that bill corporate clients on net terms, to the immigration, family, and tenant-rights practices in the Mission and the Tenderloin, to the tech-focused boutiques South of Market that work with startups on flat fees and equity, to the solo practitioners and small firms in the Richmond, Sunset, and Civic Center corridors. Their payment patterns differ sharply. Corporate clients want invoices on ACH or wire. Consumer clients want to pay a retainer by card, online, tonight.

Retainers, flat fees, and evergreen billing

Flat-fee and evergreen retainer arrangements are increasingly common for consumer practices. If a client agrees to automatic replenishment of a retainer, that is recurring billing, and California's Automatic Renewal Law and the general consent expectations apply to consumer-facing recurring charges. Your engagement letter should disclose the replenishment trigger, the amount, and how to stop it. A recurring billing tool with pre-charge notices creates the consent record you will need if a client later disputes.

Chargebacks and what they mean for a firm

A client who fires the firm and disputes the retainer creates two problems. The card issuer may pull the funds regardless of your engagement letter, and if those funds were in trust and already earned and transferred, the trust account may end up short. Your defense is documentation: the signed engagement letter, the billing statements, the receipt for each charge, and a clear descriptor that matches your firm's name. Keep your ratio far below the network thresholds around 0.9%-1%. A firm rarely gets there, but a high-volume consumer practice can if engagement terms are sloppy.

Large invoices belong on ACH

Corporate clients paying a $60,000 invoice should not do it on a card, and most will not. ACH carries a flat fee, settles in 1-3 business days, and pairs with invoicing and payment links so a client's AP department can pay from the emailed invoice. For the consumer side, cards settle in 1-2 business days. Some SF firms serving tech and international clients also accept stablecoin payments, settled instantly to the firm's wallet; whether that fits your client base and your trust accounting is a question for your ethics counsel before your processor.

Client data and confidentiality

Law firms hold privileged information, and payment data should never touch the same systems. Use hosted fields so card numbers never pass through your website or practice management software, and tokenization for cards on file. This reduces PCI scope, supports CCPA/CPRA obligations, and keeps a payment breach from becoming a confidentiality breach.

Reconciliation and the three-way trust reconciliation

California requires regular reconciliation of trust accounts. Processor reporting that clearly shows which deposits went to trust versus operating, and which fees were debited from operating, makes that reconciliation manageable. If your processor pushes transaction data into QuickBooks (one-way, from the processor into your accounting file), make sure the trust and operating accounts are mapped separately before the first sync.

Questions to ask a processor

• Can fees be debited exclusively from the operating account, and is that configured by default or on request?
• How are chargebacks handled against trust deposits?
• Does reporting distinguish trust and operating transactions?
• Is there any reserve, and against which account would it be held?

A processor that cannot answer those four clearly is not set up for a law firm, regardless of the rate. In San Francisco, where the Bar's trust rules are actively enforced, the setup matters more than the price.