•••• •••• •••• 4417
Treasury, cards and books in one place.
We are designing a home for the stablecoin wallets a finance team holds, the cards and agent wallets that spend from them, and the reporting that follows. Funds stay on‑chain throughout.
What Unifraction is
Unifraction is a design for one place to run a company’s on-chain money. The wallets, the treasury, the cards and agent wallets that spend from them, and the books, on one record.
A finance team sets up the wallets and who signs for them. An admin authorizes an amount for each card or agent wallet, with one signature or several, and a payment settles on‑chain against it. The wallet and the ledger should be the same record, so the reporting starts from the same place as the money.
It is at the idea stage: nothing here is live, and there is nothing to sign up for yet. What follows is design work. We are publishing it early to find out whether finance teams want it built.
More companies will hold stablecoins. The tools are in pieces.
We expect stablecoins to become a normal way for companies to hold and move money. This is what that looks like today, and where it breaks.
500,000.00 USDC
A company’s first money can now arrive as stablecoins.
Y Combinator has announced that the startups it funds can choose to receive their funding in stablecoins. A company that does starts with its funding on‑chain and nothing set up to control it, approve spending from it or keep its books.
Source: Y Combinator’s announcement on LinkedIn, February 3, 2026
Stablecoins are already spent by card.
Visa said in September 2026 that more than 160 stablecoin-linked card programs run on its network, with payment volume up nearly 200% in a year. The cards exist; the approvals and the books around them are still in pieces.
Four reasons a company would hold them
A dollar balance you hold yourself
Stablecoins are designed to hold the value of a currency such as the dollar, and a company can keep them in a wallet it controls.
Approval built into the payment
A wallet can ask for several signatures and enforce limits, so the rules travel with the money instead of sitting in a policy document.
One record for the money and the books
Every movement is written to a ledger the chain keeps, so accounting can start from the same source as the payment.
Spendable by software
An agent or a service can hold a balance and pay for what it uses, request by request, with no card on file.
How a company manages stablecoins today
Each stage needs a tool, and each tool keeps its own record. Someone matches them by hand at month end.
5 tools, 5 records
Examples of the tools a team reaches for.
- ReceiveExchange account
- HoldWallet
- ControlChat approvals
- SpendTransfers
- AccountSpreadsheet
1 platform, 1 record
One record, from receiving funds to reporting.
One platform, four jobs
Wallets and treasury, the cards and agents that spend from them, the controls in between, and the books that come out.
USDC
USDT
BNB Chain
Reporting Approvals Screening Cards Agent wallets
Hold
Company money, in wallets your finance team controls.
Stablecoin wallets
Hold company funds in wallets your finance team controls, with the signers you nominate.
On-chain treasury
Funds stay on‑chain. Balances, movements and the ledger are the same record, not two systems to reconcile.
Spend
Cards and agent wallets that draw on an authorized amount.
Cards on authorized amounts
An admin authorizes an amount, and the card spends against it. One signature or several, set per configuration.
Agent payment wallets
Give an AI agent its own wallet and its own limit, and let it pay for each call it makes, inside that limit.
Control
Who can authorize what, and where a payment may not go.
Limits per card and per agent
Per-transaction, daily and monthly limits, with a threshold above which an approval is required.
Roles and approvals
Owners, admins, approvers and viewers, each seeing and authorizing only what their role allows.
Merchant and wallet screening
Turn on monitoring to stop payments to sanctioned merchants and addresses before they leave.
Account
The books come from the same record as the money.
Spend as it happens
Authorizations and settlements arrive in one feed, with the wallet they drew on.
Reporting and accounting
Every authorization and settlement is already a ledger entry, so the books come from the same place as the money.
How it would work
Four steps, and the money stays on‑chain through all of them.
- Finance team
Finance sets it up
A CFO, or someone on the finance team, connects the company wallet, names the signers, and decides who may authorize what. No engineer needed.
- Admin
An admin authorizes an amount
Each card and each agent wallet spends against an amount an admin has authorized. Depending on how the wallet is configured that takes one signature or several.
- On-chain
Spend settles on-chain
When a payment happens, the authorized amount settles against the wallet. Who the settlement partner would be has not been chosen yet.
- Ledger
The books keep themselves
By the time a payment settles, its ledger entry already exists. Reporting and accounting read that record, not a copy of it.
Concept screens
Design work, not a live product. Every name, wallet and figure below is invented.
The signers agree an amount first.
- Two of three signatures before an amount is authorized.
- SignedPriya NairHead of finance
- AwaitingMarcus BellCFO
- AwaitingLena OrtizController
Decide where and how much a card or agent can spend.
- The limits and merchant rules behind a card or an agent wallet.
- Per transaction
- 2,500.00 USDC
- Daily
- 7,500.00 USDC
- Monthly
- 40,000.00 USDC
- Approval above
- 1,000.00 USDC
Allow, ask or block each kind of merchant.
- Allow a merchant category, send it for approval, or block it outright.
- SoftwareMCC 5734
- Cloud hostingMCC 7372
- Travel agenciesMCC 4722
- RestaurantsMCC 5812
- Cash advanceMCC 6010
A card that draws on the authorized amount.
- A limit on one card, with the status spelled out beside the meter.
Each allocation settles against the wallet.
- Card, employee, sub-wallet and AI agent allocations all draw on the same wallet, and each one settles on-chain.
- AuthorizedSigners approved
- BroadcastSent to BNB Chain
- Confirming7 of 12 confirmations
- SettledFinal on-chain
Roles decide who sees and approves what.
- Roles, and what each one may do.
| Member | Role | Can | Last active |
|---|---|---|---|
Priya Nair priya@northwind.example | Owner | Everything, including billing and signer changes | Today |
Marcus Bell marcus@northwind.example | Admin | Issue cards, set limits, invite members | Today |
Lena Ortiz lena@northwind.example | Approver | Approve spend requests and releases | Yesterday |
Ada Okonkwo ada@northwind.example | Member | Use their own card and file expenses | 3 days ago |
Sam Iyer sam@northwind.example | ViewerInvite pending | Read reports only | Invite pending |
- Priya Nairpriya@northwind.exampleOwner
Everything, including billing and signer changes
- Marcus Bellmarcus@northwind.exampleAdmin
Issue cards, set limits, invite members
- Lena Ortizlena@northwind.exampleApprover
Approve spend requests and releases
- Ada Okonkwoada@northwind.exampleMember
Use their own card and file expenses
- Sam Iyersam@northwind.exampleViewerInvite pending
Read reports only
Wallets that agents can spend from
An agent gets its own wallet, its own limit and its own ledger line, and pays for what it calls over x402. The same authorization rules apply as to a card.
x402 is an open standard for internet-native payments: x402.org
GET /v1/forecast HTTP/1.1
Host: data.example.comHTTP/1.1 402 Payment Required
{
"price": "0.05 USDC",
"network": "BNB Chain",
"payTo": "0x7a3f…c9e1"
}POST /v1/agents/ag_4417/pay HTTP/1.1
Host: api.unifraction.example
HTTP/1.1 200 OK
{
"payment": "eyJ4NDAy…",
"limitLeft": "19.95 USDC"
}GET /v1/forecast HTTP/1.1
Host: data.example.com
X-PAYMENT: eyJ4NDAy…
HTTP/1.1 200 OKIllustrative only. The addresses, amounts and identifiers are invented, and this is not a published interface.
The agent calls a paid service
A request for something the service charges for, such as data or compute.
The service answers 402
HTTP 402, Payment Required, with the price. This is the x402 flow.
The wallet checks the limit
The agent’s wallet checks its own limit and the authorization rules before it pays.
The request goes through
The agent retries with proof of payment, and the spend lands as one line in the ledger.
Paid
Questions
Something we have not covered here?Email hello@unifraction.io
Deciding whether to back it?Read the pitch deck (PDF)
What is Unifraction?
Is any of this live?
Who is it for?
Where do the funds sit, and who holds the keys?
Which stablecoins and networks?
How is spending authorized?
How does settlement work?
Would it replace our accounting software?
Is a stablecoin balance cash on our books?
What is an agent payment wallet?
What stops an agent from spending too much?
Can we stop payments to sanctioned merchants and wallets?
What about licensing and compliance?
What happens when I join the waitlist?
Join the waitlist
Leave your work email, and we will get in touch when there is something to show.
What we will ask you then
- Where your stablecoins sit today, and who can move them.
- How card spend and approvals work now, and what you reconcile against.
- Whether agents or services already spend on your behalf.
You are on the list. We will get in touch when there is something to show. No newsletter, and you can ask us to remove your address at any time.
Check your email. We sent a link to confirm your address.
Thank you. Your address is confirmed.
Something in the form needs another look. Check the fields and try again.
We could not check that you are a person. Try again, or email hello@unifraction.io.
That is a lot of attempts in a short time. Wait a while and try again, or email hello@unifraction.io.
That did not send. Try again in a moment, or email hello@unifraction.io.
That confirmation link has expired or is not valid. Join the waitlist again to get a new one.
What we collect: your email, your company if you give one, the time you agreed, the country you connect from, and scrambled forms of your network address, kept a day to limit repeat submissions and 90 days to spot bulk signups. We use it only to contact you about Unifraction. It is stored with Cloudflare, which runs this form, and we do not share it with anyone else. We keep your details until you ask us to remove them.