LawPay is a payments platform built for law firms. It lets firms accept credit cards and ACH online, request retainers, keep trust and operating funds strictly separated, and reconcile deposits—without running a

LawPay is a legal payments and billing solution from AffiniPay designed to meet bar association rules and trust accounting requirements. It powers online card and eCheck/ACH acceptance, payment pages/links, recurring schedules and payment plans, client-friendly financing (ClientCredit), and detailed reporting with separate trust and operating accounts.
Core product areas include:
Common data entities:
Legal teams and finance ops rely on LawPay every day, but turning portal workflows into API-driven automations that respect trust accounting rules and matter-centric organization can be difficult:
Supergood reverse-engineers authenticated browser flows and network traffic to deliver a resilient REST layer for your LawPay tenant.
Book a 30-minute session to confirm your modules, licensing, and authentication model.
We deliver a hardened LawPay adapter tailored to your workflows and entitlements.
Go live with continuous monitoring and automatic adjustments as LawPay evolves.
- Generate matter-tagged payment links and embed them in iManage workspaces or engagement letters - Automatically store paid receipts, ACH authorization PDFs, and transfer memos into the correct iManage folders - Sync payment status back to iManage profile fields (e.g., Retainer Balance, Last Payment Date)
- Request retainers against trust with designated matter numbers - Initiate compliant trust-to-operating transfers when invoices are approved, with itemized references - Preserve a complete authorization and audit trail per matter
- Pull daily payouts and tie them to underlying transactions and fees - Reconcile by matter, client, and bank account; export to accounting (e.g., QuickBooks) - Detect ACH returns and disputes and route them to your case/ticketing systems
- Offer card/ACH/ClientCredit options via branded links - Schedule payment plans and send reminders; notify your app on success/failure - Trigger retainer replenishment when balances fall below thresholds
Authentication
Username/password with MFA (SMS, email, TOTP); supports service accounts or customer-managed credentials
Response format
JSON with consistent resource schemas and pagination across modules
Rate limits
Tuned for billing operations and reconciliation workloads while honoring entitlements and usage controls
Session management
Automatic reauth and cookie/session rotation with health checks
Data freshness
Near real-time retrieval of payment requests, transactions, transfers, and payouts; settlement/returns reflect network timelines
Security
Encrypted transport, scoped tokens, and audit logging; respects LawPay/firm role permissions and trust accounting constraints
Webhooks
Optional delivery for events (payment.succeeded, ach.returned, refund.processed, trust.transfer.completed, payout.paid)
Latency
Sub-second responses for list/detail queries under normal load; settlement/return availability depends on card/ACH networks
Throughput
Designed for bulk payment link generation and high-volume reconciliation
Reliability
Retry logic, backoff, and idempotency keys minimize duplicates and support at-least-once processing
Adaptation
Continuous monitoring for UI/API changes with rapid adapter updates
Supergood supports workflows commonly used for legal billing and trust accounting, including Payment Requests (links, email delivery), Transactions (card/ACH, refunds, returns), Trust Transfers (IOLTA-compliant movements), and Payouts/Reporting (deposits, fees, net amounts), subject to your licensing and entitlements. Scope is finalized during assessment.
We support username/password + MFA (SMS, email, TOTP). Sessions are refreshed automatically with secure challenge handling and monitoring for expiry.
Yes. We can deliver webhooks for settlement, ACH returns (with NACHA codes), disputes, refunds, and trust transfer completion—or you can poll endpoints with incremental filters.
We separate trust and operating contexts, require explicit invoice/matter references for transfers, capture authorization details, and maintain immutable audit records. We also ensure request parameters align with allowed methods and firm policies.
Yes. Include iManage metadata (workspace/folder) when creating requests or transfers, and we will attach generated receipts/authorizations and post them to the specified iManage location with consistent filenames and profile fields.