> ## 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.

# Payment flows and prerequisites

> Choose a payment path by signer, network, protocol, and test environment.

Choose the flow first, then verify the specific wallet and network through `GET /api/sdk/setup`.
A configured network does not imply every custody or protocol combination is available for your
organization.

## Flow requirements

| Flow                        | Signing and network requirement                                                     | Conto's part                                                                              | Start here                                                          |
| --------------------------- | ----------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------- | ------------------------------------------------------------------- |
| Anonymous sandbox           | No signer or funded wallet needed                                                   | Simulated payment decisions, execution receipts, and spend tracking                       | [Sandbox](/docs/quickstart/agent-sandbox)                                |
| Managed stablecoin payment  | A linked, funded managed wallet on its configured chain                             | Request authorization and managed execution                                               | [First payment](/docs/quickstart/setup)                                  |
| External stablecoin payment | Your signer and sender wallet on the explicitly supplied chain                      | Approve before sending; confirm the final transfer                                        | [External flow](/docs/sdk/payments#external-wallet-approve/confirm-flow) |
| x402 API payment            | Your x402 signer/client must support the service's challenge and settlement network | Pre-authorize and record verified settlement; does not make the paid HTTP request for you | [x402](/docs/guides/x402-api-payments)                                   |
| MPP charge or session       | Your MPP client and the service must agree on method, network, and session terms    | Evaluate controls and record charges/settlement                                           | [MPP](/docs/guides/mpp-session-payments)                                 |
| Contract-enforced wallet    | A deployed contract and an independently configured authorization/signing path      | Policy evaluation; ordinary managed `execute` cannot execute a smart-contract wallet      | [Custody](/docs/guides/custody-modes)                                    |

## Network and currency selection

| Network       | Chain ID         | Primary stablecoin | Environment                         |
| ------------- | ---------------- | ------------------ | ----------------------------------- |
| Tempo Testnet | `42431`          | `pathUSD`          | Onchain testnet; quickstart default |
| Tempo         | `4217`           | `USDC.e`           | Mainnet                             |
| Base          | `8453`           | `USDC`             | Mainnet                             |
| Base Sepolia  | `84532`          | `USDC`             | Testnet                             |
| Ethereum      | `1`              | `USDC`             | Mainnet                             |
| Arbitrum One  | `42161`          | `USDC`             | Mainnet                             |
| Polygon       | `137`            | `USDC`             | Mainnet                             |
| Solana        | `solana-mainnet` | `USDC`             | Mainnet                             |
| Solana Devnet | `solana-devnet`  | `USDC`             | Testnet                             |

This table identifies configured networks and primary currencies, not a certification of every
flow on every network. Check `GET /api/chains` and your actual setup. Managed payment requests
select the wallet with `walletId`; external approval uses `chainId`. MPP examples use Tempo.
For x402, follow the service's supported settlement network.

## Before enabling real funds

Confirm the intended custody model is available, the wallet is provisioned and funded, and your
signer can pay the network's fees. Organization-controlled managed wallets require owner setup;
an explicit request for that model fails until configuration is complete. See
[wallet ownership](/docs/guides/custody-modes).

Run a small payment on the intended path and verify the final transaction, not just authorization.
Use separate production credentials and controls, then complete [production readiness](/docs/guides/production-readiness).
If the selected path is unavailable, [contact support](mailto:support@conto.finance) before funding it.