Loading
Platform · Agentic Payments
People set the limits. Agents do the work. Mesta settles.
Your software already decides who gets paid, how much, and why. We turn those decisions into settled money — payroll, suppliers, sellers, treasury — landing in local-currency accounts in 40+ currencies, under our licenses and regulated partners. $2.5B settled to date. Now your agents reach Mesta over MCP, starting with the documentation server; when the payment tools open, anything that moves money waits for a named person.
The run
One payout, end to end.
The agent passes every limit and still can’t move money — that’s the design. One signature later, MX$343,539.00 lands — to the centavo.
Intent · MCP
> tools/call payments.quote { from: "USD", to: "MXN", amount: 18450.00 }
< { rate: 18.62 · beneficiary_receives: "MX$343,539.00" · guaranteed: true · window: "SPEI · value today" }
> tools/call runs.request
Mandate · Limits & Approval
agt_7c21… → payroll platform KYB verified → its Head of Treasury
limits ≤ $25,000/txn · ≤ $150,000/day · corridors US→MX, US→BR · expires 2026-12-31
amount ✓ velocity ✓ corridor ✓ recipient ✓
$18,450 > $10,000 approval threshold → human approval required
Approval packet
packet sha256:9f2c…e41a
$18,450.00 → MX$343,539.00 · beneficiary in Mexico · CLABE ••••4907 ✓ check digit · ✓ name match
Signed by the Head of Treasury with a passkey — bound to the exact artifact reviewed.
Settlement
workflow payout.mx.spei · one of 150 versioned workflows
SettledSPEI ref 2026080641772034 · 14:32:07 CST
Beneficiary received MX$343,539.00 — the guaranteed amount, exactly.
Illustrative product UI
That’s the shape a payroll platform’s run will take — yours will run the same way.
The engine
The engine is already built to be driven.
Every payment here already executes as software: fixed steps, version history, built-in approvals. Opening that to your agents is an interface project, not a rebuild.
150 versioned workflows
Every payment executes as a versioned workflow across our services and provider network. Every step is recorded, so any payment can be reconstructed end to end — and human approval is available as a step inside the flow.
Intelligence already in the loop
We read and validate invoices and onboarding documents against each destination country’s requirements, reconstruct failed payments across services and propose the fix, and assist compliance review at volume.
A licensed last mile
40+ currencies, fiat and stablecoin rails, into a real account in local currency — under licenses that took years to earn.
Running today
We automated our own floor first.
None of this is roadmap. It runs inside Mesta every day, driven by our own internal agents. What we run internally is what we're packaging for yours.
Documents validate themselves
Our own onboarding queue runs these checks first — every invoice, every file, in production.
Failed payments diagnose themselves
Diagnosis plus proposed fix — the single hardest job in cross-border, running on our own data.
Compliance review keeps pace
Our AI assembles the evidence; our analysts make the call — at production volume.
What we’re building
Opening the engine to your software.
Three layers, in the order we're opening them. The first has opened its documentation door.
01
The tools — MCP and Agent Skills
Mesta over the Model Context Protocol. The documentation server is open today at docs.mesta.xyz/mcp, so any MCP-compatible agent finds every operation, reads the guides and rehearses calls against the sandbox; the payment tools, shaped around outcomes, follow. Agent Skills will sit alongside, carrying the knowledge that is genuinely hard to get right: which corridor supports which payment type, what a beneficiary needs in each country, how to recover from a rejection.
- High-level tools shaped around outcomes — not 104 endpoints wrapped one-to-one
- Read and quote openly; anything that moves money waits for a named person’s release
- Authorization checked on every single tool call — by our infrastructure, not by the agent’s good behavior
- Errors that name the offending field, so an agent corrects itself in one turn
02
The workflows layer
Define a payment process once — recipients, eligibility, funding, approvals, limits, corridors — then run it on a schedule or on demand. Every run reconciled, every payment tracked individually, every failure repairable without failing the run.
- One definition, versioned and approved before it can execute
- A run paying ten thousand recipients is still one reviewable object
- A durable guarantee that a retry never becomes a second payment
03
Mandates — the authorization layer
KYC and KYB don’t go away — mandates sit on top of them. We bind an agent’s signing key to a KYB-verified legal entity and a named person, then issue a signed, scoped, revocable mandate stating exactly what it may do — and above what amount a person must approve.
- Limits by amount, velocity, recipient, corridor and expiry — evaluated in code
- Approval bound cryptographically to the exact artifact that was reviewed
- Narrow or revoke authority instantly, including for runs already scheduled
- Every payment carrying provable evidence of who permitted it, and within what bounds
Where this goes
What your software will be able to hand us.
Not one payment at a time. Whole processes, run repeatedly, adapting as the inputs change.
Payroll that runs itself
A roster changes, the run adapts. Rejected rows get repaired against the destination country’s rules. You approve once, and each month lands without anyone assembling a file.
Invoice to settled payment, end to end
An approved invoice becomes a validated recipient, a funded run, a routed corridor and a reconciled payment — with the purpose code, tax identifiers and beneficiary fields that country requires already correct.
Treasury that acts on its own signals
Balances rebalanced across corridors ahead of a cut-off rather than after it, on the conditions you set, with every movement authorized and reconciled like any other payment.
Marketplace payouts at the moment of earning
Sellers paid as revenue clears rather than on a weekly batch, across dozens of countries, without your team growing to match the seller count.
The build order
Three phases, none betting on the next.
OneConnect your agents through MCPOpen now through the documentation server: agents find every payment function, read its definition and rehearse quotes, status and payment instructions in the sandbox. The payment tools, where every instruction waits for a named person to release it, follow in this phase.
TwoBusiness workflows and mandate controlsBeginning Q4 2026. Workflows you approve once and run on schedule; a ledger that can’t be edited after the fact; spending limits, expiry and off switches enforced in code; approvals signed with a passkey; an audit trail you can hand to your auditor.
ThreeEnd-to-end agentic transactions within approved limitsAgents run whole payment processes inside limits a named person approved in advance, with anything outside them waiting for a person. The agents we run on our own floor, offered to you. Identity for third-party agents as standards mature.
Each phase lets software do more of the payment. What never changes: a named person stays accountable for the money. In Phase One every instruction that moves money waits for one; in Phase Three anything outside the limits they approved still does.
The full architecture — the mandate document, the tool tiers, the controls, the market map — lives one level deeper.
Read the full architecture
Agentic payments
Bring your agent.
Point it at Mesta today — the documentation server is open on the API it already reads.