The subledger for agentic commerce
Let agents move money.Keep the controls finance requires.
Axorum checks every payment an agent proposes against the limits your company set, before it settles, and records the decision. Inside the limits, the payment goes through. Outside them, the money never moves.
- Checked before settlement, not after
- Limits that hold across every agent and payment method
- Never holds or moves your money
- Verdict
- Agent
- procurement-agent
- Requested
- $1,200.00
- Mandate
- $5,000.00 a month
- Spent so far
- $4,300.00 across 3 agents
$1,200.00 would bring this month's total to $5,500.00 against a $5,000.00 mandate.
Nothing moved. The refusal is on record as evidence the control worked.The problem
Agents can reach real money. Finance has no matching controls.
A company can hand an autonomous agent a card or a funded wallet today. What it cannot hand the finance team is a way to control what happens next. The standing advice to developers is to fund an agent only with what you can afford to lose, and to assume a compromised or confused agent could drain the whole balance. That is how you set a limit at a casino. A controller needs six answers before any payment, and today none of them exist for an agent. Until they do, the only control left is to keep agents away from money.
| Control | Question | Today |
|---|---|---|
| Identity | Who is acting? | Missing |
| Authority | Under whose authority? | Missing |
| Mandate | What is it allowed to buy? | Missing |
| Counterparty | Is this counterparty approved? | Missing |
| Budget | How much budget is left? | Missing |
| Policy | Does this fit within the active corporate policies? | Missing |
| Evidence | Can we prove afterwards that the controls worked? | Missing |
Why today's controls fall short
Agents at machine speed need accounting and controls at machine speed.
Built for people
Detective: they find the problem
Approval queues, card limits, reconciliation and fraud review were built for human volume, with a window in which someone can investigate or reverse a mistake. They tell you what happened.
Needed for agents
Preventive: they stop it
Agents act in milliseconds, and some payment methods settle instantly and cannot be reversed. A control that fires a minute late has controlled nothing. The check has to happen before the payment, and the record has to be written in the same moment, because a minute later the agent that acted may no longer exist.
How it works
A checkpoint between the agent and the payment network.
Agent, then Axorum, then the network that moves the money. The checkpoint lives outside the agent, so the agent cannot reason its way around it. It sits before the network, because that is the last point where saying no costs nothing.
- Step 1
Agent initiates payment
Any agent, any framework, any way of paying: card, bank transfer, stablecoin, x402.
- Step 2
Axorum verifies
Is this the right agent? Is its authority valid right now? Is the purchase inside its mandate, the written limits of what it may do for you? Is the counterparty permitted? Is there budget left after everything the fleet has already spent?
- Step 3
Payment processed
An approved instruction goes to whichever network you use. A refused one goes nowhere. Axorum never holds or moves the money itself, and it is tied to no payment company, which is why it can sit above all of them.
Either way, the decision is written down at that moment.
Who acted, under whose authority, which rules applied, where the budget stood. The settlement result comes back to join the same record. Refusals are kept too: a refused payment is evidence the control worked.
Proof
Don't take our word for it. Watch it refuse a payment.
Two ways in, both free, both in your browser. Run the real engine and try to break it, or read the short course that builds the idea one entry at a time.
Break it and watch it hold
Watch agents pay each other, then stop a machine or cut the connection between them. The books stay balanced, refused payments stay refused, and nothing posts that should not have.
- Runs the real engine, not a recording
- Break it yourself and watch it hold
- Nothing to install, nothing to sign
How a ledger learns to say no
A short scrolling explainer for finance readers. It starts with one journal entry and ends with a refusal, one step at a time, with no code and no jargon.
"This charge duplicates an invoice already settled on April 3."
3 of 8 chapters
- Plain English throughout
- The five outcomes, worked by hand
- No account required
Who it's for
Your customers will ask how to let agents pay, and how to get paid by them.
You could build this yourself. Keeping a financial ledger that gives the same answer every time is a sharp turn away from billing or AP software, and every platform needs roughly the same thing. Embed it instead, and be the platform that made agents safe.
Billing and revenue platforms
Accept money from agents
Money will arrive from agents your customers cannot name. Give them a channel they can book and defend: the payer resolved, the price checked against the contract, the entry written when the cash lands.
Spend and AP platforms
Let agents pay
Your customers will hand an agent a card whether policy allows it or not. Offer limits that hold across the whole fleet and every payment method, and refusal before anything moves.
CFOs and controllers
Approve it with your eyes open
The integrator builds with us; the controller approves us. Axorum was built by a startup CFO who has signed the attestation letters and an infrastructure engineer who builds the systems that make controls hold at machine speed.
The payment networks for agents are being built either way.
The open question is whether companies will trust agents enough to use them. We are selecting design partners on both sides of the market now. Book a walkthrough and pressure-test it with us.