Skip to main content

LawPay Setup

Configuring a custom LawPay OAuth app for use with Caddi

Caddi connects to LawPay through a partner OAuth application on the AffiniPay platform — now branded 8am. The application is created by 8am support rather than self-service, then configured in your LawPay account.

AffiniPay has rebranded to 8am, and the developer documentation moved from developers.affinipay.com to developers.8am.com. LawPay, CPACharge, and ClientPay all share one platform and one OAuth system, so 8am documentation applies to LawPay.

In most cases Caddi handles this. A partner OAuth application is a vendor-level artifact, not a per-firm one, and processing live payments requires 8am certification of the integration. Contact Caddi support before creating your own — you may not need to.

Before you start

You'll need:

  • A partner OAuth application on the 8am platform — request one from devsupport@8am.com, or use the values Caddi support provides

  • Owner or Admin access to your Caddi organization

Step 1: Have 8am create the partner OAuth application

  1. Email devsupport@8am.com and ask them to create a partner OAuth application for the integration.

  2. 8am provisions it — there is no self-service creation path.

If you don't see any partner OAuth applications in your account, this step hasn't happened yet.

Step 2: Configure the application in LawPay

  1. Sign in at secure.lawpay.com.

  2. Click your name in the top right and choose Developers.

  3. On the right, find My Partner Applications and open your application.

  4. Application name — this is what merchants see on the consent screen.

  5. Confirm OAuth Enabled is ticked. OAuth is mandatory for all integrations.

  6. Redirect URI — enter https://app.trycaddi.com/oauth-callback.

  7. Save, then copy the OAuth Client ID and OAuth Secret.

The Redirect URI field appears to accept a single value, so a separate application is needed for any additional environment.

Step 3: Configure LawPay in Caddi

This step must be completed by a Caddi organization owner or admin.

  1. In Caddi, open Integrations in the left sidebar, then click the Integration Setup tab at the top of the page. This tab is only visible to organization owners and admins.

  2. Find LawPay in the list and click Configure.

Enter the following values:

  • Client ID — the OAuth Client ID from your partner application

  • Client Secret — the OAuth Secret from the same application

  • Scopes — enter payments. This is the only documented LawPay scope and covers payment processing access.

Click Save Configuration. Caddi validates the credentials immediately — if something is wrong you'll see an error right away, and nothing is stored until validation passes.

Step 4: Connect your account

  1. Go back to the My Connections tab and find LawPay.

  2. Click Connect + and sign in to LawPay.

  3. Approve the request. Caddi retrieves your gateway credentials and the connection goes active.

How the connection behaves

  • Connections are scoped to merchant accounts, not individual users. After authorization, Caddi retrieves the gateway credentials for your merchant accounts and works through those.

  • Test mode and live mode are hard-partitioned. Each merchant account has separate test and live keys, and they cannot be mixed.

  • 8am does not document a refresh token for this flow. Caddi stores the gateway credentials retrieved at authorization rather than refreshing a token, which means connections are stable but a revocation requires reconnecting.

  • Revoking access. Use Developers → Authorized Applications in your LawPay account to revoke Caddi, or delete the partner application.

  • Live payment processing requires 8am certification of the integration, including a recorded end-to-end demo. Caddi handles this; it's worth knowing it exists if you're planning a go-live date.

Troubleshooting

No partner applications appear under Developers

8am hasn't created one yet. Email devsupport@8am.com, or contact Caddi support to use Caddi's partner application instead.

A redirect error when connecting

The Redirect URI on the partner application doesn't match https://app.trycaddi.com/oauth-callback. Correct it in the LawPay Developers area.

Payments are created but don't appear in LawPay

You may be authenticated against test-mode gateway credentials. Confirm which mode the connection is using with Caddi support.

The connection was working and stopped

Check Developers → Authorized Applications in LawPay — the application may have been revoked. Reconnect from Caddi.

Still stuck? Contact Caddi support with the exact error message you're seeing and the time it occurred.

Automation ideas

Law Firms

Invoice sent → payment link and follow-up

Caddi generates the LawPay payment link when an invoice goes out and schedules the follow-up reminders, so collections stop depending on someone remembering.

Payment received → ledger and matter update

When a LawPay payment settles, Caddi records it against the matter, updates the client ledger, and logs the activity — with trust and operating accounts kept distinct.

Retainer depleted → replenishment request

Caddi watches trust balances against your threshold and drafts the replenishment request with a payment link when a matter runs low.

Did this answer your question?