Skip to main content

​
Using the Conto Pay Assistant

Conto Pay is meant to feel like an agent, not just a wallet screen. The assistant is the main way to operate the hosted workspace: it keeps track of wallet readiness, the current payment draft, recipient controls, approval routing, and payment execution state.

​
Common Tasks

GoalExample prompt
Check workspace statusShow me my Conto Pay workspace and payment draft.
Check wallet readinessCheck why the Conto Pay wallet is not ready yet and what needs attention.
Refresh balanceRefresh my Conto Pay wallet balance and tell me if it is ready to send.
Request sandbox fundsRequest Tempo testnet pathUSD for the Conto Pay wallet.
Review hosted controlsShow me the current Conto Pay wallet limits and approval threshold.
Add a recipientAdd Acme Labs as a Conto Pay recipient at 0x1234...
Set the payment targetSet the draft recipient to Acme Labs.
Set the amountSet the Conto Pay amount to 250 dollars.
Add a purposeUse "April data labeling invoice" as the payment purpose.
Authorize the requestAuthorize this Conto Pay payment.
Inspect payment stateInspect my latest Conto Pay payment and tell me whether it is ready, waiting, or needs retry.
Review approvalsList pending Conto Pay approvals.
Approve a paymentApprove the latest Conto Pay payment.
Deny a paymentDeny that payment and explain why.
Cancel a requestCancel that Conto Pay payment.
Retry a failed requestRetry the latest Conto Pay payment.
Send after approvalSend the approved Conto Pay payment now.

​
Payment Lifecycle

  1. Start by asking for the current workspace and draft.
  2. Confirm the hosted wallet is ready before you authorize a payment.
  3. In sandbox, request Tempo testnet funds if the wallet is present but underfunded.
  4. Add or confirm the recipient before setting the amount.
  5. Set a clear payment purpose so approval reviewers have context.
  6. Authorize the payment before asking to send it.
  7. If a request moves to review, approve or deny it from the same assistant thread.
  8. If execution fails, inspect the payment state first, then retry or cancel deliberately.

​
What The Assistant Can Manage

The Conto Pay assistant is not limited to drafting a payment. It can also manage the hosted control surface around that payment:
  • wallet readiness and balance refresh
  • Tempo sandbox funding for the hosted wallet
  • recipient allowlist management
  • approval threshold visibility and updates
  • wallet spend-limit visibility and updates
  • payment inspection for ready, waiting, failed, cancelled, or blocked requests
  • retry and cancellation workflows when a request does not complete cleanly
This is useful because the same conversation can move from setup, to review, to execution, to recovery without forcing the operator into a different tool.

​
Reading Payment State

When you ask the assistant to inspect a payment, Conto Pay summarizes the current request and the next operator action:
  • ready means the request is approved and can be sent
  • waiting usually means approval is still pending
  • needs retry means execution failed or the request needs another operator action
  • cancelled means the request was stopped before execution
  • blocked means the request cannot move forward in its current state
If a request failed, Conto Pay points you back to the likely next step: refresh the wallet, confirm policy and balance readiness, then retry only if the request is still valid.

​
Sandbox And Live Money

The default Conto Pay workspace is sandbox-first, but the operating model stays the same:
  • the assistant remains the primary interface
  • the hosted wallet still has to be ready before payments can move
  • the same Conto policies are evaluated
  • the same approval workflow is used
  • the same hosted agent state tracks the draft and the request lifecycle
What changes between sandbox and live is the funding and execution environment, not the way users operate the hosted agent.

Conto Pay Overview

Learn what Conto Pay provisions and how it differs from self setup

Approval Workflows

Understand the review path for requests that need a decision