Separate spending rules for each customer
Each customer gets their own limits. Your agent asks Conto before it pays.
Use your own payment path, or let Conto buy
Your payment path
- API calls, supplier payments, your own wallet
- One agent
- Your backend, from your own settings screen
- Reviewers in your Conto workspace
- Your wallet or a managed wallet
Conto Commerce
- Buying from online stores
- One buyer
- The customer, on a Conto page
- The customer, on a Conto page
- The customer's own card
Live purchases need Conto to enable them for your organization.
From one customer to one payment
Your backend adds each customer once. Conto checks their rules on each payment request.
Add each customer
Create one agent for each customer with your organization key, and store your customer ID on it. For store purchases, create a buyer instead.
Set their limits
Your backend sets limits and allowed recipients. For store purchases, the customer sets limits on a Conto page.
Your agent asks Conto
Conto answers Approved, Needs approval, or Blocked under that customer's rules.
One agent, three customers, one $129 request
Example data. A request marked approved can be paid. It shows as paid once the payment confirms.
your-agent · $129.00
Customer A
$200 per purchase
Customer B
Approval above $100
Customer C
Tickets not allowed
What each customer gets
Your backend manages customers with one organization key. Agent keys can't loosen any rule.
Rules for each customer
Set per-payment and daily limits, allowed recipients, and categories for one customer. Rules you set for your whole organization apply to every customer as well.
Keys that can't loosen rules
Agent keys can't raise a limit or remove a rule. Your backend can, with your organization key.
Approvals
On store purchases, the customer reviews each purchase on a Conto page from a link you send. On your own payment path, requests that need approval go to reviewers in your Conto workspace.
Store purchases on the customer's card
The customer adds a card and confirms per-purchase and daily limits on a Conto page. Your keys can't add a card, grant permission to shop, or approve a purchase.
Records for each customer
Each payment request records the agent, recipient, amount, and policy result. Your customer ID is on the agent, so you can match them to your own records.
Checks in the payment path
On managed wallets and connected cards, Conto releases the signature or card details only after a request passes. If you use your own signer, x402, or MPP, your code asks Conto first and follows the answer.
Run one customer's limits through the demo
Under $100 the purchase clears. Above it, the agent stops and asks. A gift card is blocked.
Run the personal agents demoWhat you don't have to build
You add limits, approvals, and audit records for each customer without building them.
On store purchases, your platform and your agents never receive card details.
Your app can follow each purchase and payment through events and signed webhooks.
Support can look up a payment's recipient, amount, rules, and approval history.
Spending limits apply to payments made through the connected integration.