Skip to main content
Conto Pay is a hosted payment workspace. The agent owner or budget holder sets spending policy and approvers. Conto manages the payment account and checks those rules before sending.
New workspaces start in test mode. When test flows are complete, an owner or admin requests production access from the dashboard, and Conto reviews the workspace before enabling live payments.

Run your first test payment

Open the hosted dashboard and complete a small payment in test mode.

​
Hosted profile

Each workspace has a public profile with a stable Conto Pay handle. The profile shows a counterparty who they are paying and offers 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. Organization settings, credentials, policy configuration, and operator activity stay 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

Manage Conto Pay, below the payment form, holds the operational tools. It is collapsed by default and has these tabs:
  • Activity shows recent payments and requests with their next action.
  • People shows known contacts and searches 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.

​
Connected cards

On the Builder and Enterprise plans, the Conto Pay page lists the organization’s connected cards below the wallet. Each card shows its brand, last four digits, and status, the agents it is assigned to with their limits and spend today, and how many authorizations are active or waiting for verification. The panel also shows how many card purchases are waiting for review and the most recent card purchases. The panel is read-only. Connect a card, assign it to an agent, and verify or revoke authorizations from the agent’s Connected Cards tab. Review card purchases from Alerts. Card purchases use the card’s own limits and approvals and are listed in this panel, not in Activity. GET /api/conto-pay/cards returns the same summary for the signed-in organization.

​
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 payer’s policy and approval controls. A recipient request supplies payment details. It cannot grant spending authority or override the payer’s budget.

​
Payment flow

The flow runs in the hosted dashboard. It needs no SDK, API key, or payment agent. You need:
  • access to a Conto organization
  • the Owner, Admin, or Manager role (Viewers and Members are view-only)
  • a saved recipient, exact Conto Pay handle, or supported wallet address
1

Open Conto Pay

Sign in to the dashboard, select the intended organization, and open Conto Pay from the sidebar. If you see Set up Conto Pay, an owner or admin selects it once to create the hosted payment account.
2

Check the mode and wallet

Look for the Test payments badge beside the payment form. Confirm that the hosted wallet is available and has the funds the payment needs. Use test funds while in test mode. Do not use production funds for a test.
3

Enter a recipient

In Recipient, enter a saved recipient name, an exact handle such as @vendor-org/accounts-payable, or an approved wallet address. The example handle is a placeholder. Use your own verified test recipient.Prefer an exact handle or wallet address for a first test. It avoids ambiguity when several profiles have similar names.
4

Enter the amount

Enter the amount, such as 1.00 for a small test, and an optional recognizable note such as Conto Pay quickstart test. Verify the destination before continuing.
5

Continue to review

Select Continue to review. Conto resolves the recipient, checks the available balance, and applies the organization’s payment controls.This step may authorize a payment request, but it does not send funds.
6

Handle the result

Check the recipient, amount, network, and policy result, then follow the action shown on the payment:
  • Send payment means the payment is authorized and ready.
  • Review approval means a person must approve it before sending. Open it and complete the decision.
  • A funding message means the hosted wallet needs more funds.
  • A recipient error means Conto could not safely resolve a unique destination.
7

Send and confirm

When Send payment is available, select it. Review the recipient and amount in the confirmation dialog, then select Confirm send payment to authorize the transfer.
8

Verify the receipt

Wait for the payment to complete, then open View receipt or the payment status page. Confirm that the recipient, amount, note, and final status match what you intended, and keep the receipt for reconciliation. A Simulated test receipt means no funds moved and no transaction hash exists. A Testnet receipt shows the testnet transaction hash.
A test payment is complete when:
  • the intended recipient was resolved
  • the payment passed or followed the expected approval path
  • the final status is complete
  • a status page or receipt is available

​
Common problems

Retry with the exact Conto Pay handle or full wallet address. A general name can match multiple profiles or no saved recipient.
Select Review approval, complete the approval in Alerts & Approvals, then return to Conto Pay and refresh the payment status.
Open Wallets and add the required test funds, or ask an organization administrator for help. Do not substitute production funds for a test run.
Payments stay blocked until the wallet’s custody connection is restored. Ask an organization administrator or support to check that connection, then refresh the existing payment. The wallet address remains unchanged; adding funds does not restore access. Execution can report CONTO_PAY_WALLET_UNAVAILABLE when this check fails.
Open Payment details and review the policy result. Change the recipient or amount only if that matches the intended test. Otherwise, ask a policy administrator to review the active controls.
Refresh the existing payment before trying again. Creating a second payment can produce a duplicate if the first payment is still processing.
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 still reviews the request and completes the required controls. Links expire after 30 days. When sharing a link:
  • send it only to the intended counterparty
  • ask the recipient to verify the profile and amount
  • cancel the link on the Links tab 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 Activity tab keeps these records together for reconciliation.

​
Activity analytics

Owners, admins, managers, and viewers signed in to the dashboard 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 it as CSV.

​
Moving from test to live payments

GET /api/conto-pay/readiness (dashboard session, not an API key) 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 organization owner or admin 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.

​
Trust report review

Operators with alert access can review trust reports concerning their organization’s Conto Pay profiles. GET /api/conto-pay/reports returns 8 reports by default (limit up to 25) with status, severity, reason, profile, checkout reference, timestamps, outcome, and 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.

Testing payments safely

Test integrations, policy outcomes, and payment edge cases

Approval workflows

Configure and complete payment approvals

Conto Pay with the assistant

Prepare, review, and follow Conto Pay tasks with the dashboard assistant

Conto Pay, assistant, and MCP

Compare who acts, how each surface authenticates, and how it executes payments