Weave
Sign InSign Up
View as .md ↗
LawPay

LawPay | Get Transaction By Source Id

MCP server · Payments · lawpay.com · 1 category · 4 tools

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.

lawpay_get-transaction-by-source-id

Fetch a single LawPay Payment Gateway transaction by its merchant-supplied source id.

Tool Input

sourceIdstringrequired— Merchant-supplied source id assigned to the transaction at creation (distinct from the LawPay-assigned transaction id).(min length: 1)

Tool Output

dataobjectrequired— The requested transaction.
idstringrequired— Unique identifier of the transaction.
typestringrequired— Transaction type, e.g. "CHARGE", "REFUND", "CREDIT" (open string).
statusstringrequired— Transaction status, e.g. "COMPLETED" (open string).
accountIdstringrequired— LawPay account id the transaction was processed against.
accountNamestringnullrequired— Operator-configured display label for accountId (from the accounts credential); null when the id isn't mapped.
createdstringnullrequired— When the transaction was created; presence varies by endpoint (provisional).
completionTimestampstringnullrequired— When the transaction completed; null while pending or unavailable.
amountintegerrequired— Transaction amount in integer minor units (e.g. USD cents).
currencystringrequired— ISO 4217 currency code, e.g. "USD" (open string).
amountRefundedintegernullrequired— Total amount refunded against this transaction, in integer minor units; null when not applicable.
surchargeAmountintegernullrequired— Surcharge amount included in the transaction, in integer minor units; null when not applicable.
autoCapturebooleannullrequired— Whether the charge was configured to auto-capture; null when not applicable.
authorizationCodestringnullrequired— Card network authorization code; null when unavailable.
failureCodestringnullrequired— Failure reason code (open string); null when not failed.
chargeIdstringnullrequired— Id of the parent CHARGE transaction; present on a REFUND.
referencestringnullrequired— Merchant-supplied correlation reference; null when unset.
cvvResultstringnullrequired— CVV verification result code (open string); null when not collected.
avsResultstringnullrequired— Address-verification result code (open string); null when not collected.
messagesarraynullrequired— Human-readable status/processing messages; null when none.
[]string
methodobjectrequired— Payment method used for the transaction.
typestringrequired— Payment method type, e.g. "card" or "bank" (open string).
cardTypestringnullrequired— Card brand, e.g. "Visa"; null for non-card methods.
numberstringnullrequired— LawPay-masked card number, e.g. "************4242"; null when not applicable.
last4stringnullrequired— Last four digits of the card number, derived from the masked number; null when not derivable.
expMonthintegernullrequired— Card expiration month (1-12); null for non-card methods.
expYearintegernullrequired— Card expiration year; null for non-card methods.
fingerprintstringnullrequired— LawPay's stable fingerprint for this payment method; null when unavailable.
namestringnullrequired— 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.
givenNamestringnullrequired— Individual bank account holder's given name; null for business holders or card methods.
surnamestringnullrequired— Individual bank account holder's surname; null for business holders or card methods.
bankNamestringnullrequired— Bank name; null for card methods.
accountTypestringnullrequired— Bank account type, e.g. "checking" (open string); null for card methods.
accountHolderTypestringnullrequired— Bank account holder type, e.g. "individual" or "business" (open string); null for card methods.
routingNumberstringnullrequired— LawPay-masked bank routing number, e.g. "******013"; null for card methods.
accountNumberstringnullrequired— LawPay-masked bank account number, e.g. "******0003"; null for card methods.
refundsarraynullrequired— Refunds issued against this transaction; present on a CHARGE, null otherwise.
[]object
14 fields
idstringrequired— Unique identifier of the refund transaction.
typestringrequired— Transaction type (open string; expected "REFUND").
statusstringrequired— Transaction status, e.g. "COMPLETED" (open string).
accountIdstringrequired— LawPay account id the refund was processed against.
accountNamestringnullrequired— Operator-configured display label for accountId (from the accounts credential); null when the id isn't mapped.
createdstringnullrequired— When the refund was created; presence varies by endpoint (provisional).
completionTimestampstringnullrequired— When the refund completed; null while pending or unavailable.
amountintegerrequired— Refund amount in integer minor units (e.g. USD cents).
currencystringrequired— ISO 4217 currency code, e.g. "USD" (open string).
failureCodestringnullrequired— Failure reason code (open string); null when not failed.
chargeIdstringnullrequired— Id of the parent CHARGE transaction this refund applies to.
referencestringnullrequired— Merchant-supplied correlation reference; null when unset.
methodobjectrequired— Payment method used for the refund.
15 fields
typestringrequired— Payment method type, e.g. "card" or "bank" (open string).
cardTypestringnullrequired— Card brand, e.g. "Visa"; null for non-card methods.
numberstringnullrequired— LawPay-masked card number, e.g. "************4242"; null when not applicable.
last4stringnullrequired— Last four digits of the card number, derived from the masked number; null when not derivable.
expMonthintegernullrequired— Card expiration month (1-12); null for non-card methods.
expYearintegernullrequired— Card expiration year; null for non-card methods.
fingerprintstringnullrequired— LawPay's stable fingerprint for this payment method; null when unavailable.
namestringnullrequired— 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.
givenNamestringnullrequired— Individual bank account holder's given name; null for business holders or card methods.
surnamestringnullrequired— Individual bank account holder's surname; null for business holders or card methods.
bankNamestringnullrequired— Bank name; null for card methods.
accountTypestringnullrequired— Bank account type, e.g. "checking" (open string); null for card methods.
accountHolderTypestringnullrequired— Bank account holder type, e.g. "individual" or "business" (open string); null for card methods.
routingNumberstringnullrequired— LawPay-masked bank routing number, e.g. "******013"; null for card methods.
accountNumberstringnullrequired— LawPay-masked bank account number, e.g. "******0003"; null for card methods.
messagesarraynullrequired— Human-readable status/processing messages; null when none.
1 field
[]string

We're Adding More LawPay Tools Constantly!

Don't see a specific LawPay tool you need? Email [email protected] and we can add it.

LawPay Frequently Asked Questions

What does the Get Transaction By Source Id tool do?

This page documents the Get Transaction By Source Id tool (lawpay_get-transaction-by-source-id). Fetch a single LawPay Payment Gateway transaction by its merchant-supplied source id. 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.

What is a source id?

It is the identifier your own billing or practice management software attached to the payment when it was created, as distinct from the id LawPay assigns. Use it to jump straight from a record in another system to the matching LawPay payment.

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 Tools

get-transactionsearch-transactionsget-invoice