Overview
Mandate402 is a Morph-native governance and treasury control layer for x402 machine commerce. It sits between an agent payment request and settlement, defining who an agent may pay, how much it may spend, which vendors are approved, when authority expires, and what evidence remains reviewable.
The current repository documents the v0.2.0 production-hardening milestone and a deployed Morph Hoodi treasury contract. It does not replace the x402 facilitator or the paid vendor; it adds the policy boundary between payment intent and value leaving the treasury.
What I built
- Mandate creation, approval, expiry, and revocation workflows
- Budget reservation before a paid vendor request is dispatched
- Vendor, facilitator, receipt, spend-limit, and treasury policy gates
- Reconciliation for ambiguous payment outcomes instead of guessing final truth
- Operator-facing audit trails for allowed, blocked, and unresolved attempts
- Morph-native contract anchors for mandate and treasury lifecycle events
Stack
Next.js, TypeScript, Solidity, Foundry, Morph Hoodi, x402, Pyth, Postgres, and a Go x402 merchant.
What I learned
Agentic payments need governance before they need more autonomy. The key design lesson was to separate payment transport from organizational policy, then preserve enough evidence for a human to understand why a payment was allowed, blocked, or held for reconciliation.
