The Agent Payments Stack is Splitting in Two

<p>Five companies raised $111M+ in the last 30 days to build payment infrastructure for AI agents. Visa announced ChatGPT integration. Coinbase projects agent payments will drive 7x revenue growth.</p> <p>The market is validated. But there's a fork in the road nobody's mapping.</p> <h2> The Core Question </h2> <p>Should AI agents <em>borrow</em> human wallets, or <em>own</em> their own?</p> <p>Most coverage treats all solutions as equivalent. They're not. The architectural choice — account abstraction vs agent-owned MPC wallets — determines everything downstream: speed, liability, autonomy.</p> <h2> Route 1: Account Abstraction (Delegation) </h2> <p><strong>How it works:</strong> Agent operates YOUR wallet with permissions.</p> <p>Players: Biconomy Smart Sessions, ZeroDev, Alchemy Account Kit.</p> <p>The agent gets a session key. It can execute transactions on your behalf within pre-set rules. You own the wallet. The agent borrows it.</p> <p><strong>Strengths:</strong></p> <ul> <li>Leverage existing user liquidity</li> <li>Familiar smart contract patterns</li> <li>Works within Ethereum's account model</li> </ul> <p><strong>Trade-offs:</strong></p> <ul> <li>Every payment still flows through your approval logic</li> <li>Liability sits with the user (if agent drains funds, it's your asset)</li> <li>Adds latency — even with session keys, there's an approval layer</li> </ul> <p><strong>Best for:</strong> Agents executing tasks on behalf of a user (trading, DeFi, social actions).</p> <h2> Route 2: MPC Wallets (Ownership) </h2> <p><strong>How it works:</strong> Agent has ITS OWN wallet. No shared custody.</p> <p>Players: AgentWallex, Skyfire, Turnkey (enterprise).</p> <p>The agent controls a wallet secured by multi-party computation. Private keys never exist in one place. Agent authorizes payments directly from its wallet. Clean separation from user funds.</p> <p><strong>Strengths:</strong></p> <ul> <li><150ms authorization (no human approval loop)</li> <li>Liability isolated (agent's wallet runs dry, user assets untouched)</li> <li>Native autonomy (agent acts, doesn't delegate)</li> </ul> <p><strong>Trade-offs:</strong></p> <ul> <li>Agent needs its own liquidity (deposit required)</li> <li>New mental model (agents as financial entities)</li> <li>Custody responsibility shifts to infrastructure provider</li> </ul> <p><strong>Best for:</strong> Agent-to-agent transactions, micropayments, autonomous commerce at scale.</p> <h2> Why the Fork Matters: Three Litmus Tests </h2> <h3> 1. Speed </h3> <p>An agent paying $0.002 per API inference shouldn't need to route through your wallet's approval logic.</p> <p>x402 micropayments (pay-per-API-call, pay-per-result) need sub-150ms settle times. Card networks average 2-3 seconds. AA adds a session key check. MPC wallets authorize directly.</p> <p><strong>Example:</strong> Agent calls a weather API 1,000 times per day at $0.001 per call. AA route processes 1,000 delegated transactions through your wallet. MPC route: agent pays from its own wallet, you never see the noise.</p> <h3> 2. Liability </h3> <p>If an agent overspends, who's liable?</p> <p><strong>AA model:</strong> Agent was operating YOUR wallet. Even with spending limits, the funds came from your account. You're exposed.</p> <p><strong>MPC model:</strong> Agent spent from ITS wallet. Your assets never touched. When the agent's wallet runs dry, it stops. Clean failure mode.</p> <h3> 3. Autonomy </h3> <p>Can the agent transact while you sleep?</p> <p><strong>AA model:</strong> Depends on session key expiry and spending caps. You're still in the loop, even passively.</p> <p><strong>MPC model:</strong> Agent operates 24/7. You topped up its wallet once. It pays for compute, APIs, services — no approval required.</p> <h2> The Bigger Picture: Four Layers Emerging </h2> <p>The agent payments stack isn't winner-take-all. It's layering:</p> <ol> <