EconomicoStablecoin payments
Normal invoices. Stablecoin settlement. Clean books.
Invoice in dollars and let clients settle by bank transfer or in stablecoins — USDC, USDT, PYUSD — over a link, email, or the Notabene Flow rail. Each stablecoin gets its own cash account, so on-chain revenue lands as clean, auditable books.
"The reconciliation back to the original invoice is worse"
That's how founders describe accepting stablecoins today: "I send a normal invoice and just include the wallet address" — the easy part — and then "the reconciliation back to the original invoice is worse." Money lands on-chain, but nothing ties it to the dollar invoice you sent. So you refresh a block explorer by hand to confirm it arrived, guess a dollar value for the day, and write a spreadsheet line. In QuickBooks or Xero, every stablecoin settlement is a manual journal entry against a cash account that was never built for it. The payment was instant; the bookkeeping is the slow, error-prone part.
Invoice in dollars, settle in USDC, and it reconciles itself
Here's the whole loop in one ask. You invoice Acme $5,000 in dollars and send a link they can settle in USDC. They pay. You record the settlement against its transaction hash — and your agent books it: it clears the receivable, marks the invoice paid, and posts the incoming USDC to the right cash account, with the dollar value fixed at settlement. The invoice and the on-chain payment are tied together in the ledger, not in your head.
Invoice Acme $5k and send a payment link they can settle in USDC. Once it's paid, record the settlement against this transaction hash.
Each stablecoin gets its own cash account in the ledger
A fiat invoice settling in stablecoin isn't a bolt-on here — it's the native data model. Cash USDC, USDT, and PYUSD each live as their own distinct line in the general ledger, alongside your bank cash. On-chain revenue lands as its own sub-balance rather than a lump you have to untangle later. Send however the client prefers — a shareable link, an email, or the Notabene Flow rail — and when both sides are on Flow, the invoice, payment, settlement, and ledger entry all happen without either of you leaving your agent.
Year-end: on-chain revenue that your accountant just accepts
The reason the per-stablecoin cash account matters isn't the moment of payment — it's April. Because every settlement already posted to a real ledger with a dollar value at the time it arrived, your accountant opens a clean trial balance instead of a wallet address and a folder of screenshots. On-chain revenue is auditable the same way your bank revenue is, on one connected ledger rather than a spreadsheet bolted onto your accounting tool. And recording an on-chain payment is idempotent — if your agent repeats the call, the settlement is never double-posted.
"Does it watch the chain and post payments for me?"
Not yet — and that's the one honest caveat. Today you record a settlement with the transaction hash you hand it, and your agent books it to the right stablecoin cash account. We don't watch the chain and post automatically; that automatic reconciliation is on the roadmap, not live. Everything else is real now: invoicing in dollars, sending by link, email, or Flow, and per-stablecoin cash accounts, all posting to a real ledger. And no, you don't have to be a crypto business — you invoice in dollars; stablecoin is simply a settlement option for clients who prefer it.
Get started
Settle in USDC. Reconcile itself. Close in dollars.
Connect the agent you already use and let clients pay the way they prefer — while your books stay clean.