LawPay API
LawPay documents a payments API covering payments, payment links, trust transfers, and payout reconciliation. Live and test credentials are self-serve from the in-app Developers area once you hold a merchant account. SDKs are limited and rate-limit docs are thin.
Frequently asked questions
LawPay scores C on Supergood's API Report Card. LawPay documents a payments API covering payments, payment links, trust transfers, and payout reconciliation. Live and test credentials are self-serve from the in-app Developers area once you hold a merchant account. SDKs are limited and rate-limit docs are thin.
LawPay has an official API, but teams routinely hit its limits: gated access, partial coverage, or paid tiers. Most end up supplementing it with exports or an unofficial API layer like Supergood. Site terms may apply to any integration approach, and how they apply is a determination each team makes for itself.
LawPay (by AffiniPay) is a payments platform built for law firms, enabling credit-card and ACH payments, trust/IOLTA-compliant payment handling, payment links, online payments, and payout reconciliation. It is the dominant legal-industry payment processor.
Financial Services (Legal Payments), Typically for solo, small, and mid-size law firms accepting client payments in compliance with trust-accounting (IOLTA) rules. Firms send payment links/invoices, accept card and ACH payments into operating or trust accounts with compliant fund separation, reconcile payouts, and sync transactions into practice-management/accounting tools (Clio, MyCase, QuickBooks).
The category-leading legal payments processor, used by tens of thousands of firms and ABA/bar-association endorsed; strong Capterra/Gartner footprint. Parent AffiniPay also owns MyCase and CPACharge.
Yes, Payment transactions, trust/IOLTA flows, and payout data. But this is reachable through a self-serve, documented payments API.
Founded ~2010 (AffiniPay accredited since 2010); modern cloud payments platform, actively developed with a current developer area and webhooks.
Payments do not always auto-sync to practice-management tools; manual recording needed. Limited published rate-limit/changelog/status-page documentation. Full sourced list under Sources below.
Common alternatives include Clio Payments, Gravity Legal, Stripe, Confido Legal, Headnote. Graded alternatives appear under "More from the report card" below.
Supergood's grades measure one thing: can a customer's engineering team get their own data out programmatically? Supergood checks six things (whether a real API exists, how access is gated, data coverage, auth quality, docs and developer experience, and stability) and rolls them into a letter grade. Supergood re-verifies grades, and they only move on evidence.
Yes, via a managed API layer. Supergood builds REST APIs and MCP servers for authenticated enterprise web apps, so AI agents and internal tools can read and write data programmatically. Site terms may apply to any integration approach, and how they apply is a determination each team makes for itself.
Not that we could find. As of August 2026 there is no official LawPay MCP server in any public registry, and no maintained community server we're aware of. We re-verify this periodically — report an inaccuracy below if we missed one.
Not natively. LawPay doesn't publish an MCP server, so MCP clients like Claude, Cursor, and Codex have nothing to connect to out of the box. If that changes, this page will reflect it.