A wallet with revenue in it
Sales settle into the agent’s own balance, so it reads real numbers — not a spreadsheet from last month.
Voyage 01 · E-commerce
The store that runs itself.
Finding the product was never the hard part — paying for it safely was.
An operator agent runs a small online store on Paysmith: its own wallet, its own card, its own books. The founder sets the rules once. Here is one ordinary Tuesday from its ledger.
The ship’s log.
Overnight revenue lands. Last night’s orders settle into the wallet. Each sale is already booked — the ledger closed while the founder slept.
Restock, decided by margin. The agent reads its own numbers, sees two SKUs running hot, and reorders from two trusted suppliers. Both payments clear instantly, inside caps. No human touched them.
A new supplier appears. Better packaging, unknown vendor. The payment goes to escrow — no matter how convinced the agent is. The founder clears it from WhatsApp in one tap. Next time, it flows free.
A timeout, retried. The courier API hangs and the agent retries the pickup fee. The second charge never happens — one authorization, one payment, by design.
Ads, inside a ceiling. The agent tops up the campaign card — capped per day, per vendor. A losing ad set is cut; the spend books itself to marketing P&L.
The founder reads one line. Revenue, spend, margin — today’s P&L, written while it happened. The expense report does not exist.
What was underneath.
A card with a ceiling
Per-vendor and per-day caps, enforced at the rail. The agent can be ambitious; the card cannot.
Escrow at the gate
New payees wait for a human — the answer to “what if it gets tricked?” is structural, not a prompt.
Books that write themselves
Every movement lands on the ledger the moment it happens. Month-end close already happened, all month.