LawPay MCP Tool - Search Transactions

Q: What does the Search Transactions tool do?

This page documents the Search Transactions tool (lawpay_search-transactions). Search transactions for the connected LawPay account by free text, structured filters, or a date range, with pagination. 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.

Q: How do I narrow a search to a date range?

Pass startDate and endDate as ISO 8601 timestamps that include a time zone offset, for example 2026-10-01T00:00:00-07:00. Combine them with type, status, methodType, or name filters, and sort with orderBy (for example -created for newest first).

Q: Which account does a search cover?

If your admin set a default account, searches use it unless you name another account or set allAccounts to true. With no default, a search covers every account. You cannot pass both account and allAccounts.

Q: How many results come back at once?

20 per page by default, up to 100. The response includes totalEntries, so the assistant can page through larger result sets.

Q: 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.

Q: 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.

Q: 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.

Q: 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.

Q: 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.

Q: 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.

lawpay_search-transactions

Search transactions for the connected LawPay account by free text, structured filters, or a date range, with pagination.

Tool Input

qstring— Free-text query, matched across all transaction fields.

typestring— Filter to a transaction type, contributing a "type:<value>" structured filter.(enum: "CHARGE", "REFUND", "CREDIT")

statusstring— Filter to a transaction status, contributing a "status:<value>" structured filter.(enum: "PENDING", "AUTHORIZED", "COMPLETED", "VOIDED", "FAILED")

methodTypestring— Filter to a payment method type, contributing a "method.type:<value>" structured filter.(enum: "card", "bank")

namestring— Filter to a payment-method holder name, contributing a "name:<value>" structured filter.

qfarray— Additional raw "property:value" structured filter terms (incl. nested "a.b:value"), appended verbatim as repeated qf params — the escape hatch for filters outside the documented type/status/methodType/name enums.

[]string

accountstring— Account label or raw LawPay account id to scope the search to; resolved via the configured accounts map. Mutually exclusive with allAccounts.

allAccountsboolean— When true, search across every account (omit the account scope) even if a defaultAccount is configured. Mutually exclusive with account.

startDatestring(date-time)— ISO 8601 offset-qualified start of the date range.(pattern: ^(?:(?:\d\d[2468][048]|\d\d[13579][26]|\d\d0[48]|[02468][048]00|[13579][26]00)-02-29|\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\d|30)|(?:02)-(?:0[1-9]|1\d|2[0-8])))T(?:(?:[01]\d|2[0-3]):[0-5]\d(?::[0-5]\d(?:\.\d+)?)?(?:Z|([+-](?:[01]\d|2[0-3]):[0-5]\d)))$)

endDatestring(date-time)— ISO 8601 offset-qualified end of the date range.(pattern: ^(?:(?:\d\d[2468][048]|\d\d[13579][26]|\d\d0[48]|[02468][048]00|[13579][26]00)-02-29|\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\d|30)|(?:02)-(?:0[1-9]|1\d|2[0-8])))T(?:(?:[01]\d|2[0-3]):[0-5]\d(?::[0-5]\d(?:\.\d+)?)?(?:Z|([+-](?:[01]\d|2[0-3]):[0-5]\d)))$)

orderBystring— Comma-separated sort spec with an optional "+"/"-" prefix, e.g. "-created".

pageinteger— 1-indexed page number.(default: 1, >= 1)

pageSizeinteger— Page size (LawPay max 100).(default: 20, >= 1, <= 100)

Tool Output

pageinteger— 1-indexed page number of this result page.

pageSizeinteger— Number of results requested per page.

totalEntriesinteger— Total number of transactions matching the search.

resultsarray— Transactions on this page, in LawPay's returned order.

[]object

idstring— Unique identifier of the transaction.

typestring— Transaction type, e.g. "CHARGE", "REFUND", "CREDIT" (open string).

statusstring— Transaction status, e.g. "COMPLETED" (open string).

accountIdstring— LawPay account id the transaction was processed against.

accountNamestringnull— Operator-configured display label for accountId (from the accounts credential); null when the id isn't mapped.

createdstringnull— When the transaction was created; presence varies by endpoint (provisional).

completionTimestampstringnull— When the transaction completed; null while pending or unavailable.

amountinteger— Transaction amount in integer minor units (e.g. USD cents).

currencystring— ISO 4217 currency code, e.g. "USD" (open string).

amountRefundedintegernull— Total amount refunded against this transaction, in integer minor units; null when not applicable.

surchargeAmountintegernull— Surcharge amount included in the transaction, in integer minor units; null when not applicable.

autoCapturebooleannull— Whether the charge was configured to auto-capture; null when not applicable.

authorizationCodestringnull— Card network authorization code; null when unavailable.

failureCodestringnull— Failure reason code (open string); null when not failed.

chargeIdstringnull— Id of the parent CHARGE transaction; present on a REFUND.

referencestringnull— Merchant-supplied correlation reference; null when unset.

cvvResultstringnull— CVV verification result code (open string); null when not collected.

avsResultstringnull— Address-verification result code (open string); null when not collected.

messagesarraynull— Human-readable status/processing messages; null when none.

1 field

[]string

methodobject— Payment method used for the transaction.

15 fields

typestring— Payment method type, e.g. "card" or "bank" (open string).

cardTypestringnull— Card brand, e.g. "Visa"; null for non-card methods.

numberstringnull— LawPay-masked card number, e.g. "************4242"; null when not applicable.

last4stringnull— Last four digits of the card number, derived from the masked number; null when not derivable.

expMonthintegernull— Card expiration month (1-12); null for non-card methods.

expYearintegernull— Card expiration year; null for non-card methods.

fingerprintstringnull— LawPay's stable fingerprint for this payment method; null when unavailable.

namestringnull— Holder display name — the account/card holder name for business bank and card methods, or the given name + surname composition for individual bank holders; null when unavailable.

givenNamestringnull— Individual bank account holder's given name; null for business holders or card methods.

surnamestringnull— Individual bank account holder's surname; null for business holders or card methods.

bankNamestringnull— Bank name; null for card methods.

accountTypestringnull— Bank account type, e.g. "checking" (open string); null for card methods.

accountHolderTypestringnull— Bank account holder type, e.g. "individual" or "business" (open string); null for card methods.

routingNumberstringnull— LawPay-masked bank routing number, e.g. "******013"; null for card methods.

accountNumberstringnull— LawPay-masked bank account number, e.g. "******0003"; null for card methods.

refundsarraynull— Refunds issued against this transaction; present on a CHARGE, null otherwise.

1 field

[]object

14 fields

idstring— Unique identifier of the refund transaction.

typestring— Transaction type (open string; expected "REFUND").

statusstring— Transaction status, e.g. "COMPLETED" (open string).

accountIdstring— LawPay account id the refund was processed against.

accountNamestringnull— Operator-configured display label for accountId (from the accounts credential); null when the id isn't mapped.

createdstringnull— When the refund was created; presence varies by endpoint (provisional).

completionTimestampstringnull— When the refund completed; null while pending or unavailable.

amountinteger— Refund amount in integer minor units (e.g. USD cents).

currencystring— ISO 4217 currency code, e.g. "USD" (open string).

failureCodestringnull— Failure reason code (open string); null when not failed.

chargeIdstringnull— Id of the parent CHARGE transaction this refund applies to.

referencestringnull— Merchant-supplied correlation reference; null when unset.

methodobject— Payment method used for the refund.