Conto

Autonomous procurement

Payment controls for autonomous procurement

Agents select suppliers. Conto checks payments against your recipient rules, spending limits, and approval requirements.

Illustrative example

Supplier payment request

procurement-agent · Purchase order PO-1042

Helia Compute

$920.00

GPU capacity · approved supplier

Approved

Under $1,000 · compute category allowed

Unapproved supplier

$920.00

Same purchase · different recipient

Blocked

Supplier is not on the approved recipient list

The purchase order and policy decision follow the payment into reconciliation.

Controls at the payment boundary

Four rules, set by finance and checked on each request. A listed payee under the limit clears. A new payee, changed bank details, or an amount over the line waits.

Customer-approved payee rosters

Only authorize payment destinations your organization has approved, unless someone explicitly reviews the exception.

Payment category rules

Evaluate the category supplied by the procurement workflow against the agent’s allowed payment categories.

Per-payment limits

Put a hard ceiling on one payment request. Above it, the request escalates.

Approval-backed exceptions

Keep a manual gate for high-value requests, changed payee details, or payments that do not match the expected operating pattern.

Demo

Follow autonomous sourcing to testnet settlement

Simulated inventory, quotes, and purchase context produce a supplier payment request. A $920 restock clears and settles on Tempo Testnet. A $3,312 order crosses the $2,500 line and waits for review.