When a client pays an invoice through MyCase's online payment link, the transaction runs through LawPay, not a generic card processor. That matters because LawPay was built specifically to solve a problem generic processors create for law firms: a card network's processing fee can't legally come straight out of a trust deposit without creating a commingling problem. LawPay routes the fee around the trust balance instead of through it.
MyCase and LawPay are both AffiniPay products, so the integration between them is native, not a third-party add-on bolted on afterward. A client pays through MyCase's portal or an emailed invoice link, LawPay processes the card or bank transfer, and the payment posts back into the matter in MyCase, split correctly between the trust and operating sides when the invoice calls for both.
We don't sell, set up, or process payments ourselves. What we build sits after the payment lands: getting that LawPay transaction data reconciled correctly against the firm's broader accounting and trust records, which is the part that still takes a person's attention even with the native split working as designed.
The trust/operating split happens correctly inside MyCase and LawPay. Where firms still lose time is afterward: matching each LawPay settlement against the right invoice and matter when a batch deposit hits the bank a day or two later, especially once refunds, declined payments, or partial payments are in the mix. A firm running high payment volume ends up with a settlement batch that doesn't map one-to-one to the invoices it covers, and someone has to reconstruct that mapping by hand to close the books cleanly.
A LawPay settlement deposit gets matched automatically against the MyCase invoices it covers, flagging the rare mismatch, a refund, a partial payment, a declined card retried later, instead of a bookkeeper tracing a lump-sum deposit back through a stack of invoices.
A client payment flagged as a trust deposit in MyCase gets checked against the matter's trust ledger the same day, not whenever the next reconciliation cycle happens to catch it.
Tell us where LawPay settlements and MyCase invoices stop lining up cleanly. We'll scope what's worth automating there.
Tell us how payments flow from a client's card to your firm's books right now, and we'll look at where the manual matching can go away. If LawPay reconciliation turns out to be fine and the real time sink is somewhere else, that's useful to know too, the same automation applies to any system generating data your firm has to act on.
Let's talk →LawPay was built specifically for law firms to solve a compliance problem generic processors create: deducting a card network's fee straight out of a trust deposit counts as commingling in most states. LawPay routes the processing fee separately so a trust deposit stays intact.
Yes, MyCase and LawPay handle the split between trust and operating funds as part of the native integration, posting each portion to the correct account rather than requiring two separate payments.
Yes, LawPay's processing fees are separate from MyCase's own subscription cost. Check LawPay's current rate schedule directly, since processing fees vary by payment type and change periodically.
MyCase's built-in online payment feature runs on LawPay specifically; a firm that wants to keep taking card payments without it would need to handle that separately from MyCase, outside the native online-payment workflow.