Work across networks.
Connect local payment adapters through consistent interfaces. Use the same financial services in your app, through an API, or with an agent.
Open payments infrastructure. Financial agents.
We're building open financial infrastructure that connects payment networks, puts agents to work, and gives businesses more freedom to trade.
The financial operations agent
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.