Kizuna Verification & Compliance

The Verification Layer

Verification in Kizuna is the first phase of every payment flow. Before any funds move, the x402 facilitator validates the request, resolves the agent's lane, and forwards to the kernel for approval. This pre-settlement verification is what makes Kizuna fundamentally different from traditional payment systems that detect problems after money has moved.

The verify endpoint accepts the payment amount, lane selection, mandate or collateral reference, and agent identity. It returns either an approved reservation (with a signed decision envelope) or a denial (with the specific reason).

Kernel Evaluation Process

When the kernel receives a verify request, it runs a multi-step evaluation:

• Identity check — agent exists and has a valid Meishi passport
• Lane validation — agent is authorized for the requested lane
• Funding check — sufficient prefund (enterprise) or collateral headroom (crypto-fast)
• Policy evaluation — request passes all active policy packs (spend limits, frequency caps, counterparty rules)
• Risk graph check — no anomalous patterns detected
• Decision signing — if all checks pass, kernel signs an approval envelope

The entire evaluation happens in milliseconds. The kernel is optimized for low-latency decisioning to keep agent workflows fast.

Meishi Compliance Passports

Meishi is KAMIYO's compliance passport system. Every agent participating in Kizuna has a Meishi profile containing verified identity attributes, compliance certifications, jurisdiction information, and policy attestations.

Mandate Enforcement

Enterprise lane agents operate under mandates — explicit spending authorizations set by the agent's operator. Mandates define per-transaction limits, daily/weekly/monthly caps, allowed counterparties, and allowed service categories.

The kernel enforces mandates during verify. If a request would exceed any mandate limit, it is denied. Operators manage mandates through the Wallet Control Plane API, and changes take effect immediately on the next verify request.

Audit and Reporting

Every Kizuna verification and settlement generates audit records. These are accessible through the companion API and include:

• Full request/response payloads for every verify and settle call
• Kernel decision details including which policy checks passed or failed
• Settlement amounts, lanes, timestamps, and on-chain transaction signatures
• Denial reasons for rejected requests
• Agent identity and Meishi passport state at time of transaction

This audit trail supports regulatory compliance, internal reconciliation, and dispute investigation. For organizations subject to financial reporting requirements, the companion API provides structured data exports.