> ## 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.
# Live Rollout
> How Conto Pay moves from sandbox to live money through launch evidence, live review, rollout gates, and customer-safe agent guidance.
# Live Rollout
Conto Pay is sandbox-first. A hosted workspace can discover payees, create checkout links, run
closed-loop sandbox payments, and request payment from another organization before live money is
enabled.
Live money is enabled through a guided rollout. Conto reviews the workspace, launch evidence,
support ownership, funding scope, trust-review ownership, and customer-facing claims before the
workspace is marked live-enabled.
Agents and operators should treat `livePaymentsEnabled` as the source of truth for live-money
claims. If it is `false`, keep the user in setup, sandbox testing, launch evidence, or live-review
guidance.
## The Launch Path
The Conto Pay Activation card and launch evidence packet use the same launch path:
| Phase | What it means | Safe next action |
| ------------- | --------------------------------------------------------------------------- | ----------------------------------------------------- |
| Hosted setup | The workspace, profile, wallet, controls, or handoff links still need setup | Finish setup in the Conto Pay console |
| Sandbox proof | Setup is usable, but sandbox payment evidence is incomplete | Run payer-initiated and payee-initiated sandbox flows |
| Live review | Sandbox evidence is ready or review has been requested | Request live review or wait for Conto support |
| Live-enabled | Conto has approved the workspace and live payments are enabled | Use live-money flows inside normal Conto controls |
Operators can copy launch evidence from the Activation card. Authenticated agents can fetch the
same customer-safe packet from:
```http theme={null}
GET /api/conto-pay/launch-evidence
```
The response returns `{ launchEvidence }`. It intentionally omits SDK key prefixes and
support-only review metadata.
## What Launch Evidence Includes
Launch evidence is safe to paste into a support thread or hand to another authenticated agent. It
includes:
* hosted profile handle, profile URL, and Profile API URL
* account display name, public discovery aliases, and handoff query examples
* setup, wallet, profile, approval, and handoff readiness
* closed-loop payment and hosted request evidence status
* live-review status and next action
* sanitized public-rollout evidence completeness, missing labels, and next action
* public `paymentMode` and compact `agentReadiness.actions`
* customer-safe rollout-policy messaging
* non-secret support packet details for Conto review, including sanitized public-rollout evidence
Agents should use the packet to explain what the user can do next. They should not infer live-money
capability from a profile being discoverable, a checkout link being active, or a live-review request
existing.
## Requesting Live Review
When hosted setup and sandbox proof are ready, operators can click **Request live review** from the
Activation card. The request creates or reuses one Conto support review item for the workspace.
Conto support can also create a launch-review record from the internal launch dashboard when a
cohort is being prepared and the customer has not clicked the Activation card yet. That support
created review gives launch evidence an audit-backed home, but it does not enable live payments by
itself.
A live-review request is not live approval. The workspace remains sandbox or guided-live until
Conto approves the review and the Profile API reports `livePaymentsEnabled: true`.
## Public Rollout Evidence
Before Conto Pay moves beyond a controlled cohort, Conto records launch-ops evidence for each
workspace. The required public-rollout evidence fields are:
| Evidence field | What Conto records |
| ------------------------- | ------------------------------------------------------------------------------ |
| Support owner | The named owner for customer questions, live review, and incidents |
| Production funding limit | The approved live-funds scope and replenishment owner |
| Funnel review cadence | How often launch funnel alerts are reviewed during rollout |
| Trust-report owner | The owner for profile reports, impersonation concerns, and directory decisions |
| Deployment evidence | Release, commit, pull request, or deployment evidence for the customer session |
| Legal/compliance evidence | Counsel-approved legal or compliance evidence for external use |
| Public rollout decision | The launch owner's public rollout decision and scope |
| Claims review evidence | Review evidence for docs, marketing, onboarding, and sales claims |
These fields are visible to Conto support in launch-readiness exports and signoff packets. They are
not required for a supervised sandbox run, but they are required before broad live-money rollout.
The same readiness response includes a `publicRolloutDecision` summary with the recommended
decision, release scope, public-invite flag, live-rollout flag, reasons, and next action for the
selected cohort.
## Rollout Gate Modes
Conto uses a rollout gate before support can enable live mode:
| Mode | Meaning |
| --------- | --------------------------------------------------------------- |
| Closed | Live approvals are paused |
| Allowlist | Only configured organizations can be approved for live mode |
| Open | Public live rollout is approved, subject to launch-ops evidence |
An allowlist that permits all reviewed organizations is treated like a public rollout switch.
Support still records the public-rollout evidence fields before enabling live mode.
## Agent Guidance
Agents consuming Conto Pay profiles should follow this order:
Fetch the public Profile API URL for the handle or checkout link. Keep any `intent` query
parameter when reading a tracked checkout link.
Use `profile.discovery.aliases`, `profile.discovery.queryExamples`, and
`profile.discovery.agentInstruction` to decide how to display, search, or hand off the payee
identity.
Use the Profile API `profile.integrity.fingerprint`, response `ETag`, and any saved contact
trust snapshot before preparing a repeat payment. If a saved contact has trust warnings, ask the
operator to review the current profile before staging the payment.
Use `profile.paymentMode.canPresentLivePayments` and `profile.activation.livePaymentsEnabled`
before describing the payee as live-money capable.
Use `profile.liveReview.status` and launch evidence `liveReview.rolloutPolicy` only to explain
where Conto review stands.
If live payments are not enabled, help the operator finish setup, run sandbox proof, request
live review, or wait for Conto support.
## Operator Checklist
Before asking Conto to approve live mode:
* confirm hosted setup is complete
* verify the hosted wallet is ready
* name the public Conto Pay account and add any search aliases counterparties will use
* run a payer-initiated sandbox payment to another Conto Pay workspace
* run a payee-initiated hosted request loop
* confirm no active warning or critical funnel alerts block the launch
* review any open trust reports
* copy the launch evidence packet
* request live review from the Activation card
For public rollout, Conto support also records the launch-ops evidence fields listed above and
exports a signoff packet for launch, support, trust, and legal owners.
## Related Docs
Learn what Conto Pay provisions and how profiles, requests, and receipts work
See the prompts and tool behavior for hosted Conto Pay operations
Understand how payment approvals are reviewed and resolved
Subscribe to Conto Pay lifecycle webhooks for request events