Skip to content
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.

VirtualUnifraction

•••• •••• •••• 4417

Card holderNijat MayilovFrom01/25Thru01/29

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

The funding a YC-funded startup can choose to receive in stablecoins, such as USDCSource: Y Combinator’s announcement on LinkedIn, February 3, 2026
Why now

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.

Source: CoinDesk, September 8, 2026

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.

Today

5 tools, 5 records

Examples of the tools a team reaches for.

  1. ReceiveExchange account
  2. HoldWallet
  3. ControlChat approvals
  4. SpendTransfers
  5. AccountSpreadsheet
The idea

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
  1. 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.

  2. 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.

  1. 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.

  2. 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.

  1. 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.

  2. 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.

  3. 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.

  4. 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.

Authorize

The signers agree an amount first.

  • Two of three signatures before an amount is authorized.
Concept
Operations treasury
BNB Chain
2 of 3 signatures required to release funds
Vendor payment: Northwind Cloud
42,000.00 USDC
1 of 2 required signatures collected.
  • Priya Nair
    Head of finance
    Signed
  • Marcus Bell
    CFO
    Awaiting
  • Lena Ortiz
    Controller
    Awaiting
Set the rules

Decide where and how much a card or agent can spend.

  • The limits and merchant rules behind a card or an agent wallet.
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 hosting
Blocked categories
Cash advance
Choose merchants

Allow, ask or block each kind of merchant.

  • Allow a merchant category, send it for approval, or block it outright.
Concept
Merchant category controls
Engineering
  • Software
    MCC 5734
  • Cloud hosting
    MCC 7372
  • Travel agencies
    MCC 4722
  • Restaurants
    MCC 5812
  • Cash advance
    MCC 6010
Approve sends the purchase to an admin before it is authorized.
Spend

A card that draws on the authorized amount.

  • A limit on one card, with the status spelled out beside the meter.
Concept
UnifractionVirtual
•••• •••• •••• 4417
Design
Ada Okonkwo
Expires
01/29
Monthly limitBNB ChainOn track
1,240.50 of 5,000.00 USDC
25% used · resets October 1
Settle

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
BNB Chain
42,000.00 USDC
  1. Authorized
    Signers approved
  2. Broadcast
    Sent to BNB Chain
  3. Confirming
    7 of 12 confirmations
  4. Settled
    Final on-chain
Transaction0x9f31ac…a31f28
Manage access

Roles decide who sees and approves what.

  • Roles, and what each one may do.
Concept
Team members, their roles and what each role may do.
MemberRoleCanLast active
Priya Nair
priya@northwind.example
OwnerEverything, including billing and signer changesToday
Marcus Bell
marcus@northwind.example
AdminIssue cards, set limits, invite membersToday
Lena Ortiz
lena@northwind.example
ApproverApprove spend requests and releasesYesterday
Ada Okonkwo
ada@northwind.example
MemberUse their own card and file expenses3 days ago
Sam Iyer
sam@northwind.example
ViewerInvite pendingRead reports onlyInvite pending
  • Priya Nair
    priya@northwind.example
    Owner

    Everything, including billing and signer changes

  • Marcus Bell
    marcus@northwind.example
    Admin

    Issue cards, set limits, invite members

  • Lena Ortiz
    lena@northwind.example
    Approver

    Approve spend requests and releases

  • Ada Okonkwo
    ada@northwind.example
    Member

    Use their own card and file expenses

  • Sam Iyer
    sam@northwind.example
    ViewerInvite 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

x402.httpBNB ChainhttpConcept
GET /v1/forecast HTTP/1.1
Host: data.example.com
HTTP/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 OK

Illustrative only. The addresses, amounts and identifiers are invented, and this is not a published interface.

  1. The agent calls a paid service

    A request for something the service charges for, such as data or compute.

  2. The service answers 402

    HTTP 402, Payment Required, with the price. This is the x402 flow.

  3. The wallet checks the limit

    The agent’s wallet checks its own limit and the authorization rules before it pays.

  4. 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?

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 that takes five separate tools, one of them 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 holds stablecoins, or soon will: funding that arrives in USDC, a vendor who asks to be paid in it, an agent that pays for the services it calls. A CFO, or someone reporting to them, sets up the wallets, names the signers and decides who may authorize what.

Where do the funds sit, and who holds the keys?

On-chain, in wallets the company controls. The finance team names the signers, and every amount would be authorized with their signatures. In the design, the balance and the keys stay with the company: the wallet is the account. How a lost key would be recovered is not decided.

Which stablecoins and networks?

The concept screens show USDC on BNB Chain, and the diagram of the platform adds USDT, because a design needs real examples. Which would be supported first is not decided.

How is spending authorized?

An admin authorizes 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 authorized amount settles against the wallet, on-chain. A card payment still reaches the merchant through the card network, in its own currency, so a settlement partner would stand between the wallet and the network. Who that partner would be has not been chosen yet.

Would it replace our accounting software?

The idea is that every authorization and settlement would already be a ledger entry, so the records your books need would sit in one place. How they would reach your accounting software, by export or by a direct connection, is not decided.

Is a stablecoin balance cash on our books?

That is for your accounting policy and your auditors to decide, and standard-setters are still working on the question. What the design would do is keep every movement in one record, so whichever way it is decided, the books start from the same place as the money.

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, the service that checks and settles each payment, it would use is not decided.

What stops an agent from spending too much?

The same thing that stops a card: an agent wallet would only spend against the amount an admin has authorized for it, within its own limits. Not decided yet: how an admin would pause one at once.

Can we stop payments to sanctioned merchants and wallets?

That is the intent: an admin turns monitoring on, and payments to sanctioned merchants and addresses are blocked before they leave. Not decided yet: which screening provider would do this, and what it would and would not cover.

What about licensing and compliance?

Unifraction is an idea, so what permissions it would need, and who would hold them, is not decided: both depend on choices still open, such as the settlement partner. 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

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.

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.

Join the waitlist

Leave your work email, and we will get in touch when there is something to show.

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.

Read the privacy page