USDC payments & names · on Arc
Get paid in USDC.
One link. One name.
Zunivo turns USDC on Arc into programmable revenue: payment links anyone can pay, .zunivo names anyone can remember, wage-grade committed sends, automatic revenue splits — and rails that machines can use as easily as humans. Settled in under a second. Never held by us.
Live on Arc Testnet · contracts verified · zero-custody by construction
Receipt
paidsettlement finality on Arc
verified zero-custody contracts — settlement, identity, commitment, splits
fee, hard-capped in verified contract code (currently 0%)
gas is USDC too — no second token to buy
What Zunivo does
Three things a transfer can't do
USDC moves value. Running a business needs more: knowing whose money, for what, whether it's the right amount — and proving it later. Zunivo is that layer.
Payment links
Create an order, share one short link or QR. The payer opens it and pays from any wallet — or with no wallet at all, using a passkey and Face ID. Funds land in your wallet, not ours.
Create a link →Zunivo Names
yourname.zunivo — an NFT that routes money. Fully on-chain art and metadata, tradable, and payments sent to the name follow whoever holds it. Your address becomes a brand.
Mint yours →Receipts & reconciliation
Every payment binds to an order on-chain, so matching is automatic: live paid / unpaid status, a shareable receipt page for both sides, and a CSV your accountant will actually accept.
Open the dashboard →The honest question
"Why not just send USDC directly?"
You can. A transfer moves the money — and leaves you doing the bookkeeping by hand. Here's the same payment, both ways.
A raw transfer
- Fifty deposits, one address — which payment was which invoice?
- Copy a 42-character address by hand and hope
- Your "receipt" is a transaction hash
- Who underpaid? Who never paid? Nobody knows
- New customers need a wallet, gas, and a tutorial
The same payment on Zunivo
- Every payment matches its order automatically
- Amount and destination locked inside the link — or just say a name
- A receipt page both sides can keep and share
- Paid / unpaid live, CSV export for the books
- No wallet? A passkey and Face ID is enough
How it works
From "pay me" to reconciled, in three steps
Create
Enter an amount and a memo. Your wallet — or your .zunivo name — is the destination. Zunivo issues the order and a short link.
zunivo.io/pay?oid=60eeafd3Share
Send the link or QR anywhere: an invoice, a chat, a bio. The payer opens it and confirms. Gas is USDC too, and can be sponsored.
Settled
Money lands in your wallet in under a second. The order flips to paid, the receipt is issued, and your CSV already knows.
One network, four verbs
Every way money needs to move
Each verb is its own verified contract — small enough to read, strong enough to promise.
Get paid
Links, QR codes, machine-issued invoices. Any wallet pays — or no wallet at all, with a passkey and Face ID.
Create a link →Send
Pay anyone by name or address, settled in under a second, with a receipt both sides keep.
Send now →Commit
Payroll-grade scheduled sends: locked on-chain until a date, irrevocable once made — the recipient watches the countdown, and not even Zunivo can touch it.
Schedule →Split
One payment, divided atomically between up to 20 recipients on immutable terms. Platforms, co-creators, referral shares — everyone gets their cut and their receipt.
Create a split →Zunivo Names
A name that money answers to
- The art and metadata are generated by the contract itself — no server, no IPFS, nothing to go dark
- It's an ERC-721: sell it, gift it, hold it. Payments follow the holder automatically
- Works everywhere in Zunivo: receive with it, get paid to it, look up your books by it
- 3–20 characters · a-z, 0-9, dashes · first come, first served
Built for what's next
Machines pay machines here
The next customers aren't people clicking "buy" — they're AI agents calling paid APIs, SaaS metering by request, and plugins earning revenue shares. Zunivo gives them rails: an API that issues orders, a 402 paywall any endpoint can adopt in three lines, and a settled, auditable receipt for every single call.
Every call above is a real flow we run today on Arc Testnet — an autonomous agent discovering a price, paying from its own wallet, and collecting an auditable receipt. No card networks. No human in the loop.
Trust, verifiable
Don't trust our word. Read the contracts.
Zunivo's rails are four small, verified contracts — settlement, identity, commitment, and splits. Payments pass through atomically; committed sends sit in keyless code with no admin path. There is nothing for anyone — including us — to hack, freeze, or run away with.
- Non-custodial by construction — the router forwards funds in-transaction and can't hold a balance
- Fee hard-capped at 1% in on-chain code, currently 0% — a promise you can read, not one you take
- 35-test suite with fuzzing and reentrancy probes; Slither static analysis: zero high or medium findings
- Independent security review scheduled before mainnet
Questions
Do my customers need a crypto wallet?
No. Any EVM wallet works — Zunivo adds the Arc network for them automatically — or they can pay with no wallet at all: a passkey (Face ID / Touch ID) creates a secure Circle smart account on the spot.
What does Zunivo cost?
Free during testnet. At mainnet, a protocol fee of up to 1% on payments — the cap is enforced by the contract, not a promise — and 1 USDC to mint a name.
Why is Zunivo on Arc?
Arc is Circle's chain built for money: USDC is the native gas token and settlement is deterministic and sub-second. It's the first place a stablecoin checkout can feel like a card payment.
Can a scheduled send really never be taken back?
If it was created in committed mode — correct. Before unlock, no function exists that can move it: not for the sender, not for the recipient, not for Zunivo. After unlock, release is permissionless but funds can only flow to the recipient fixed at creation. It's enforced by code you can read, and proven by our public test suite.
Can split percentages be changed after a link is shared?
Never. A split's payee table is immutable from the moment it's created — the terms your collaborators saw are the terms that execute, forever. Need different shares? Create a new split.
Is a .zunivo name a real domain?
It's an on-chain payment name, not a DNS domain: an ERC-721 on Arc that any app can resolve permissionlessly. Inside Zunivo it works everywhere you'd otherwise paste an address.
Get paid. Send. Commit. Split.
All on rails you can read.
Payment links, committed payroll, automatic revenue shares, machine-payable invoices — live on Arc Testnet today, non-custodial by construction.