Policy Engine
Set spending limits, approved recipients, and approval requirements for your agents. Conto checks each payment request against your rules.
One policy check, two execution paths
Conto decides, the wallet sends · Conto holds the rules and the record
Agent requests a payment
POST /payments/requestConto checks owner policy
Owner’s approver decides
Routine spend skips this step.
Buyer wallet sends funds
Once the request clears, the managed wallet signs and sends. Conto holds the decision and the record.
POST /payments/:id/executeLogged with full context
tx 0x9f2c… ✓
policy · approval · settled
Agent keeps its own keys · Conto authorizes, logs on confirm
Agent asks to authorize
POST /payments/approveConto checks owner policy
Owner’s approver decides
Routine spend skips this step.
Buyer’s signer sends
Conto returns a 10-minute approval. The agent sends the transaction.
Agent reports the transaction ID
POST /payments/:id/confirmtx 0x9f2c… ✓
policy · approval · settled
Same payment context, same policy evaluation, same audit trail. Who signs and sends is where the path diverges.
Choose your spending rules
Check each payment request against your spending rules.
Spend limits
Set per-payment and period budgets. Add limits for a recipient, category, or project.
Recipient rules
Allow approved recipients, block excluded addresses, and review new recipients.
Payment frequency limits
Limit repeated payment requests and retries within a set period.
Approval thresholds
Pause payments above your thresholds and show the reviewer which rule requires approval.
Set up payment checks
Configure rules
Assign rules to each agent and payment source through authorized owner access.
Evaluate every request
Connect your payment tools to send Conto the amount, recipient, and purpose.
Return a clear decision
Your payment system follows the decision: proceed, stop, or wait for approval.
Test a purchase against your rules
Try a purchase, then change its amount or recipient to test the checkout rules. Payments use test funds.
$300
$100
Food · shopping · tickets · apps
What your team can control
Limits apply to payments made through the connected payment system. External signers must require authorization before sending.
Update spending rules in Conto.
Payment controls in practice
Approvals for payment exceptions
Decide which payments need a reviewer before they can proceed.
ExploreVendor and counterparty controls
Pay approved vendors automatically. Review payments to new, changed, or risky recipients.
ExploreBudgets for paid API calls
Set spending limits per request and per session for API, inference, and compute usage.
Explore