​

Deployment Options

Choose a hosting option before you design authentication, wallet custody, webhooks, networking, and operational ownership. Conto is provided as a hosted service by default. The source repository is useful for development and evaluation, but it is not a packaged customer-operated production distribution.

​

Available Paths

If your architecture requires a dedicated environment, a particular region, private connectivity, or customer-operated infrastructure, contact Conto before implementation. This avoids designing against a hosting model that has not been agreed.

​

Hosted Service Boundary

The hosted product exposes the dashboard, REST and OpenAPI endpoints, SDK and MCP integration surfaces, webhooks, and sandbox workflows. Your organization retains control of:

• which people and agents receive credentials
• wallet custody choices and funding authorization
• policy values, approval routing, and counterparty configuration
• storage and rotation of API, SDK, webhook, and wallet secrets
• webhook availability, replay handling, and downstream accounting or ERP integration
• authorization to enable and use live funds

Treat Conto as an external service in your integration. Use request timeouts, idempotency keys, bounded retries, request-ID logging, and reconciliation so an uncertain network response does not cause a duplicate payment.

​

Questions To Settle Before Integration

Record these decisions before moving beyond sandbox:

1. hosted or dedicated-environment path
2. region, network egress, and connectivity requirements
3. wallet custody and live-funding owner
4. secret storage and rotation owner
5. webhook destination, verification, replay, and recovery behavior
6. downstream accounting and reconciliation requirements
7. incident contacts and payment-stop authority

Continue with the Production Readiness Checklist after the sandbox integration is working.