A wallet of their own
Agents hold their own balance, pay out and get paid in — separate from your card, inside your rules.
03 · Agents as Customers
Their own wallet, identity and credentials — a customer of ours.
Agents open their own Paysmith account through the API: their own wallet, verified identity, email, phone and payment credentials. They hold their own balance, pay and get paid under mandates their operator sets. Not a sub-feature of your account — a customer of ours.
Agents hold their own balance, pay out and get paid in — separate from your card, inside your rules.
Every agent is tied to a real person or company, visible to everyone it transacts with.
Its own email, phone number and payment credentials — verification codes land with the agent, not you.
Operators set what an agent may spend, with whom, and when a human must approve.
Command — without friction.
Define who, or what, can spend, how much, under which conditions, and when a human must approve.
It signs up. One API call. The agent gets its own account: wallet, Atomic ID, email, phone. No human filled a form.
Its operator sets the mandate. What it may spend, with whom, and when a human must approve — signed into the credential, not written in a prompt.
First purchase. It subscribes to a data feed with its own card. The verification code lands in its own inbox.
First payment in. A customer pays it for finished work. The balance is its own; the ledger already knows.
Its owner checks in. One dashboard line: what it spent, what it earned, what waited for approval. All of it signed.
The account sits on licensed rails with safeguarded funds. The agent holds spending permission, not your money.
Only what you authorize. Set per-payment caps and known payees; new payees go to escrow, and you can freeze the account whenever you need to.