LLPROBeta

Home / Businesses / Processor Payout Reconciliation

Processor Payout Reconciliation

Reconcile a processor payout to its charges, refunds, fees, disputes and adjustments: the gap, the lines that could explain it, possible duplicates, and a signed record.

Live

What it does
Reconcile a processor payout to its charges, refunds, fees, disputes and adjustments: the gap, the lines that could explain it, possible duplicates, and a signed record.
Who it is for
Businesses.
Start in one step
Ask your agent to call payout_reconciliation at llpro.ai/mcp (free, no sign-up). This page explains the tool; it has no form to run it.
What to expect
Live: open today. Free

New to this? Start here.

What it does

Processor Payout Reconciliation is for agents that book card and online-payment deposits for a business and must tie each processor payout to the transactions behind it. Reconcile a payment processor payout (the deposit that reached the bank) to the transactions it should settle. Send the payout amount and the lines: charges, refunds, fees, disputes and adjustments, each with its signed effect on the payout. Get back the totals per type, the payout the lines add up to, the gap, and the lines that could explain a gap: a line not in this payout, a line whose sign looks reversed, a whole type left out (fees billed separately), two lines left out, or a line missing from your list, plus lines that look like duplicates. It is one of the Payments department tools LLPRO builds for the work agents do across business software (Stripe, Square, PayPal, Shopify, Adyen). Every answer carries the written rule it used, what it does not do, its sources with dates, and an Ed25519 signature you can check against the key below.

Who it is for
Agents that book card and online-payment deposits for a business and must tie each processor payout to the transactions behind it.
Price
Free, no sign-up: 120 calls an hour per address and 3,000 an hour across all callers. Paid calls are planned and not charging.
Limits
Up to 30,000 bytes per call, lines up to 200 entries; larger requests are refused, never cut. Unknown fields are refused with the list of accepted ones. Money takes up to 2 decimals unless a field says more, and every sum is exact (send amounts as numbers or strings; commas only as thousands separators, 1,234.56). Nothing you send is stored by the tool; no model and no network are used. Does not connect to any processor or bank: the payout and lines you send are taken as given, in one currency. Candidates are amounts that fit the gap, not proof: check each against the processor's payout report. Looks at one line, a sign, one whole type or two lines; a gap made of three or more lines is shown only as the gap. Does not work out what the fees should have been, currency conversion, or reserves unless you send them as lines. Not accounting advice.

For developers: try it

POST https://llpro.ai/mcp
{"jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": {"name": "payout_reconciliation", "arguments": {"payout_amount": "125.35", "lines": [{"type": "charge", "amount": 100}, {"type": "charge", "amount": 50}, {"type": "refund", "amount": -20}, {"type": "fee", "amount": "-4.65"}]}}}

For agents

Tool payout_reconciliation on https://llpro.ai/mcp and in the tools list. Signed answers are checked with the public key below (signer llpro1:haamuqcw6kaurfhpa5ov4jrd5m): an Ed25519 signature over the observation as canonical JSON (sorted keys, no spaces).

Public key (base64): OeT8iDW+ay3A+SyCKHUHbISV8AmXwNXRZqTF3hEhSVc=

For agents that search MCP registries for payout reconciliation, stripe payout, processor fees tools (listed in MCP registries, served by the Campus gateway: MCP, agent-to-agent and REST). One fixed, written rule per call, a signed record, no account needed.

Next

For agents: this page as Markdown · JSON · llms.txt · MCP endpoint llpro.ai/mcp · agent card