Collect
Create payment requests, track incoming funds, match receipts, and investigate unpaid invoices.
The financial layer for a new generation of companies.
Shared payments infrastructure and intelligent financial agents, built first for the Humanscaled venture network and designed for independent developers and businesses.
Collections prototype live · All transactions synthetic
Give it a financial job in ordinary language. The agent understands the task, finds the relevant records, and works through the payment lifecycle using permissioned tools. Humans approve consequential actions. Actual transaction state determines what gets reported.
Create payment requests, track incoming funds, match receipts, and investigate unpaid invoices.
Find a payee, review balances, prepare a transfer, secure specific approval, and observe execution.
Connect invoices, orders, receipts, and financial records, with no accidental double allocation.
Handle missing payments, incorrect references, insufficient funds, duplicates, and interrupted tasks.
“Pay our supplier $120 from the operating account. Ask me before sending it.”
Target workflow: account and payee lookup → exact preparation → trusted confirmation → financial record → status and reconciliation. Synthetic transfer integration is in development.Humanscaled is building companies across commerce, travel, healthcare, insurance, and financial services. They all need to collect money, make payments, and keep accurate financial records. Building those capabilities separately for every venture would multiply cost, complexity, and dependence on providers.
OpenPaygents develops a reusable payments foundation that increases economic and technical independence for the portfolio and other builders. Financial agents are a powerful interface to that foundation, while the underlying services work through conventional APIs as well.
These are the venture application areas. The current public prototype demonstrates synthetic merchant collections; domain-specific implementations remain at different stages of development.
Choose your models, financial providers, and infrastructure. The agent handles interpretation and workflow. The financial services handle permissions, exact amounts, approvals, records, and safe retries.
Model-independent interfaces, exportable records, modular payment adapters, and a self-hostable direction. The reference implementation uses Cloudflare services and Neon Postgres.
The collections sandbox uses synthetic payment contexts from Vietnam, Thailand, and Brazil. Broader cross-border payment capabilities are a strategic development area, not currently live rails.
Create a synthetic payment request, issue a sample bank receipt, and see exact matching, duplicates, and exceptions for yourself. The connected financial agent and banking services are being integrated.