Settlement & vault credit

The in-app Settlement screen is where you move value into USDC vault credit on Base before subscribing to a credit pool. This page explains how that rail works at a policy level. Binding terms remain in executed agreements, pool documents, and the in-app legal suite.

Nothing here is an offer to sell or a solicitation. Access is limited to qualified institutional and accredited investors where permitted.

What you are funding

Denomination: Pool subscriptions consume USDC vault credit recorded against your wallet on the Base network. That is the only unit the subscription rail uses for commitment.
Other digital assets are ingress-only: bridge to Base and/or use in-app Convert on Base where a pair is supported—so value becomes USDC vault credit before you subscribe.
Custody: Routine flows are non-custodial at the wallet layer—you approve and sign transactions; the platform does not hold your private keys.

Typical path (A–D)

Eligibility & identity — Complete KYC/KYB when required before your first subscription.
Settlement (this rail) — Obtain USDC vault credit on Base (direct USDC deposit and/or approved on-chain conversion per in-app configuration).
Pool subscription — Allocate from Marketplace according to pool rules.
Position & attestation — Track holdings and activity in Portfolio; on-chain events support verification where applicable.

For a broader lifecycle view, see How it works. For subscription mechanics at a high level, see Subscription & commitment.

Bring funds from another network

If your balance sits on another supported network, move it to Base first (the in-app panel links to an external bridge flow where configured), then continue with deposit or convert on Base. In-app chain and token selectors are planning aids; you always confirm network, asset, and destination USDC on Base in the third-party bridge interface. Outbound links to the official Base bridge may include standard UTM-style query parameters for product analytics only — they do not configure routing; you still confirm everything in the bridge UI.

Cross-chain friction (common issues)

Wrong network in wallet — Subscriptions execute on Base (or Base Sepolia on test deployments). If your wallet is on another chain, switch to the correct Base network before depositing or subscribing.
Gas on the source chain — You need enough native gas on the origin network to initiate a bridge transaction; the platform does not fund gas for you.
Delays and pending state — Cross-chain transfers can take minutes or longer. Use a block explorer to verify status; do not assume instant finality.
Token choice — You may bridge from various assets depending on the bridge; vault and subscription denomination on KIBOV remains USDC on Base after funds arrive.

For a fuller risk overview, see General risk and Technology risk.

Risk, compliance, and liquidity context

Risks — Credit, liquidity, technology, and smart-contract factors are summarized under Risk.
Compliance — KYC/AML and conduct expectations are described under Compliance.
Internal liquidity — Any rule-based transfer or platform-governed liquidity is described in offering documents and Platform liquidity—not an unrestricted market for underlying credit claims.