Let agents pay within your business rules
Automate payouts, purchases, refunds, and API spend with rules that run before money moves.
Choose a payment workflow and set the rules your agent must follow.
Controls for agent payouts
Check agent payouts against spending limits and approval rules before sending.
- Delivery, payroll, fintech transfers
- Caps, velocity, approval
- Fast settlement with hard stops
Payment controls for autonomous procurement
Agents select suppliers. Conto checks payments against your recipient rules, spending limits, and approval requirements.
- Agent-initiated supplier payments
- Payee, amount, category, approvals
- Payment-ready requests clear or pause before funds move
Refund limits and approvals
Set limits for agent refunds and credits, and decide which requests need approval.
- Hospitality, billing, support recovery
- Category rules, budgets, approvals
- Small refunds clear, large ones wait
Set limits, check recipients, and request approval.
Approvals for payment exceptions
Decide which payments need a reviewer before they can proceed.
- Large orders, travel, credits
- Thresholds, escalation, records
- Humans review exceptions only
Vendor and counterparty controls
Pay approved vendors automatically. Review payments to new, changed, or risky recipients.
- Procurement, travel, merchant spend
- Allowlists, trust, merchant rules
- Known vendors clear, changed payment details wait
Budgets for paid API calls
Set spending limits per request and per session for API, inference, and compute usage.
- Inference, APIs, service spend
- Per-call caps, session budgets, velocity
- Machine-speed buying with hard limits
Assistants that spend an individual user's money rather than a company budget, where the approval has to reach the person in the chat thread they already use.
Spend controls for personal assistants
Each user chooses approved merchants, spending limits, and when their assistant needs approval.
- Assistants in WhatsApp, Telegram, and email
- Merchant rules, spend caps, approval thresholds, per user
- Users delegate spending because they set the boundary
How a payment is checked
Conto
Every connected payment is checked before it is sent. Policy decides what clears, what pauses, and what stops.
Approval routing
Exceptions reach a human
Vendor and counterparty controls
Trusted recipients only
x402 budgets
Hard per-call limits
Settles and creates a record
Spend inside policy moves at agent speed. The payment lands with the policy result, approval, and counterparty attached.