Tutorial · live today
Treasury USDC
→ spending on your card.
A 5-minute, one-time setup. After that, send funds with no MetaMask — or let AIBIZ auto-sweep on a schedule.
A 5-minute, one-time setup. After that, send funds with no MetaMask — or let AIBIZ auto-sweep on a schedule.
Every .aibiz name comes with its own ERC-6551 wallet (a "treasury"). Revenue from agents living under the name lands there in USDC. To spend that USDC at a real merchant, you don't withdraw to a personal wallet and then to an exchange and then to a card — AIBIZ moves the USDC directly into the wallet your card provider already monitors. When you swipe, the provider converts USDC → USD on the fly. No new account, no KYC for AIBIZ to handle, no extra hop.
Five steps total. The first three are one-time setup (~5 min). The last two are how you use it forever after.
Visit my-domains.html and click Sign in with email. We email you a single-use magic link (15-minute TTL). Click it, and you're authenticated for 24 hours — no password.
No MetaMask needed for this step. Sign-in is what unlocks the "send now" and "auto-sweep" buttons later. Your email is also matched against the wallet that bought the SLD originally.
In the Linked cards section, click + Add a card. Pick your provider (Coinbase Card, Crypto.com Card, etc.), paste the funding wallet — the Polygon address your card provider already watches for deposits — and sign once with MetaMask to prove you own the card-linking wallet.
Where to find your funding wallet: Coinbase → Send & Receive → USDC → Polygon network → "Your USDC address." Same idea on Crypto.com. Copy that address.
Click authorize off-ramp on the card row. The 3-step wizard collects exactly three signatures, all from the wallet that owns your SLDs:
After this, the on-chain AIBIZSweeper contract enforces the rules. AIBIZ's operator key cannot exceed your cap, cannot redirect to a non-allowlisted wallet, cannot drain your treasury — even if our server is compromised.
Click send now on the card row. Pick which treasury, enter an amount, click Send. No MetaMask. AIBIZ's operator key signs the on-chain tx and pays the gas. You see a Polygonscan link the moment it confirms.
Use this for ad-hoc top-ups: "I'm about to spend $500 at Costco, push $500 to my card."
Click auto-sweep. Set a rule like "every week, send everything above $100 to my Coinbase Card." AIBIZ checks every 5 minutes and fires the sweep when the schedule is due.
Modes: above-threshold (sweep excess) or fixed (send a set amount). Pause / resume / delete any time. Failures (e.g. you removed the card) show as last err on the rule.
Coinbase / Crypto.com sees USDC arrive at your funding wallet (1–5 min after the on-chain confirmation). When you swipe at any merchant, the provider auto-sells the USDC for USD on their books at spot price, settles to Visa/Mastercard, you get your latte.
AIBIZ's involvement ends when the USDC arrives. The conversion fee (~1%) is the card provider's, not ours. Same fee you'd pay if you topped up your card manually.
Routes that don't have crypto rails. AIBIZ collects your USDC, settles in fiat off-chain, and tracks the request through every stage.
Use the auto-sweep / send-now flow above if you have a Coinbase / Crypto.com card — it's instant and needs no operator involvement. The manual route is for everything else.
In My Domains → Manual payouts → + Request payout. Pick destination type, paste account details, enter amount.
We show you the collection wallet 0x3b92d6C2…536451d. Send the exact USDC amount on Polygon.
Our on-chain detector watches the wallet every minute. When your USDC arrives + matches your request amount, status flips to payment_received.
AIBIZ OTC-sells the USDC and ACHes/wires the USD to your destination. Status moves through processing → completed, with the bank/Mercury confirmation # attached as a remark.
Banking rails are slow. ACH settles overnight. International wires need correspondent banks. Mercury accepts ACH inbound only. AIBIZ doesn't have a faster path here — nobody does. We make the wait visible (status + remarks at every stage) and hands-off after step 2.
AIBIZ's job is identical across providers — drop USDC into the funding wallet on Polygon. What happens next varies.
| Card | What "funding wallet" means | USDC → USD happens... |
|---|---|---|
| Coinbase Card | Your USDC deposit address inside Coinbase (Polygon network) | at swipe time, Coinbase auto-sells your USDC for USD on their books |
| Crypto.com Card | Your USDC deposit address inside the Crypto.com app (Polygon network) | same model — swipe triggers Crypto.com's internal conversion engine |
| Mercury (team-only) | A USD-only fintech bank — no crypto rails | v1 is operator-only manual OTC + ACH. Not for end customers yet. |
| Other (any wallet) | Any Polygon address you control | you handle the off-ramp yourself (e.g. send to a CEX, withdraw fiat) |
| Lithic-future (roadmap) | An AIBIZ-issued debit card; treasury debited at swipe time directly | no off-chain hop — collapses steps 4 + 5 into one |
Why this design: regulated rails (KYC, banking, MCC routing, dispute handling) cost millions to operate. Your card provider already paid that price. AIBIZ inherits all of it for free by dropping USDC into the wallet they already monitor.
We're the on-chain rails. The card rails belong to your card provider.
AIBIZSweeper)"Server-side signs the sweep" sounds scary. Here's the math — the worst-case attacker who steals our operator key still can't move funds outside your rules.
The sweeper contract only accepts a recipient that the SLD owner personally allowlisted. Stolen operator key → can call sweep() → but only into your card's funding wallet. Attacker can't redirect funds to themselves.
Sweep amount above maxSweepPerTx reverts. You set this in the wizard (default $1000). Even with the operator key, the worst they can do is move $1000 every block — and you'd see it on Polygonscan immediately.
Open the wizard, set cap to 0 — sweeps blocked instantly. Or open MetaMask, set the TBA's USDC allowance to 0 — same effect, in one signature. No phone call to AIBIZ needed.
If you sell the SLD on OpenSea, the new owner inherits an empty approval set. Your old card stays harmless even if the buyer has the same address by coincidence — they'd have to re-run the wizard from scratch.
Sweeper contract: 0xe1b71f49…d65C · verified source on Polygonscan · 17 unit tests cover the rules above.
Sign in with email, link your card, run the wizard once. Then forever after, treasury USDC moves to your card with no MetaMask.