Financial agents. Open by design.
Give a financial agent the work of collecting invoices, paying suppliers, and keeping the books straight. OpenPaygents is being built to plan the steps, coordinate the tools, and see it through under your authority.
Meet your financial agent
We're building a financial operator that can plan, investigate, act, and adapt. One objective can become a sequence of tasks across your tools, with the context to keep going when the situation changes.
Break a financial goal into executable steps, check dependencies, and revise the plan when the situation changes.
“Prepare Friday's supplier run. Keep enough cash for payroll.”
A plan you can inspect before execution.
Planning + financial constraints
Bring the right account history, supplier terms, and operating policies into each task, with sources you can inspect and context you can edit.
“Can we pay this supplier today without touching the payroll reserve?”
Fresh financial state. Relevant business context.
ICM context routing + OKF knowledge
Turn a plan into typed tool calls across payment, invoice, and accounting services. Validate inputs, use scoped access, and check what each call actually changed.
“Find the invoice, check the receipt, and update the finance system.”
One objective carried across connected systems.
Typed tool calling · MCP adapter planned
Keep the task, its constraints, and its completed steps across sessions. Wait for a receipt, approval, or deadline, then pick up from the right place.
“Track these invoices and continue when their payments arrive.”
Work that can outlast the conversation.
Persistent tasks + event-driven execution
Set amounts, payees, budgets, and approval requirements. The agent can prepare and coordinate work while financial services enforce its authority.
“Pay approved suppliers up to $2,000. Bring new payees to me.”
Specific authority for specific financial actions.
Scoped tools + approval-bound execution
Preview a proposed payment run against a copy of the financial state. Inspect cash impact, unmet conditions, and expected results before authorizing execution.
“Show me what happens to our balance if we run this plan.”
A financial what-if you can examine.
Synthetic state + execution previews
Work through ambiguous payees, mismatched receipts, failed tools, and uncertain payment outcomes. Ask a useful question or recover without repeating a financial action.
“That payment timed out. Find out what happened before retrying.”
A timeout becomes an investigation.
Recovery journals + idempotent operations
Let a purchasing, travel, or operations agent bring financial work to OpenPaygents. Exchange scoped tasks, progress, and results while keeping each agent's authority explicit.
“The purchasing agent has an approved order. Prepare its payment.”
Financial capability for a wider agent ecosystem.
Agent2Agent · A2A
Add reviewed financial skills for a new supplier process, collections policy, or market. Version the instructions and reuse the same agent across different jobs.
“Use our booking-deposit procedure for this new travel product.”
New expertise without another isolated chatbot.
Portable Agent Skills + staged context
Purchase an API response, dataset, or other digital service within a task budget. Check the provider's payment terms, authorize the payment, and retain the receipt with the work.
“Get the data this task needs. Spend no more than $2.”
Machine payments with a financial record.
x402 · budgeted access to paid services
Compare configured payment options against cost, timing, and currency constraints. Carry the selected quote into approval, and bring changes back for a decision.
“Find a supplier-payment route within our cost and arrival limits.”
A payment decision with the tradeoffs visible.
Payment adapters + quote policies
Inspect the financial state independently of the agent's reply. Replay legitimate and adversarial scenarios, and check authorization, balances, and completed work.
“Show what the agent said, what it did, and what changed.”
An agent you can evaluate against the ledger.
Independent state API + SafeAgentEval
1 / 12
Agent capabilities are in development. These examples show the product direction; each feature carries its current status.
We're selecting standards for the jobs they do: MCP for tools, A2A for other agents, ICM for task context, Google's OKF for portable knowledge, x402 for paid digital services, and Agent Skills for reusable expertise.
AP2 payment mandates are being assessed for future agent commerce. Payment-network coverage and authorization still have to be implemented and tested for each adapter.
The financial work
Give it an objective, from collecting an invoice to preparing a supplier run. The agent finds the records, works through the steps, and brings you the decisions that need your attention.
“Collect the deposit for booking DP-1048. Tell me when the money arrives.”
Create payment requests, track receipts, and keep unpaid obligations visible. The financial record determines whether something has been paid.
“Prepare this week's supplier payments. Keep $5,000 in reserve and ask me before sending.”
Check payees, available funds, and spending rules before preparing exact payment instructions. Pause for approval and check the outcome before calling a payment complete.
“Check these receipts against our invoices. Show me anything that needs attention.”
INV-042 is for ฿8,400. The receipt is ฿500 short.Kept open for review. The duplicate was not counted again.
Compare obligations with financial events, identify duplicates, and explain the differences. Give your team a clear exception queue instead of another spreadsheet to untangle.
“The supplier payment timed out. Find out what happened before trying again.”
Investigate delays, interrupted requests, and uncertain outcomes. Preserve the task history, avoid blind retries, and make the decision to retry or escalate explicit.
Collect · 1 of 4
Synthetic collections and receipt matching are implemented in the prototype. Connected agents, supplier workflows, and banking execution are in development.
Our design commitments
Your payment network, your intelligence provider, and your financial records should remain choices you can make. OpenPaygents is being designed to keep those choices open as your business grows.
Connect local payment adapters through consistent interfaces. Use the same financial services in your app, through an API, or with an agent.
Choose and replace models without rebuilding the payment system. Give agents scoped financial tools, with permissions enforced outside the model.
Retain portable records and the ability to inspect, adapt, and host the core. The codebase is being prepared for public open-source release.
Built for merchants, finance teams, platforms, and the people building the next generation of financial agents.
A more open economy
A local business should have access to capable financial tools without the cost and complexity of building its own finance department.
That's the purpose of OpenPaygents: less time chasing payments, fewer barriers to trading, and more of the value staying with the people doing the work.
We have a particular commitment to the Global South, where local payment networks are changing what is possible. The infrastructure we're building is open to businesses and builders everywhere.
42% of adults in low- and middle-income countries made a digital merchant payment in 2024. There is much more room to open up participation.
World Bank · Global Findex 2025These are prototype environments. Bank connectivity, additional networks, and cross-border execution are future work.
For builders & researchers
The agent's answer is one part of the story. The financial records should let you check the rest. We're developing separate conversation and transaction interfaces for independent testing.
Payment requests and receipt matching, exact amounts and recipients, explicit authorization, duplicate events, insufficient funds, and recovery after a timeout.
The banking work also covers legitimate successful transfers. An agent has to complete the authorized task and report the result accurately.
A model uses a fixed set of financial tools. Controlled services enforce permissions, approval, and transaction rules. Business records remain readable independently of the agent's replies.
The same services can be called by conventional applications. You can change the model without replacing the financial foundation.
The browser prototype handles synthetic payment requests, exact receipt matching, duplicates, and exceptions for VietQR, PromptPay, and Pix profiles.
Persistent transaction services, conversational execution, banking workflows, and the SafeAgentEval adapter are being integrated. Early access will follow connected testing.
The direction is broader financial operations: supplier runs, collections follow-up, reusable approval policies, more payment adapters, and eventually cross-border workflows.
We're starting with the financial work shared by commerce, travel, healthcare, and other businesses, with an open foundation that others can extend.
Build with more freedom
Join the waitlist for early access and occasional product updates.