Virtual
Unifraction
Unifraction•••• •••• •••• 4417
Idea stage · Waitlist open
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.
Early stage. Nothing here is live yet.
Where this is
Unifraction is at the idea stage. There is no product to sign up for, no account to open and nothing to connect a wallet to.
The problem we keep seeing: a company holds stablecoins, then runs its cards, its approvals and its accounting through three other systems, and reconciles them by hand at month end. The wallet and the ledger should be the same record.
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.
A sign of what is coming
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, 3 February 2026
500,000.00 USDC
What holding them gives a company
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 adapts today
Each stage needs a tool, and each tool keeps its own record. The company is the integration.
Receive
Take payment or funding in stablecoins.
- A wallet address
- An exchange account
Hold
Keep it somewhere the team controls.
- A wallet app
- A multisig tool
Control
Decide who can spend, and where.
- Chat approvals
- A screening service
Spend
Pay vendors, staff and software.
- Manual transfers
- A card programme
Account
Keep the books and report.
- Spreadsheets
- Accounting software
The idea
One record, from receiving funds to reporting.
Examples of the pieces a team can end up joining by hand.
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.
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 authorised amount.
Cards on authorised amounts
An admin authorises 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 per request over x402.
Control
Who can authorise 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 authorising 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
Authorisations and settlements arrive in one feed, with the wallet they drew on.
Reporting and accounting
Every authorisation 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 authorise what. No engineer needed.
- Admin
An admin authorises an amount
Each card and each agent wallet spends against an amount an admin has authorised. Depending on how the wallet is configured that takes one signature or several.
- On-chain
Spend settles on-chain
When a payment happens, the authorised amount settles against the wallet. Who the settlement partner would be has not been chosen yet.
- Ledger
The books keep themselves
Every authorisation and settlement is already a ledger entry, so reporting and accounting come out of the same record as the money, 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 authorised.
Concept
Operations treasury
Ethereum2 of 3 signatures required to release funds
Vendor payment: Northwind Cloud
42,000.00 USDC
1 of 2 required signatures collected.
- 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.
- Allow a merchant category, send it for approval, or block it outright.
Concept
Engineering spend policy
Engineering- Per transaction
- 2,500.00 USDC
- Daily
- 7,500.00 USDC
- Monthly
- 40,000.00 USDC
- Approval above
- 1,000.00 USDC
Allowed categories
SoftwareCloud hostingTravel
Blocked categories
Cash advanceGambling
Merchant category controls
Engineering- SoftwareMCC 5734
- Cloud hostingMCC 7372
- Travel agenciesMCC 4722
- RestaurantsMCC 5812
- Cash advanceMCC 6010
Approve sends the purchase to an admin before it is authorized.
A card that draws on the authorised amount.
- A limit on one card, with the status spelled out beside the meter.
Concept
UnifractionVirtual
UnifractionVirtual•••• •••• •••• 4417
Design
Nijat Mayilov
Expires
01/29
Monthly limitOn track
1,240.50 of 5,000.00 USDC
25% used · resets 1 October
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.
Concept
Settling on-chain
Ethereum42,000.00 USDC
- AuthorizedSigners approved
- BroadcastSent to Ethereum
- Confirming7 of 12 confirmations
- SettledFinal on-chain
Transaction0x9f31ac…a31f28
Roles decide who sees and approves what.
- Roles, and what each one may do.
Concept
| 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 |
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 authorisation rules apply as to a card.
curl https://api.unifraction.io/v1/agents/ag_4417/wallet \
-H "Authorization: Bearer $UNIFRACTION_KEY"Illustrative only. The address 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 authorisation 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.
Questions
Something we have not covered here?Email hello@unifraction.io
What is Unifraction?
One platform for a company’s on-chain money: stablecoin wallets, treasury, the cards and agent wallets that spend from them, and the reporting and accounting that follow. Today those are four tools and a spreadsheet.
Is any of this live?
No. Unifraction is at the idea stage. Everything on this page is design work: the screens are concepts and every figure in them is invented. The waitlist is how we find out who wants it built.
Who is it for?
The finance team at a company that already holds stablecoins. A CFO, or someone reporting to them, sets up the wallets, names the signers and decides who may authorise what.
Where do the funds sit?
On-chain, in wallets the company controls. We are not designing a custodial balance with an on-chain veneer: the wallet is the account.
How is spending authorised?
An admin authorises an amount for a card or an agent wallet. Depending on how that wallet is configured this needs one signature or several, and the request stays pending until the threshold is met.
How does settlement work?
When a payment happens, the authorised amount settles against the wallet. Who the settlement partner would be has not been chosen yet.
What is an agent payment wallet?
A wallet that belongs to a software agent rather than a person, with its own limit and its own ledger. It pays for what it calls using x402, the HTTP 402 flow for per-request payment. Which facilitator it would use is not decided.
Can we stop payments to sanctioned merchants and wallets?
That is the intent: an admin turns monitoring on, and payments to screened merchants and addresses are blocked before they leave. Which screening provider would do this, and what it would and would not cover, is not decided.
What about licensing and compliance?
Unifraction is an idea, so what permissions it would need, and who would hold them, is not decided. This page makes no claim about licensing or compliance.
What happens when I join the waitlist?
We email you when there is something concrete to show, and we may ask how your team handles treasury and spend today. No newsletter, and you can ask us to remove your address at any time.
Join the waitlist
Tell us where you would use it. We will get in touch when there is something to show.
What we would like to know
- 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.
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 address, your company if you give one, the time you agreed, and a scrambled form of your network address, kept only to limit repeat submissions. 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, and you can ask at any time.