Rail-neutral mandates
The same caps, payees and expiry apply whether the agent pays by bank transfer or on a token rail.
Markets and digital assets
Tokenised deposits and stablecoin rails
Programmable money still needs a programmable mandate on top.
Tokenised deposits, stablecoins and central-bank experiments such as MAS's Project Orchid on purpose-bound money make payments programmable. Specifications such as x402 carry payments inside HTTP requests between machines. AgenticOpenFinance keeps the mandate, the identity check and the evidence the same whether the payment settles on a bank rail or a token rail, and treats the rail as a connector.
What agents do
What you build on AgenticOpenFinance
HTTP 402 payment handling
When a service answers 402 Payment Required, the agent's payment is checked against its mandate before it is made.
Purpose limits
Payments can be limited to a purpose, a merchant category or a time window.
Counterparty checks
Receiving agents and addresses are checked against allow lists before payment.
Evidence across rails
Evidence packs record the rail, the transaction reference and the confirmation, whatever the rail.
Value chain
The actors in this chain
AgenticOpenFinance connects them with one identity check, one mandate model, one policy and one evidence trail.
PayerPaying agentService or merchant agentToken issuerBankWallet provider
Typical flow
A governed agent flow, step by step
- Service requests payment
- Mandate and purpose check
- Counterparty check
- Payment on permitted rail
- Confirmation
- Evidence sealed
Live demo
See it in the terminal
The same governed payment over API, SDK, CLI and an MCP tool call (demo). Demo data
DemoAll companies, people, agents and amounts are fictional. Protocol names refer to public specifications; naming one is not a partnership or an endorsement.
Glossary