What we do
Tools
Industries
Department
How we workLet's talk →
Home/LawPay
LawPay

LawPay API Access for Law Firms and the Software Vendors That Serve Them

Your intake form takes a retainer, and the money has to land in trust and show up on the right matter in a case system LawPay doesn't connect to. Or you build software for law firms, and your customers keep asking for LawPay. Either way you need the LawPay API, which now sits on 8am's developer site: AffiniPay renamed itself 8am, and LawPay became 8am LawPay.

Where LawPay stops

The payment clears, but recording it on the right matter and the right ledger still falls to staff.

Stuck on LawPay? Let's solve it →
The LawPay API, briefly

Docs: developers.8am.com, under the 8am Payment Gateway. It covers charges, refunds, voids, recurring charges, surcharges and events.

A firm connecting its own systems uses its own API keys, found on the Developers page in LawPay. Secret keys stay on a server, never in browser code, and test and live keys are separate.

Your name (top right) Developers

A software vendor connects firms through OAuth 2.0 and LawPay's Connect button, and has to show 8am a recorded demo of the integration before it can take live payments.

Card details go through hosted fields, which return a token, so your system never holds card numbers. Saved payment tokens are the only payment data you keep.

LawPay API mistakes that touch client money

Most of them come down to which account a charge hits, and to events that arrive out of order.

A retainer charged to the operating account

How you'll know: The charge succeeds, the money is in operating, and the matter's trust ledger shows nothing.

Fix: The gateway's merchant record marks each account as trust or operating. Choose the account in code from what the payment is for, a retainer or an earned fee, never from a default, and test both paths in test mode. Fees and trust deposits have rules of their own, so confirm with your state bar's rules.

Webhooks treated as the record of what happened

How you'll know: Your system posts a payment twice, or misses one after it was down for an hour.

Fix: 8am's events aren't batched or sequenced, and anyone can post to a webhook URL. Treat each event as a cue to fetch the transaction from the API, ignore repeats, and poll the events list on a schedule for anything missed. 8am's own docs name polling as the preferred option.

Refunds made on one side only

How you'll know: A refund issued in LawPay never reaches the practice management system, so the invoice still shows paid.

Fix: Not every native integration carries refunds back. Smokeball's help center says refunds issued in LawPay aren't sent to Smokeball, for one; see Smokeball integrations. Read refund events from LawPay and post or flag them where the case system's API allows.

Card numbers reaching your own server

How you'll know: A custom payment form posts the card number straight to your backend.

Fix: Use hosted fields, so the browser swaps card details for a token before anything reaches you. 8am's partner rules allow storing saved payment tokens only, unless you're PCI Level 1 certified.

Native integration, firm keys or a partner app: which LawPay route fits

If you are Use Worth knowing
A firm on a practice system that already integrates with LawPay, such as MyCase, Smokeball, Tabs3 or Aderant Expert The built-in integration Check what it carries back. Payments onto invoices, usually. Refunds and reversals, not always.
A firm taking payments in its own intake form, client portal or in-house app Your own API keys Your code picks trust or operating on every charge, so write and test that rule before anything else.
A legal software company adding LawPay for its customers A partner OAuth application 8am reviews a recorded demo of the whole flow, including connect, disconnect, charge, refund and void, before you can go live.
A firm that only wants payment links on its invoices LawPay's own invoicing, or your practice system's 8am has added invoicing, time tracking and trust balance reporting to LawPay itself, so check your plan before paying for a build.

A general practice firm where retainers waited on a person

Small general practice firm · LawPay for card payments

Before

A retainer arrived through LawPay, and a staff member recorded it against the matter, confirmed it went to trust and told the attorney, sometimes a day late.

After

Each payment now goes to trust or operating by the firm's rules, is recorded on the matter as it clears and gets a receipt out to the client.

The attorney sees the payment the same day it clears.

LawPay API and payment questions

What is LawPay, and who makes it now?

A payment processor for law firms, built to take card and eCheck payments into trust or operating accounts. It's made by 8am, the company formerly called AffiniPay, which also makes MyCase, and it's now branded 8am LawPay.

Does LawPay work with case management software?

Yes. LawPay connects natively with many practice management systems, including MyCase, Smokeball, Tabs3 and Aderant Expert. Where your system isn't one of them, or the built-in link skips refunds or trust deposits, n-frames builds the connection on the LawPay API. For one native pairing in detail, see MyCase and LawPay.

Does LawPay have a public API?

Its documentation is public at developers.8am.com. A firm uses its own keys from the Developers page in LawPay, which needs the Administrator or Developer role. A software vendor uses partner OAuth and goes through 8am's demo review before taking live payments.

Can the LawPay API tell our system when a client pays?

Yes. Under Developers, a Webhooks section takes one or more URLs, with separate ones for test and live mode, and 8am posts transaction events to them. Because those events can repeat or arrive out of order, pair them with a scheduled read of the events list.

Who builds a LawPay integration for a law firm?

For firms, n-frames writes the payment step for your own intake or portal on hosted fields, sends each charge to the right account and records it on the matter in your case system. For legal software companies, we build the partner connection through to 8am's review. Trust ledgers themselves are covered on our trust accounting software page.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.