Salesforce · 8am LawPay · Legal Payments

LawPay Salesforce Integration: How Law Firms Automate Legal Payments

LawPay takes the payment. Salesforce runs the matter. The integration decides whether the two ever agree. Here is what LawPay actually offers Salesforce firms, the three ways to connect it, how a custom build works, and how to keep trust money where the rules say it belongs.

SALESFORCE MATTER Matter Invoice Balance PAYMENT REQUEST LAWPAY PAYMENT PAGE Pay by card or eCheck TRUST / IOLTA Unearned funds no fees taken here OPERATING Earned fees processing fees debited PAYMENT EVENT → SALESFORCE Cash receipt on the matter · fee recorded

Key Takeaways

  • LawPay, now branded 8am LawPay, is a payment platform built for lawyers. It separates trust and operating funds and never takes processing fees from the trust account.
  • There is no native LawPay app for Salesforce. LawPay's integrations list includes Litify, which runs on Salesforce, but not Salesforce itself.
  • Firms on Salesforce therefore connect LawPay in one of three ways: Litify's built-in integration, a custom integration on the 8am Payment Platform API, or a no-code tool such as Zapier.
  • A good custom integration does four things: it sends payment requests from the matter, keeps card data out of Salesforce, writes each confirmed payment back to the right matter, and records the fee separately.
  • The payment platform keeps trust money compliant at the bank. Your Salesforce design has to keep it compliant in the books.

What is a LawPay Salesforce integration? It is a connection between 8am LawPay, the legal payment processor, and the Salesforce org where a law firm manages clients, matters and invoices. Clients pay through LawPay by card, eCheck or ACH. Each confirmed payment is then recorded on the right Salesforce matter, with trust and operating money kept apart, so nobody re-keys transactions or reconciles them by hand at month end.

We first published this article in 2025. This version replaces the old claims, which could not be traced to a source, with LawPay's, 8am's and Salesforce's current documentation. It covers the 2025 rebrand from AffiniPay to 8am, explains that there is no native connector, and compares the three real ways to connect. It also adds the trust accounting rules that shape the design and a published example from our own work. It is written for managing partners, operations and finance leaders at growing and mid-market law firms that run on Salesforce, and for the admins and developers who will build the connection.

Section 01 · Short Answer

Does LawPay Integrate with Salesforce?

Not out of the box. LawPay does not publish a Salesforce app, and Salesforce is not on its list of integrations. Firms that use Litify, a legal platform built on Salesforce, can use the LawPay integration Litify and LawPay launched in 2022. Every other Salesforce firm connects through the 8am Payment Platform API, with a custom build, or through a no-code connector such as Zapier.

That matters because the old promise of a "seamless" plug-in sets the wrong expectation. The payment side is ready-made. The Salesforce side, meaning which object holds the invoice, how a payment finds its matter, and where the fee goes, is a design decision your firm has to make. LawPay's own integrations directory shows what connects natively, and its Litify partner page describes the one Salesforce-based route.

LawPay takes the money

Hosted payment pages, Quick Bill links, QR codes and saved cards collect card, eCheck and ACH payments into the right bank account.

Salesforce holds the matter

Clients, matters, invoices, retainers and balances live in Salesforce, Litify, CaseCloud or a custom legal data model.

The integration keeps them in step

It sends the request out, brings the confirmed payment back, matches it to the matter and records the fee, without anyone re-keying it.

Section 02 · The Platform

What Is LawPay (Now 8am LawPay), and What Does It Do?

LawPay is an online payment platform designed for lawyers, operated by the company formerly called AffiniPay. On August 19, 2025, AffiniPay renamed itself 8am, and LawPay became 8am LawPay. LawPay's brand FAQ says this was a rename, not a sale or merger: accounts, pricing, logins and features did not change. The developer platform moved to 8am's name too.

LawPay wordmark in white on a dark blue background
LawPay has traded as 8am LawPay since August 2025. Source: 8am LawPay brand FAQ.

What LawPay does for a firm, from its features page and feature guides:

CapabilityWhat it doesWhy it matters in Salesforce
Card, eCheck and ACH paymentsAccepts credit and debit cards, eChecks and ACH; the pricing page also lists Apple PayEach method reports its own statuses, so the writeback must handle all of them
Payment pagesBranded pages hosted on LawPay's PCI Level 1 compliant servers, linked from invoices, emails or your websiteThe simplest link to put on a Salesforce invoice or email template
Quick BillSends a payment request and shows whether it was opened, paid or is still pendingUseful for retainers and one-off requests sent before an invoice exists
QR codesA unique code the client scans to reach the firm's payment pageCan be printed on invoices generated from Salesforce
Scheduled paymentsOne-time or recurring charges, with Account Updater keeping stored cards currentPayment plans and retainer top-ups; Salesforce must expect a payment each cycle
Card VaultStores several payment methods per client, with a recorded authorizationSalesforce stores a reference, never the card number
Legal fee financingThe firm receives the full invoiced amount up front while the client pays in instalmentsThe matter is paid in full; the financing sits between the client and the provider
Next-day paymentsFunds available the next business day, subject to the receiving bankImproves cash flow; record the deposit date separately from the payment date
Reporting and QuickBooks OnlineDeposit, trust activity, A/R and aging reports; automatic upload to QuickBooks OnlineDecide which system owns the ledger before you sync to two places
LawPay payments features: credit and debit card payments, eCheck payments, legal fee financing, customizable payment pages, scheduled payments, QR codes, secure card storage, refunds and the legal payments network
LawPay's payment options, as shown on its features page (captured June 2025, before the 8am rename).
LawPay billing and invoicing features: time and expense tracking, and Quick Bill payment requests that show whether each request was paid, opened or remains unpaid
LawPay's own billing tools. Firms that bill from Salesforce usually keep invoicing there and use LawPay to collect.

Clients can also receive invoices by email or text message, with a Pay Now link to the payment form and no login, as LawPay's help article on emailing and texting invoices explains. Pricing changes over time, so check the current LawPay pricing page rather than relying on figures in articles.

Section 03 · Compliance

How Does LawPay Keep Trust and IOLTA Payments Compliant?

By connecting both a trust account and an operating account, and never taking fees from trust. LawPay deposits the full payment into whichever account the payment is for. It then debits all processing fees from the operating account once a month. It also refuses third-party debits from the trust account for any reason, including chargebacks. That protects the bank side of ABA Model Rule 1.15.

The rule behind this is ABA Model Rule 1.15, Safekeeping Property. Client money must be held separately from the lawyer's own. A lawyer may put their own funds in trust only to cover bank service charges. Fees and expenses paid in advance go into trust and come out only as they are earned or incurred. If a card processor took its fee from the trust deposit, the client's money would pay the firm's costs. LawPay's compliance page describes how it avoids that.

What LawPay handles. Separate trust and operating deposit accounts, full deposits with fees taken from operating, no third-party debits from trust, and PCI DSS Level 1 certification for card data. Surcharges, where allowed, cannot apply to trust account transactions, according to LawPay's surcharge guide.

What your Salesforce design must handle. Recording each payment against the right client and matter, tracking a per-client trust balance, never applying a trust deposit to an invoice before the work is earned, and logging the fee as a firm expense. A compliant processor cannot fix a ledger that books money to the wrong place.

Rules differ by state. The State Bar of Michigan's opinion RI-344 is a typical example: with two accounts, advance fees go to trust and the card company takes its fees and chargebacks from the business account. Confirm the details with your own state bar, and treat this article as an explanation of the mechanics, not legal advice.

Section 04 · Options

What Are the Ways to Connect LawPay to Salesforce?

Use Litify's LawPay integration if you run Litify. Build on the 8am Payment Platform API if you run Salesforce, CaseCloud or a custom legal model and need payments on the matter. Use Zapier only for light, low-risk notifications. Manual entry from LawPay statements is the status quo most firms are trying to leave.

RouteHow it worksBest forWatch out for
Litify + LawPayLawPay and Litify's integration, launched in 2022, adds IOLTA-compliant card, debit and eCheck payments inside the Litify environmentFirms already on LitifyCheck which Litify objects it updates and whether your accounting tool sees the result
Custom build on the 8am Payment PlatformSalesforce calls the 8am API through a Named Credential; payment events come back and Apex or Flow updates the matterSalesforce, Mitratech CaseCloud or custom legal orgs; firms using Accounting SeedNeeds a developer, test mode, monitoring and an owner after go-live
ZapierLawPay is on Zapier, so a zap can create or update a Salesforce record when a payment happensAlerts and simple logging for small volumesNo matter-matching logic, fee splitting or reconciliation; another system holding payment data
Manual entryStaff re-key LawPay transactions into Salesforce and reconcile against statementsVery low volumes onlyKeying errors, late receipts and a monthly reconciliation burden

Sources: LawPay's Litify integration announcement and its integrations directory, which also lists Zapier, QuickBooks and practice management tools outside Salesforce. LawPay also mentions a Custom Solutions team for bespoke payment integrations. If you run Litify, our Litify integration services cover connecting it to payments and accounting.

Section 05 · Architecture

How Does a Custom LawPay Salesforce Integration Work?

Four layers: a payment request leaves Salesforce, the client pays on LawPay's secure page or hosted fields, a payment event comes back, and Salesforce posts it to the matter. Card and bank details never touch Salesforce. Salesforce stores only the transaction ID, amount, status, account type and fee. That keeps the org out of PCI scope and gives every payment a clear trail.

1 SALESFORCE Payment request Matter, invoice or retainer record sends a payment link or opens a pay form 2 CLIENT PAYS Hosted page or fields Card or bank details go to 8am, which returns a short-lived payment token 3 8AM LAWPAY Charge and event Charge posts to the trust or operating account; an event records the result 4 WRITEBACK Post to the matter Poll or webhook; match the matter, create the receipt, record the fee CARD DATA STAYS WITH 8AM · SALESFORCE STORES IDS, AMOUNTS, STATUS AND FEES
The four layers of a custom LawPay and Salesforce integration. Diagram: Twopir Consulting.
Layer 1

The payment request

Start simple: a LawPay payment page or Quick Bill link on the Salesforce invoice or email template. For a branded portal or an Experience Cloud site, embed 8am's hosted fields, iframes served by 8am that replace the card and bank inputs and keep you at SAQ-A PCI scope.

Layer 2

Tokenization and the charge

The browser swaps the card or bank details for a one-time payment token, which expires after five minutes. Your server then creates the charge with that token, the amount in cents and the trust or operating account ID, authenticated with a secret key.

Layer 3

Payment events

8am records each result as an event, such as an authorized transaction. Its notifications guide recommends polling the events endpoint and also supports webhooks. A scheduled Apex job that polls is simpler to secure than a public endpoint.

Layer 4

The Salesforce writeback

Apex or a record-triggered Flow finds the client and matter, creates the payment or cash receipt record, applies it to the invoice or to the trust balance, and records the processing fee separately. If you run Accounting Seed for law firms, this is where the cash receipt and the fee entry land in the ledger.

Section 06 · Setup

How Do You Set Up a LawPay Integration with Salesforce?

Decide whether you connect as a merchant or a partner, store the credentials in a Salesforce Named Credential, collect payments through LawPay's hosted pages or fields, bring events back on a schedule, and test every payment outcome in test mode before go-live. A firm connecting its own LawPay account is a merchant and uses API keys. A software vendor connecting many firms is a partner and uses OAuth.

1. Map the money before the code.
→ List each payment type (retainer, invoice, payment plan, cost advance), which bank account it goes to, which Salesforce record it belongs to, and who owns the ledger: Salesforce, Accounting Seed or QuickBooks.
2. Choose merchant or partner access.
→ 8am's quickstart separates the two. A firm uses its API keys: a public key for creating tokens, test and live secret keys, and an account ID for each trust and operating account. A partner registers an OAuth partner application under Developers in the LawPay web app.
3. Store credentials in Salesforce, not in code.
→ Create a Named Credential for the 8am API with an External Credential. For OAuth, use the OAuth 2.0 browser flow. Grant access through a permission set, so only the integration user can call it.
4. Collect payments without touching card data.
→ Use LawPay payment pages or hosted fields. 8am's integration requirements say that only PCI Level 1 certified partners may pass card or eCheck data through their own servers; everyone else stores saved payment tokens at most.
5. Call the API from Apex or Flow.
→ Apex gives full control over charges, refunds and recurring charges. For simpler lookups, Salesforce's Flow HTTP Callout calls an external API without code, and Salesforce's own example is checking with a payment processor whether an invoice has been paid.
6. Bring events back and match the matter.
→ Poll the events endpoint on a schedule or receive webhooks. Pass the matter or invoice number in the payment reference, so Apex can match each transaction without guessing, and make the handler ignore an event it has already processed.
7. Test every outcome in test mode.
→ A test-mode secret key with a test account runs charges without reaching the card networks. Mixing test keys with live accounts fails, by design. Test successful, declined, partial and refunded payments, eCheck returns and fee edge cases.
8. Go live with monitoring and an owner.
→ Alert someone when a sync fails, report unmatched payments daily, and diary key rotation. Partners must also demonstrate the integration to 8am before taking live payments.

One housekeeping point: 8am moved its API base URL from api.affinipay.com to api.8am.com in August 2025. The old address still works, but new builds should use the new one. The 8am developer glossary defines every key and token named above.

Section 07 · Automation

What Can Law Firms Automate Once LawPay and Salesforce Are Connected?

Everything between "the client paid" and "the books are right". The biggest wins are usually the writeback (receipts and fees created automatically on the matter), retainer requests sent from intake, and live balances for partners. All of these are standard Salesforce Flow or Apex work once payment events reach the org.

Retainer request at intake

When a matter is opened or an engagement letter is signed, Flow sends the client a LawPay link for the retainer, marked for the trust account.

Invoice payment links

Every invoice email or PDF generated from Salesforce carries a payment page link or QR code with the invoice number in the reference.

Automatic cash receipts

A confirmed payment creates the receipt on the right matter and applies it to the invoice, with no re-keying.

Fee recorded separately

The processing fee becomes its own expense or disbursement record, matching how LawPay debits fees from operating.

Payment plans and top-ups

Scheduled LawPay charges match an expected payment schedule in Salesforce, and a missed one opens a follow-up task.

Live balance dashboards

Outstanding balances, trust balances per client and payment status per matter, visible to partners without a month-end report.

Payment requests can also go out by text. In another published project for a US law firm, Salesforce generates a client-specific LawPay payment link pre-filled with the invoice amount and matter reference, and Flow sends it by SMS with a sequence of reminders. The firm reports average invoice collection time falling from 14 days to under 5 days; see the SMS payment automation case study.

Section 08 · Example

What Does a LawPay Salesforce Integration Look Like in Practice?

In one published Twopir Consulting project, a US family law firm, Weinberger Law Group, replaced manual LawPay data entry with a real-time API integration. eCheck payments now sync to Salesforce as clients submit them. A Flow creates a linked cash receipt and a separate disbursement for the merchant fee, and Accounting Seed is updated in near real time instead of reconciled monthly.

LawPay eCheck payment automation

Family Law · US

Stack: Salesforce, 8am LawPay API, Apex, Flow and Accounting Seed.

Before: staff re-entered LawPay transactions into Salesforce, created cash receipts by hand by matching matter, amount and transaction ID, calculated merchant fees manually, and reconciled against LawPay statements and Accounting Seed every month.

What was built: a LawPay REST API integration, Apex that finds the right client and matter for each transaction, Flows that create the cash receipt and fee disbursement on each successful payment, testing of successful, failed and partial payments run in parallel with the old process, and monitoring with alerts for sync failures.

Results reported in the case study: 80% faster payment processing, a 75% reduction in accounting admin, 90% faster fee reconciliation, 99% transaction accuracy, and no manual data entry per payment.

Read the full LawPay and Salesforce eCheck automation case study.

Not every firm uses LawPay. The same firm also has a Salesforce client payment portal on Authorize.Net, with card and eCheck payments, automatic cash receipts per matter and recurring retainer billing; see the Authorize.Net legal payment portal case study. The design questions are the same whichever processor collects the money.

Section 09 · Pitfalls

Where Do LawPay Salesforce Integrations Usually Go Wrong?

Rarely at the payment. Usually in matching, trust handling and ownership after go-live. The processor works. Problems come from payments with no reliable matter reference, trust money posted as income, and integrations nobody watches. Check these points before launch and at every change to your billing process.

No matter reference on the payment. Without the invoice or matter number in the reference, matching falls back to client name and amount, which fails for clients with several matters.
Trust deposits applied as income. A retainer paid into trust is not earned revenue. Record it against the client's trust balance and transfer it only when the work is billed.
Card data in Salesforce. Building your own card form, or storing card numbers in fields or notes, pulls the org into PCI scope. Use payment pages or hosted fields.
Fees netted out of the payment. LawPay deposits the full amount and debits fees monthly. Booking the payment net of the fee breaks reconciliation with the bank.
Only the happy path handled. Declined, failed, partial and refunded payments each need their own handling. Reverse or adjust the receipt when a later event changes the outcome, or balances will be overstated.
Two ledgers syncing at once. LawPay can upload to QuickBooks Online while Salesforce posts to Accounting Seed. Pick one ledger of record, or every payment is counted twice.
Section 10 · Fit

When Is a Custom LawPay Salesforce Integration Worth It?

It is worth it when payment volume, trust activity or reconciliation effort is high enough that manual entry costs real staff time or creates risk. It is not worth it when Litify's integration already covers you, or when a few payments a month can be logged by hand.

Good fit. You run matters and billing in Salesforce, CaseCloud or a custom legal model. Staff re-key LawPay transactions or reconcile monthly. You hold retainers in trust and need per-client balances. You use Accounting Seed and want receipts and fees posted automatically. Partners want live collection figures.

Think twice. You are on Litify and its LawPay integration does what you need. Payment volume is low. Billing lives entirely in another practice management tool that already integrates with LawPay. Nobody will own the integration after launch.

Section 11 · Bottom Line

The Bottom Line

LawPay gives law firms a compliant way to take card, eCheck and ACH payments. Salesforce gives them the matter, the client and the invoice. A LawPay Salesforce integration joins the two, so payments land on the right matter with trust and fees handled correctly. Twopir Consulting has built this integration with LawPay's API, Salesforce Flow, Apex and Accounting Seed, and we design the money map before we write the code.

  1. 1

    Confirm your route: Litify's integration, a custom 8am API build, or Zapier for light needs.

  2. 2

    Map each payment type to a bank account, a Salesforce record and one ledger of record.

  3. 3

    Keep card data out of Salesforce with payment pages or hosted fields.

  4. 4

    Carry the matter or invoice number on every payment, and record the fee separately.

  5. 5

    Test every outcome in test mode, then monitor sync failures and unmatched payments after go-live.

Ready to Start

Stop Re-Keying LawPay Payments into Salesforce

Tell us how clients pay you today and where the money is recorded. We will map the matter matching, trust handling and accounting writeback your firm needs.

Schedule a Discovery Call

FAQ

Frequently Asked Questions

Not a native one. LawPay does not publish a Salesforce app, and Salesforce is not on LawPay's integrations list. Firms on Litify, which is built on Salesforce, can use the LawPay integration launched in 2022. Other Salesforce firms connect through the 8am Payment Platform API with a custom build, or through Zapier for simple needs.

Yes. AffiniPay, the company behind LawPay, renamed itself 8am on August 19, 2025, and LawPay became 8am LawPay. LawPay's brand FAQ says it was a rename, not a sale or merger, and that accounts, pricing, logins and features did not change. The developer API moved to api.8am.com, and the old address still works.

Yes. LawPay and Litify launched an integration in August 2022. LawPay's Litify partner page says it adds IOLTA-compliant credit card, debit card and eCheck payments that integrate into the Litify environment, so firms can send and receive payments from one system. Check which Litify records it updates before relying on it for accounting.

No. LawPay says it deposits the full payment into the trust or operating account it was made to, then debits all fees from the operating account once a month. It also refuses third-party debits from trust, including chargebacks. Your Salesforce records should match this by logging each fee separately rather than netting it from the payment.

It can be, if card data never reaches Salesforce. Use LawPay payment pages or 8am's hosted fields, which tokenize card and bank details on 8am's servers and keep you at SAQ-A scope. 8am holds PCI Level 1 certification. Salesforce then stores only transaction IDs, amounts, statuses and fees, never card numbers.

Partly. Flow's HTTP Callout action can call an external API without code once a Named Credential handles authentication, and Salesforce's own example is checking whether an invoice has been paid. Charges, refunds, event handling and matter matching are usually more reliable in Apex, with Flow creating the records afterwards.

Yes, through a custom integration. In a published Twopir Consulting case study, LawPay eCheck payments sync to Salesforce in real time and a Flow creates a linked cash receipt and a separate fee disbursement in Accounting Seed. Avoid also syncing LawPay to QuickBooks, or payments will be recorded in two ledgers.

TC

Twopir Consulting

Salesforce Partner · HubSpot Partner

Twopir Consulting helps growing and mid-market companies solve complex CRM, integration, and business system challenges. We implement, rescue, optimize, and integrate complex CRM and revenue systems, including legal payment, billing and accounting integrations for Salesforce, for 500+ clients over 12+ years.