> ## Documentation Index
> Fetch the complete documentation index at: https://conto.finance/docs/llms.txt
> Use this file to discover all available pages before exploring further.
# Conto Pay
> A hosted workspace for preparing, approving, sending, and tracking agent payments.
# Conto Pay
Conto Pay is a hosted payment workspace for teams that want to use Conto without operating their
own agent runtime. It brings payment preparation, policy checks, approvals, execution, and receipts
into one dashboard experience.
New workspaces start in sandbox so you can test recipients, policies, approvals, and receipts with
test funds. Contact [sales@conto.finance](mailto:sales@conto.finance) when your organization is
ready to discuss production payments.
Open the hosted dashboard and complete a small payment in test mode.
## What You Can Do
With Conto Pay, an authorized operator can:
* manage a hosted payment profile and share its public link
* save approved recipients and resolve other Conto Pay profiles by handle
* prepare payments with an amount, recipient, memo, and optional invoice reference
* apply the organization's spending policies and approval requirements
* review pending requests before funds move
* track payment status and open a receipt after execution
* create payment or request links for a specific counterparty
* review activity totals and conversion rates for reconciliation
* review production readiness and request live-payment access when eligible
* review trust reports concerning the organization's hosted profiles
* use the dashboard assistant to navigate common payment tasks
## Hosted Profile
Each workspace has a public profile with a stable Conto Pay handle. The profile helps a
counterparty confirm who they are paying and provides Pay and Request actions. You can share the
profile URL or its handle without sharing dashboard credentials.
The public Profile API provides the identity and payment information needed to present the profile
and start a payment safely. Treat that response as public information; keep organization settings,
credentials, policy configuration, and operator activity in the authenticated dashboard.
Before paying a saved profile, confirm that its current name, handle, and destination match the
details you expect. If Conto reports that a saved profile changed, review the latest profile before
continuing.
## Manage Conto Pay
Open **Manage Conto Pay** below the payment form when you need operational tools. It stays collapsed
by default and groups the secondary controls into focused tabs:
* **Activity** shows recent payments and requests with their next action.
* **People** shows known contacts and lets you search the Conto Pay directory.
* **Links** creates and manages shareable pay or request links.
* **Profile** updates the public account name, description, aliases, and directory visibility.
* **Controls** summarizes the hosted wallet and links to shared wallet, policy, transaction, and
alert pages.
* **Insights** shows recent usage, conversion, and trust reports.
For setup and production access, follow the readiness steps below and use the returned next action.
## Payments To Any Wallet
Conto Pay can prepare a payment to an approved wallet address. When the recipient also uses Conto
Pay, you can resolve the workspace by its handle or profile and save it as a recipient. Both paths
use the same policy and approval controls.
## Payment Flow
Sign in to the dashboard and select **Conto Pay**. Confirm that you are in the intended
organization and environment.
Confirm that the hosted wallet is available and has the funds required for the payment. Use test
funds while working in sandbox.
Select a saved recipient, resolve a Conto Pay handle, or enter an approved wallet address. Enter
the amount and optional note, then verify the destination before continuing.
Select **Continue** to resolve the recipient and run the organization's payment controls.
Continuing does not send funds.
Check the recipient, amount, network, and policy result. If approval is required, open **Review
approval** and complete the decision.
When the payment is ready, select **Send payment**, review the confirmation, and authorize the
transfer.
Keep the payment status page or receipt for reconciliation. If execution is uncertain, check the
existing request before trying again.
## Payment And Request Links
A payment link can prefill a profile, amount, memo, or invoice reference. A request link gives the
payer the same details in a reviewable form. Opening either link does not authorize or execute a
payment; the payer must still review the request and complete the required controls.
When sharing a link:
* send it only to the intended counterparty
* ask the recipient to verify the profile and amount
* set an expiry when the request is time-sensitive
* cancel the link if its details are no longer valid
## Requests And Receipts
Payment requests have a hosted review page where the payer can inspect the details and decide what
to do. Completed payments have a status page and receipt. The Conto Pay activity view keeps these
records together so operators can reconcile requests and outcomes without relying on chat history.
## Activity Analytics
Authenticated organization members can use `GET /api/conto-pay/analytics` to review Conto Pay
activity totals, conversion rates, and stage counts. Set `period` to `24h`, `7d`, `30d`, or `90d`;
add `format=csv` to download the same customer-facing data for reconciliation.
The response includes the selected period, activity totals, conversion rates, and stage counts.
These fields can be displayed in an operations view or exported for reconciliation.
## Moving From Test To Live Payments
`GET /api/conto-pay/readiness` returns the current workspace's setup, readiness, payment mode,
profile, wallet network, controls, and test-flow counts. Use the stable
`canRequestProductionAccess`, `canPresentLivePayments`, blockers, and next-action fields to decide
whether to keep testing, finish setup, or request production access.
When `canRequestProductionAccess` is `true`, an authenticated organization member can call
`POST /api/conto-pay/production-access`. The response includes the request reference, status,
timestamps, and next action. Continue using test payments until payment availability explicitly
reports **Live payments**.
Existing integrations can continue calling `GET /api/conto-pay/launch-evidence` and
`POST /api/conto-pay/live-review`. Those compatibility routes return the same customer readiness
and production-access fields and identify their successor endpoint in the response headers. New
integrations should use `/readiness` and `/production-access`.
## Trust Report Review
Operators with alert access can review trust reports concerning their organization's Conto Pay
profiles. `GET /api/conto-pay/reports?limit=8` returns up to 25 reports with stable status,
severity, reason, profile, checkout reference, timestamps, outcome, and customer-facing next-step
fields. Operators with alert-management permission can update a report through
`PATCH /api/conto-pay/reports/{reportId}` using a status of `reviewing`, `resolved`, or `closed`.
The optional `hide_profile_from_directory` action removes the reported profile from broad directory
search while leaving an auditable outcome on the report. Organization responses include the report
reference, customer-readable status, reason, details, timestamps, outcome, and next step.
## Using The Dashboard Assistant
The assistant can help you find payment information and move through supported dashboard tasks.
Financial actions still require the same permissions, policy checks, and confirmations as actions
started elsewhere in the dashboard.
Use direct, specific prompts such as:
* "Show the current balance for this Conto Pay workspace."
* "Find the profile for @vendor-org."
* "Prepare a \$25 sandbox payment to the saved Vendor AP recipient for invoice 1042."
* "Show the status of my most recent payment request."
Always review the recipient, amount, network, and resulting status before treating a payment as
complete.
## Conto Pay, AI Assistant, And MCP
| Surface | Best for | Authentication | Payment execution |
| --------------------------------------- | ---------------------------------------- | ----------------- | ------------------------------------------------------------- |
| **Conto Pay** | Hosted payment preparation and tracking | Dashboard sign-in | Supported through the hosted payment flow |
| **[AI Assistant](/docs/assistant/overview)** | Help with supported dashboard tasks | Dashboard sign-in | Uses the permissions and confirmations of the underlying task |
| **[MCP Server](/docs/mcp/overview)** | Connecting your own MCP-compatible agent | Agent SDK key | Supported through MCP payment tools and policy checks |
## Safety Checklist
Before authorizing a payment:
1. Confirm that you are in the correct organization and environment.
2. Verify the recipient's handle or wallet address.
3. Confirm the amount, asset, network, memo, and invoice reference.
4. Review the policy result and any required approval.
5. After execution, verify the resulting status and receipt.
Run a first hosted payment safely in test mode
Test integrations, policy outcomes, and payment edge cases
Configure and complete payment approvals
Learn how the dashboard assistant handles supported tasks