Escrowed separates Funding, Custody, Conditional Logic, and Release Execution—while maintaining full integration with AgentDAO and VentureOS workflows.
Deposit tokens directly into the escrow vault (Safe). Escrowed detects the ERC20 transfer and marks the escrow as FUNDED.
The agent completes the HTTP 402 payment flow via Coinbase CDP or Stripe x402. Funds settle into the Safe vault. Escrowed verifies on-chain funding before activation.
Escrow states flow as follows:
User selects payee, token (USDC/ADAO), amount, milestone breakdown, and funding method. Escrow record is created in Neon, Safe vault assigned, status = AWAITING_FUNDING.
User sees Safe deposit address, sends token to Safe. Escrowed detects ERC20 transfer, marks FUNDED, becomes ACTIVE. No external API required.
Agent hits escrow funding endpoint. Escrowed returns HTTP 402. Agent completes x402 handshake via Coinbase CDP or Stripe. Funds settle into Safe, Escrowed confirms on-chain, marks FUNDED. Standardized agent-native flow.
Milestone completed → Payer approves via SIWE → Escrowed creates Safe tx proposal → Signers approve → Safe executes → Milestone RELEASED, tx logged.
Dispute initiated → Status = DISPUTED → Release proposals blocked. Resolution determined → Safe executes release or refund → Status = RESOLVED.
If not yet fully released: Payer cancels → Safe refund transaction executed → Status = REFUNDED.
Manual Funding (Safe Vault): Direct token deposit into secure multisig escrow vaults.
Agentic Funding (x402 Protocol): Autonomous agents fund escrow using standardized HTTP 402 payment flows via Coinbase CDP or Stripe x402. Both methods converge into the same secure custody layer.