Yes, do lawyers take credit cards? Most do. Our 2026 guide covers ethical rules for trust accounts, processing fees, and choosing a compliant payment
Law firms have been permitted to accept credit cards for decades. The harder question is whether the firm can do it without creating an ethics problem in the process.
Risk sits in two places. First, a firm that adds processing costs back to the client without checking state ethics guidance, card-brand rules, and surcharging laws can turn a routine payment policy into a billing dispute or disciplinary issue. Second, a firm that accepts advance fees or retainers by card must handle trust accounting with precision, because IOLTA deposits, chargebacks, refunds, and processor fee withdrawals can all affect client funds if the payment setup is wrong.
Those are not edge cases for small firms. They are the points where payment operations, professional responsibility, and cash management meet. For solos and firms with 2 to 50 lawyers, the payment processor is part of the firm’s financial control system, not just a checkout tool. The same is true of the surrounding law firm software that controls billing, trust accounting, and payment routing.
A firm can get the upside of card acceptance. It should do so only with a policy that separates earned fees from trust money, defines how processing fees are treated, and assigns responsibility for reconciling every transaction.
For a small firm, refusing card payments is often a working-capital decision disguised as a fee decision. The direct cost is easy to see. The indirect cost is slower collection, more staff follow-up, and a higher chance that an approved bill becomes an aged receivable.
That trade-off is measurable. According to LeanLaw’s analysis of online credit card payments for lawyers, firms that accept online credit card payments collect a higher share of billed revenue and get paid materially faster than firms that rely on checks or cash. For a managing partner, those gains affect more than billing. They influence payroll timing, case-cost recovery, and how much cash the firm has available to fund intake and operations.
The economics also change by practice area. In family law, immigration, criminal defense, estate planning, and other matters where clients often make decisions under time pressure, payment friction can reduce conversion at the point of engagement. A card option does not solve every collection problem, but it removes one avoidable barrier.
A useful way to frame the issue is this. If card acceptance shortens the gap between invoice delivery and cash receipt, the comparison is not “merchant fee versus no fee.” It is “merchant fee versus collection drag,” including staff time spent chasing payment and the financing strain created by slower cash turnover.
Broader adoption supports that view. MyCase’s lawyer statistics roundup reports that online card and digital payment acceptance is now common across U.S. law firms. That trend matters because client payment behavior has changed, but the operational implication is more important. Once clients expect to pay electronically, firms that rely on paper checks are choosing a slower collections system.
The harder financial question is not whether cards produce value. It is whether the firm can capture that value without creating avoidable risk in two places: fee handling and trust accounting. A processor that deposits every card payment into the operating account may look efficient until the first advance fee or retainer arrives. A surcharge policy may look like a clean way to recover merchant costs until state ethics guidance, card-brand restrictions, or client-relations concerns make the policy more expensive than the fee itself.
That is why software selection matters. Billing, payment links, trust routing, reconciliation, and refund controls should work as one system, not as disconnected tools that require staff to rebuild the audit trail by hand. Firms comparing platforms can use law firm software for billing, trust accounting, and payment routing as a starting point, but the key screen is narrower than general feature depth. The system needs to support separate handling for earned fees and unearned client funds before any money moves.
For managing partners, the conclusion is practical. Card acceptance usually improves collections. The firms that benefit most are not the ones that only turn on online payments. They are the ones that configure payment operations so that merchant fees, surcharges, retainers, and trust deposits are handled correctly from the start.
The highest-risk payment mistake for a small firm is simple to describe and expensive to fix. Client funds that are not yet earned must go into trust, even when the client pays by credit card. Earned fees go to operating. That separation is the rule that matters.
The practical distinction is custody. One account holds the firm’s money. The other holds money the firm is safeguarding until it has a right to transfer those funds. If a retainer is deposited to operating first and sorted out later, the compliance failure has already occurred.
Bar guidance leaves little room for improvisation. DC Bar Ethics Opinion 348 explains that advance fees and expenses paid by credit card must be handled in a way that preserves the required separation between lawyer funds and client funds. The operational consequence is clear. Firms that accept security retainers by card need payment routing that can send those funds directly to trust rather than through operating.
That requirement matters most in practices that collect money before the work is performed. Family law, criminal defense, immigration, and many estate planning matters fit that pattern. A flat fee does not solve the trust issue by itself. The answer depends on whether the fee is earned on receipt under the engagement terms and the firm’s governing rules.
For firms reviewing the basics, Caseledge’s guide to client trust account rules and workflows explains how these duties affect day-to-day bookkeeping and payment handling.
Generic payment tools often assume every card payment is business revenue. That assumption works in retail. It fails in a law practice that accepts retainers, advance costs, or replenishments. If the processor deposits all card payments into one business account, the bookkeeper inherits a problem that should have been prevented at intake.
Processing fees create a second layer of risk. If a merchant fee is pulled from the trust deposit itself, the trust account can be short the moment the transaction settles. Refunds can create similar issues if staff return money from the wrong account or reverse a charge after the underlying funds have already been moved. These are not edge cases. They are routine payment events that become ethics problems when the system is configured without legal trust logic.
A modern payment form does not make a trust workflow compliant. The routing and fee treatment determine whether the transaction is defensible in an audit or grievance response.
A workable setup usually starts with two separate destination accounts and matter-level controls that identify whether the client is paying an invoice, funding a retainer, or replenishing trust. The payment tool, accounting workflow, and reconciliation process all need to reflect that distinction.
Small firms should also test one operational question before turning on card payments for retainers. When a client pays $5,000 into trust by card, does the trust account receive the full $5,000, and can the firm document exactly how any merchant fee is handled without reducing client funds? If the answer is unclear, the processor setup is not ready.
For solo and small firms, general billing tools often stop being adequate. They may send invoices and collect cards without issue. But if they cannot preserve trust segregation, account for fees correctly, and produce a clean audit trail, they do not meet the operational standard a law firm needs.
Choosing the wrong processor can turn a routine card payment into a trust accounting problem. For a small firm, the decision is less about headline rates and more about whether the system makes the ethical workflow easy to follow under daily operating pressure.
The first test is operational. Can the payment stack distinguish among earned fees, replenishments, and advance fee deposits before the transaction posts, and can it preserve that distinction in the matter ledger? If that logic breaks down, staff will end up correcting entries after settlement, which is exactly when errors become expensive and hard to defend.
A useful comparison starts with workflow fit, not marketing labels.
| Processor type | Best fit | Main risk or advantage |
|---|---|---|
| Generic processor | Earned fees only, where the firm uses separate accounting controls outside the processor | Often lacks trust-specific routing, fee handling, and matter-level reconciliation |
| Legal-specific processor | Firms accepting retainers, trust replenishments, or mixed payment types | Better aligned with legal trust accounting and audit trail requirements |
| Embedded processor inside legal PMS | Firms that want billing, payments, and ledger activity in one system | Quality depends on how tightly payments, trust, and accounting functions are connected |
A legal-specific option often reduces failure points because payment intent, account routing, and ledger treatment are defined in one process instead of reconstructed later by staff. Firms assessing a LawPay legal payment processing profile usually focus on that issue. The practical question is whether the processor handles trust-related transactions in a way that ordinary merchant tools usually do not.
Many firms prefer to buy payments through their practice management platform. That approach can work well if the platform is already the system of record for billing, trust, and reconciliation.
Clio is a common example in this category. MyCase review and pricing analysis also belongs in the comparison set because it is cloud practice management software for solo and small law firms, and buyers often want invoicing and client payments in the same environment.
The operational risk is easy to miss. An integrated payment button can make a weak trust workflow look polished. A managing partner should ask whether the platform accepts cards, or whether it records the payment in a way that survives reconciliation review, a client dispute, or a bar audit.
The best diligence questions are narrow and concrete.
Selection filter: If a vendor cannot demonstrate a trust retainer from payment form to ledger entry without vague explanations, the firm should assume the setup will require risky manual workarounds.
A short product walk-through is useful before making that call.
For some firms, the processor decision is really an accounting decision. A platform such as CosmoLex is often evaluated because it places practice management, accounting, and payments closer together. That can reduce handoffs and duplicate entry, but only if the firm’s billing model matches the software’s trust and operating logic.
The migration issue deserves more attention than many firms give it. Teams moving from PCLaw or Time Matters often carry forward old reconciliation habits into a new payment environment. The result is a modern client-facing payment process sitting on top of legacy accounting assumptions.
That mismatch is where avoidable risk shows up. A firm may accept cards without friction and still mishandle fee treatment, refunds, or trust replenishments because the underlying ledger workflow was never redesigned.
For a managing partner, the decision standard is straightforward. Choose the stack that makes correct routing, defensible fee handling, and clean trust records the default outcome. Almost every vendor can help a firm accept cards. Far fewer reduce the chance that staff will solve exceptions in ways that create ethical exposure.
Processing cost isn’t one fee. It’s a stack of charges. According to LawPay’s guide to credit card processing fees for lawyers, the structure typically includes interchange fees, assessment fees, and processor markup, with total processing fees generally ranging from 1.5% to 3.5%.
For law firms, the practical question isn’t just what those charges are. It’s whether the firm can pass them to the client, and if so, how.
A finance or operations lead should be able to parse the charge structure at a glance.
That breakdown matters because ethical surcharge rules generally turn on the actual cost to the firm, not on a made-up convenience add-on.
Many otherwise competent firms often get sloppy in this area. Some jurisdictions prohibit surcharges entirely. Others allow them only with tight disclosure and consent rules. LawPay’s state-focused summary notes that credit card surcharges are legal in most U.S. states for law firms but are capped and require explicit disclosure; a general federal rule prohibits surcharges from exceeding 3%, while Colorado imposes a stricter 2% cap. Surcharges are permitted only for credit card transactions, not for signature debit or prepaid cards, as summarized in LawPay’s article on credit card surcharge rules.
The finer point is that legality doesn’t equal operational simplicity. A firm can be in a state that permits surcharging and still implement it badly through vague invoice language, poor engagement terms, or software that doesn’t itemize the charge correctly.
The Illinois angle shows why detail matters. The ISBA has addressed the issue with attention to disclosure and Rule 1.5 concerns in Illinois State Bar Association Opinion 14-01. The operational lesson is that billing language and system configuration have to match.
Firms shouldn’t treat surcharging as a generic switch inside billing software. It’s a jurisdiction-specific billing policy that needs legal review, invoice discipline, and clean client communication.
Many firms decide the safest policy is to absorb card fees as overhead. That isn’t always required, but it is often simpler. When a firm does surcharge, the guardrails should be explicit.
For firms comparing accounting stacks, Caseledge’s review of law firm accounting software is useful because surcharge compliance is partly a software question. If the system can’t create a separate, transparent line item when local rules allow one, the policy may be harder to administer than it’s worth.
The easiest way to answer whether lawyers take credit cards is to watch what happens to the money after the client clicks Pay. In a well-configured system, the client’s experience feels simple. The firm’s ledger logic does the hard part in the background.
Consider a small estate planning firm billing an earned flat fee for a completed package. The attorney issues an invoice through the practice management system. The client receives a payment link through the portal, reviews the invoice, and submits a card payment.
Because the fee is already earned, the payment is routed to the operating account. The billing record marks the invoice paid, and the accounting side associates the receipt with that matter. No trust entry is involved because the funds weren’t entrusted for future work.
A platform used this way needs to keep the invoice, payment confirmation, and matter ledger aligned. That’s one reason firms evaluating software often compare billing flow carefully through resources such as Caseledge’s guide to law firm billing software.
Now consider a family law or criminal defense matter. The client signs the engagement agreement and is asked to fund an initial retainer by card. The payment screen should make clear that the funds are an advance deposit to be held in trust until earned under the fee agreement.
The critical distinction is backend routing. The payment should go directly into the IOLTA or other trust account setup, not into operating. The trust ledger should reflect the deposit under that specific matter. As work is completed and billed, the firm then transfers earned amounts out of trust according to its jurisdiction’s rules and internal reconciliation process.
Sample client-facing language: “Retainer payments will be deposited to the firm’s client trust account and applied to future earned fees and approved expenses as permitted by the engagement agreement and applicable rules.”
For solo and small firms, the software doesn’t need to do everything. It does need to reduce the chance of staff making the wrong account choice under time pressure.
A practical payment workflow usually has these elements:
In litigation and personal injury practices, the same discipline matters even when trust deposits are less frequent than in family law or immigration. Once a firm offers cards broadly, staff members will use the same payment rails across many matter types. The workflow has to be right by default.
The firm should have a written procedure before taking the first retainer by card. The risk isn’t only merchant loss. It’s the possibility that a reversal touches money being held for a client matter. Missouri ethics guidance warns that using a credit card to access advance client funds for attorney benefit may violate trust account rules under Rule 4-1.15(a)(1) if the advance is for expenses, as discussed through DC Bar Ethics Opinion 348. In practice, the operations team should confirm how the processor handles reversals, document the response path, and make sure firm funds, not unrelated client funds, absorb any dispute-driven movement where required.
Yes. Using a legal-specific processor can reduce the firm’s direct handling of card data, but it doesn’t eliminate the need for basic payment security discipline. The safest operating model is to let the processor or the practice management platform host the payment collection experience. Staff should avoid storing card details outside approved systems and should route all payment collection through the designated portal or processor workflow.
The agreement should identify which payment methods the firm accepts, whether card payments can be used for earned invoices, whether advance deposits will be placed in trust, and whether any processing charge applies where permitted by law. If the firm imposes a surcharge, the language should state that the amount won’t exceed the firm’s actual processing cost and that the charge applies only where lawful. This is one area where short, plain drafting is better than broad language that the billing staff can’t implement consistently.
Sometimes, but only if the processor and the surrounding software support both operating and trust workflows cleanly. A one-size-fits-all payment tool is attractive for administration. It becomes risky if it forces the staff to solve trust routing manually every time a retainer comes in.
Caseledge is an independent trade publication for legal software buyers, and it can help firms compare practice management systems, billing tools, and payment-related workflows before committing to a vendor. Managing partners evaluating card acceptance, trust accounting support, or migration from older platforms can use caseledge to review current product coverage, side-by-side comparisons, and documented procurement analysis.