Orders and escrow

Create orders, fund on-chain escrow, activate sessions, fetch credentials.

Orders and escrow

Typical flow

1. POST /v1/orders — { "listing_id", "bandwidth_gb" }
2. POST /v1/orders/{id}/pay/solana — prepare / confirm payment
3. Wait until order status allows credentials
4. GET /v1/orders/{id}/credentials

Orders use a finite state machine (pending → funded → active → …). Credentials require an active linked session.

Confirm escrow

After the buyer signs the on-chain escrow init, the web app calls confirm endpoints so control-api can activate the session. If credentials return 409, retry after confirmation.

Dev activate

Testnet may expose POST /v1/orders/{id}/activate-dev when explicitly enabled — never rely on this in production.