# List Accounts

`lawpay_list-accounts` · LawPay MCP tool · Transactions

List the operator-configured LawPay accounts (id, label, and which one is the configured default search scope). Synthetic — makes no LawPay API call; returns an empty list when no accounts credential is configured.

## LawPay Frequently Asked Questions

**What does the List Accounts tool do?**

This page documents the List Accounts tool (`lawpay_list-accounts`). List the operator-configured LawPay accounts (id, label, and which one is the configured default search scope). Synthetic, makes no LawPay API call; returns an empty list when no accounts credential is configured. It is one of the LawPay Transactions tools, invoked through your firm's Weave MCP connection and available to members whose access level permits it.

**Why is the account list empty?**

The list shows the account names your admin entered when connecting LawPay. If none were entered, it is empty, and searches still work across every account.

**Does list-accounts call LawPay?**

No. It reads the account names saved with your firm's connection, so it answers instantly and never counts against LawPay's API.

**What is the LawPay integration?**

The LawPay integration connects your firm's LawPay account to Weave. LawPay is a legal-industry payment platform (AffiniPay). This integration exposes read-only access to your LawPay Payment Gateway transactions, search, look up by ID, and look up by source ID, as governed MCP tools, scoped per member by access level. It does not move money or change any LawPay data. It groups 4 tools into 1 category, exposed through your firm's Weave MCP connection and filtered per member by access level.

**How does my firm connect LawPay to Weave?**

An admin opens LawPay in the Weave console, clicks Connect, and enters your LawPay API secret key. Optionally, they can name your accounts (for example Operating and Trust) and choose a default account to search. Every firm member then works through that one connection, limited by their Weave access level.

**Can these tools charge a card, issue a refund, or move money?**

No. Every public LawPay tool is read-only. None of them can create a charge, issue a refund, void a payment, or change any LawPay setting.

**Why does every LawPay request fail after connecting?**

LawPay lets a merchant restrict API access to specific IP address ranges. Weave's servers do not use a fixed IP address, so if your LawPay account has an API IP allowlist configured, LawPay rejects Weave's requests. Leave the API IP allowlist empty in your LawPay settings to use this integration.

**Does it cover both my operating and trust accounts?**

Yes. Searches cover every account unless your admin chose a default account, and you can always ask for all accounts. If your admin names your accounts when connecting, you can ask for a specific account by name (for example Trust), and results show which account each payment was processed against.

**How are amounts shown?**

Amounts come back exactly as LawPay reports them: whole numbers in the currency's smallest unit, so 150000 in USD means $1,500.00. Your assistant converts them when it answers.

## Related
- /integrations/lawpay/transactions/search-transactions/
- /integrations/lawpay/transactions/get-transaction/

## Input

_No fields._

## Output

- **accounts** `array` (required) — Operator-configured accounts, in configured order; empty when no accounts credential is set (use allAccounts or a raw account id).
  - **[]** `object`
    - **accountId** `string` (required) — Opaque LawPay account id; matches accountId on transactions.
    - **label** `string` (required) — Operator-configured display label (original casing).
    - **isDefault** `boolean` (required) — True if this account is the configured default search scope.