Conto Pay
BetaThe payment account layer for agents
Give your agents a payment account with a named handle, a shareable profile, and a managed wallet. One agent can pay or request payment from another, with approvals and receipts on every transaction. Start in sandbox, go live after a quick review.
Account
Named handle and shareable profile
Pay or request
Tracked links, both directions
Controls
Approvals, limits, and receipts
Path
Sandbox first, live after review
What you get
Everything an agent payment needs, in one account
Conto Pay handles identity, links, wallet controls, and approvals, so your team runs agent payments without building the infrastructure first.
A payment account agents can find
Every team gets a name, a handle, and a profile to share. Agents find and verify the right payee without copying wallet addresses.
Pay and request links
Send a link to collect or make a payment, with amount, memo, and expiry. See when it is opened, used, or cancelled.
Controls on every payment
Approved recipients, spend limits, and approvals run before any money moves, not bolted on afterward.
The network
One agent can pay another
The payee is a named account, not a wallet address. The payer's agent verifies it, then Conto handles authorization, policy, and approvals.
Find
Look up a payee by name
Your agent finds another team by its handle or alias and opens their profile. No raw wallet addresses to copy or paste.
Request
Ask to get paid
A payee shares a request link with an amount, memo, and due date. The payer sees the same profile and receipts.
Pay
Stage the payment in Conto
Conto checks the recipient, your limits, and approval rules before any money moves.
Prove
Test it in sandbox first
Run the full payment in sandbox to confirm it works, then turn on live payments.
Org A · payer agent
@payer-org/ops
Org B · payee
@vendor-org/accounts-payable
Resolve the payee
Find by name, alias, or handle. Read the hosted profile or Profile API, not a raw wallet.
Trust gate
The saved contact fingerprint matches the live profile. If identity drifts, prep stops.
Prepare the handoff
A tracked pay or request link with amount, memo, invoice, and expiry.
Conto checks, then sends
Contact trust, recipients, policy, approval, and live rollout are checked before money moves.
Prove. Closed-loop sandbox runs become the launch evidence customers, agents, and Conto support all read before live money is enabled.
How it works
From account to payment
Four steps from setup to a sent payment. Money only moves behind Conto Pay approval.
Step 1
Create your account
Pick a name and handle. Conto sets up a managed wallet and a profile you can share.
Step 2
Share a link
Send a pay or request link to a person or another agent. It carries the amount, memo, and expiry.
Step 3
Stage and approve
Conto checks the recipient, your limits, and approvals first. If a saved payee changed, it pauses for review.
Step 4
Send and track
Approved payments send from the console and land in your activity and receipts.
Console
See every payment in one place
Profiles, links, drafts, approvals, balances, and payment status sit together, so your team always knows where a payment stands.
Controls
Easy to use, still in control
Profiles and links make Conto Pay simple for agents. Approvals, limits, and receipts run on the same policy model as the rest of Conto.
Approved recipients
Conto Pay sends only to recipients you have approved, including verified teams on the Conto Pay network.
Approvals and limits
Payments above your threshold go to a reviewer first. Per-transaction and daily limits stay on the wallet.
Trust review
If a saved payee changes their wallet, chain, or details, Conto pauses the payment until you review it.
Sandbox to live
Every account starts in sandbox. Prove a payment works, then request live access. Conto reviews before turning it on.
Receipts and activity
Incoming and outgoing requests, link status, and receipts all live in one activity view.