​

Conto Pay

Conto Pay is the hosted way to run agentic payments in Conto. Instead of wiring your own runtime, wallet, and approval flow, Conto provisions a managed payment agent workspace for you and exposes it through the dashboard and assistant. The hosted workspace now behaves like an operator console, not just a payment form. You can check wallet readiness, refresh balances, request Tempo sandbox funds, inspect payment state, retry failed payments, and tune hosted controls directly from chat.

​

What Makes It Different

​

What Conto Provisions

When you open Conto Pay, the workspace is created with:

• a Conto-managed payment agent
• a hosted wallet with readiness tracked in the workspace
• starter spend policies
• recipient allowlist controls
• an approval workflow
• assistant actions for wallet refresh, payment inspection, retry, and cancellation
• a pre-minted SDK key for optional later integration

The workspace starts in sandbox so teams can verify the experience with the same hosted control surface they will use when moving to live money.

​

Wallet Readiness

Conto Pay does not show the workspace as ready just because the page exists. The hosted agent still needs a provisioned wallet and enough balance to operate safely.

• the workspace shows whether the hosted wallet is ready to send
• if the hosted wallet is not ready, the assistant can explain what is missing
• on Tempo testnet, the assistant can request sandbox pathUSD for the hosted wallet
• once funded, you can refresh the wallet balance from chat before authorizing a payment

The goal is to keep setup, funding, and payment execution inside the same Conto Pay workflow.

​

How To Use Conto Pay

​

How Payments Are Initiated

Conto Pay is designed to behave like a hosted agent, so the assistant is the primary control surface. A user can tell the assistant to:

• explain whether the hosted wallet is ready
• refresh wallet balance
• request Tempo testnet funds in sandbox
• add a recipient
• set the payment amount
• explain the current draft
• show current wallet limits and approval threshold
• authorize a request
• inspect the latest payment request
• show pending approvals
• approve, deny, cancel, retry, or send a payment

Conto turns those operator instructions into the normal request, review, and execution flow rather than bypassing platform controls.

​

Hosted Controls

Conto Pay uses the normal Conto control model, but the hosted workspace exposes the most important operator controls directly in chat:

• recipient allowlists for who the hosted agent can pay
• approval thresholds for when human review is required
• wallet spend limits for per-transaction and daily controls
• payment inspection so operators can see whether a request is ready, waiting, failed, or blocked

This gives teams a managed surface without creating a separate rules engine or approval path.

​

Policy And Approval Model

Conto Pay does not use a separate rule engine. The hosted workspace still relies on the normal Conto controls:

• wallet policies
• agent policies
• recipient allowlists
• approval thresholds
• approval workflows

That means sandbox and live money can share the same control model even when the funding and execution environment changes.

​

Typical Sandbox Flow

In sandbox, a common first run looks like this:

1. Open Conto Pay and ask whether the hosted wallet is ready.
2. If needed, request Tempo testnet funds for the hosted wallet.
3. Add or confirm an allowlisted recipient.
4. Set recipient, amount, and purpose for the draft.
5. Authorize the request.
6. Inspect whether the request is approved, waiting for approval, denied, or ready to retry.
7. Approve, send, or retry from the same assistant thread.

​

Next Steps