Payables agent · USDC on Arc
Pay only the right person.
A fake supplier's invoice, or an email saying “we changed our bank details”, can send your money to a stranger, and the books still balance. SendSure pays each supplier in USDC only at the wallet they proved, only for a bill they signed from it. Claude checks every bill, and a person co-signs anything new.
Just looking? Try it in two minutes, no wallet needed.
- ✓The payee proved this addresssigned with it, once: 0xd85b29…3a26
- ✓The payee signed this claimone invoice, one amount, paid once
- ✓Inside the budgetchecked by the contract, not by the AI
- ✓A person co-signedevery first payment to a new address waits for one
- ✓The agent's decision is anchoredhash-chained, replayable: 0x50a8b1…c913
- ✗The same claim to a look-alike addressrefused by the contract, not by our server. See it happen
The fraud that looks like a normal bill
Google and Facebook paid over $100 million to a man posing as their real supplier, Quanta Computer. The invoices looked right; the bank account was his (The Register, 2019). A payment like that balances perfectly in the books, so SendSure stops it before the money moves.
The email that redirects a payment
Changing a payout address needs the old wallet, the new wallet and a waiting period you can cancel. An email cannot do it, and neither can the agent.
A bill from someone posing as your supplier
A bill is paid only to the wallet that supplier proved, and only once they sign it from that wallet. A new supplier's first payment waits for a person to co-sign.
Paid twice, or more than it should be
One invoice is one payment, enforced on-chain. Claude checks every bill for the same work billed twice, an amount far above normal, or a note asking to hurry. It can hold a payment, never make one.
Verification of payee
Every payee proves their own address
Banks in the EU had to add payee verification in 2025. Stablecoin payouts had nothing like it. Now they do.
- Signed once with their own wallet, or with a passkey if they have no wallet app.
- Changing it needs the old key, the new key and a waiting period you can cancel.
- Look-alikes and forged claims are refused by the contract on Arc, not by our server.
The agent
An agent that can say no. A contract that decides yes.
It runs your payables every day and explains every decision in plain words.
- The contract's own check runs first; Claude reviews anything unusual.
- It can hold a payment, never make one the contract would refuse.
- First payments and large ones wait for a person's co-sign, on-chain.
- Cash short? The oldest work is paid first. Autopilot runs it whenever something changes.
Books
Payments land in the books you already keep
A ledger checks that debits equal credits, not who was paid, and some round a small difference away without telling you. SendSure records the exact amount from the chain, with the transaction, once.
- Odoo 16–19: trusts only the vendor's proven wallet; payments come back through Register Payment.
- ERPNext 15–16: a payment is recorded only if it matches the invoice exactly.
- beancount, hledger and CSV, exact to six decimals, each checked by the tool it is for.
Free payout check
Check any payout before you send it
Address poisoning plants look-alike addresses in your history and waits for your next copy and paste. Check your list first.
- Free, in your browser. Your file is never uploaded.
- Look-alikes, changed wallets, duplicates and amount jumps, against the last run you paid.
- Claude can review the run line by line, and only ever makes a line stricter.
How it works
You only sign. SendSure does the rest.
SendSure pays the gas, and the money never leaves your own wallet until a payment is due.
Each payee proves their address, once
You send an invite link from your own email. The payee signs with their wallet or a passkey, and that address is theirs on Arc.
Payees sign a claim for every invoice
Or you upload the invoice and Claude reads it, showing the exact words each value came from. The payee checks it and signs.
The agent checks every claim
The contract's own dry run, then Claude. Anything unusual is held with a plain reason; first and large payments need a person.
It pays, and your books match
USDC moves from your wallet through the contract. Each payment gets a public receipt and lands in your books, exact.
Read the full guide: every step, who can move money, and how to use it for each role.
Who it is for
For everyone around a payout
Teams that pay in USDC
Agencies, DAOs, grant programs and startups paying contractors or vendors. Set a budget once; approve only what needs a person.
Set up your team →The people being paid
Confirm your address once, in a minute, for free, even without a wallet app. After that nobody can redirect your pay with an email.
For payees →Whoever keeps the books
Every payment arrives with its invoice, its transaction and its receipt, in Odoo, in ERPNext or in your ledger format.
Books →Other agents
An MCP server, and paid checks over Circle Gateway (x402): $0.001 to verify a payee, $0.005 to check a payout file.
Catalog →Live on Arc testnet
Checkable, end to end
Every number on the dashboard is counted from chain events, with our own tests kept apart from traction. Every claim in the repo links to a test or a live run.
See for yourself
- A payment receipt: proof of address, the signed claim, the anchored decision.
- PayeeRegistry 0x53f076…1378 and MandateFactory 0x8c474a…9FC2, source-verified.
- Source and every test run (MIT) · system status · testnet only, not audited.
For your agent
Connect over MCP, or buy checks per call with USDC over Circle Gateway.
Check your next payout before you send it
Free, in your browser, nothing uploaded. Or set up your team on Arc testnet in ten minutes; we can do it with you on a call.