MoonPay's Open Wallet Standard: Building the SWIFT of Machine Payments

Every thirty seconds, an AI agent somewhere on the internet tries to pay for something — a compute job, a data feed, a cross-chain swap — and fails. Not because it lacks funds, but because it lacks a wallet that speaks the right language for the right chain. MoonPay thinks it has fixed that problem, and PayPal, Circle, the Ethereum Foundation, and fifteen other organizations agree.

On March 23, 2026, MoonPay open-sourced the Open Wallet Standard (OWS), a specification that gives autonomous AI agents a single, secure interface for holding value, signing transactions, and making payments across every major blockchain — without ever exposing a private key. The release, available on GitHub, npm, and PyPI, arrives at a moment when over 250,000 AI agents are already executing on-chain transactions daily and the autonomous agent economy is projected to reach $30 trillion by 2030.

From MoonPay Agents to an Industry Standard

The OWS didn't materialize from a whitepaper committee. It grew out of production code.

In February 2026, MoonPay launched MoonPay Agents, a non-custodial software layer that lets AI agents create wallets, manage funds, and transact autonomously on behalf of verified users. The product supports the full financial cycle: fiat-to-crypto funding (via Apple Pay, PayPal, Venmo), portfolio tracking, cross-chain swaps, recurring purchases, and conversion back to traditional currencies.

As MoonPay's team built out multi-chain support, they realized the wallet layer — how keys are stored, how transactions are signed, how policies govern agent behavior — was a problem every builder in the agent economy faced. Rather than keep it proprietary, they generalized the infrastructure, stripped the MoonPay-specific parts, and released it as an MIT-licensed open standard.

"Every agent framework is reinventing wallet management from scratch," MoonPay noted in its announcement. "OWS gives them a shared foundation so they can focus on what their agents actually do."

How the Open Wallet Standard Works

At its core, OWS defines seven modular sub-specifications that can be adopted independently or as a complete stack:

• Storage Format — Vault layout, keystore schema, and filesystem permissions
• Signing Interface — sign, signAndSend, and signMessage operations
• Policy Engine — Pre-signing transaction policies with spending limits, asset-type restrictions, and counterparty whitelists
• Agent Access — How agents authenticate and interact with wallets through scoped permissions
• Key Isolation — Cryptographic boundaries between agent processes and private keys
• Wallet Lifecycle — Creation, backup, recovery, and revocation flows
• Supported Chains — Chain family adapters for EVM, Solana, Bitcoin, Cosmos, Tron, TON, Filecoin, and XRP Ledger

A single seed phrase derives accounts across all eight chain families. The key security model is uncompromising: private keys are encrypted at rest using AES-256-GCM, decrypted only to produce a signature, held in protected memory that cannot be swapped to disk, and wiped immediately afterward. The key is never accessible to the agent process, the language model context, or any parent application.

OWS provides native SDK bindings for Node.js and Python, a command-line interface, and a Model Context Protocol (MCP) server interface. Agents built on Claude, ChatGPT, LangChain, or any MCP-compatible framework can access wallets through their native tool system — no custom integration work required.

A Coalition That Spans the Stack

What makes OWS notable is not just the technology but the breadth of its contributor list. Over 15 organizations participated in the initial release:

Layer	Contributors
Traditional Finance	PayPal, Circle
Exchanges	OKX
L1 Foundations	Ethereum Foundation, Solana Foundation, TON Foundation, Filecoin Foundation, Tron
L2 / Scaling	Base, Polygon, Arbitrum, Sui
Cross-Chain	LayerZero, Ripple
Agent Ecosystem	Virtuals, Uniblock, Dflow, Simmer.Markets
Developer Infra	Dynamic, Allium

PayPal brings mainstream payment credibility. Circle contributes stablecoin expertise from running USDC. The foundation layer — Ethereum, Solana, TON, Filecoin — ensures OWS covers the chains where agents actually transact. LayerZero handles the cross-chain bridging layer. And Virtuals, as one of the leading AI agent token platforms, validates demand from the agent-native side.

This coalition signals something significant: the wallet layer for autonomous agents is too critical for any single company to own. Just as HTTP succeeded because no one company controlled it, OWS is betting that openness accelerates adoption faster than proprietary lock-in.

The Agent Wallet Wars: A Competitive Landscape

MoonPay's OWS enters a market where at least nine platforms already offer some form of agent wallet infrastructure. Each takes a meaningfully different approach:

Coinbase Agentic Wallets launched in February 2026 alongside the x402 payment protocol, which enables HTTP-native stablecoin micropayments. Coinbase's model is vertically integrated: agents get USDC wallets on Base, with built-in guardrails and Coinbase managing the custody layer. By March 2026, x402 had processed over 50 million transactions.

Human.tech's Agentic WaaP (Wallet as a Protocol), unveiled at WalletCon Cannes on March 31, takes a different angle — making human override a first-class protocol primitive. WaaP uses a two-party computation custody model where the private key is split between the user's device and a secure enclave, with cryptographically enforced spending limits and circuit breakers for anomalous agent behavior.

MetaMask's EIP-7702 delegation toolkit focuses on session keys, which let agents interact with dApps through scoped, time-limited permissions without full key exposure. It's a more incremental approach, retrofitting existing wallet infrastructure rather than building agent-native from scratch.

OWS positions itself as complementary rather than competitive. When Coinbase's x402 returns a payment request, OWS produces the signed authorization. When a micropayment protocol opens a session and streams payments, OWS signs each one within the agent's authorized limits. It's the wallet layer underneath, not the payment protocol on top.

Why Key Isolation Matters More Than You Think

The security architecture of OWS addresses a real and growing risk. In early 2026, an autonomous agent operating under the name Lobstar Wilde lost approximately $450,000 when its wallet was compromised — a stark reminder that agents handling real money need hardware-grade key isolation, not just software promises.

MoonPay went further in March 2026 by integrating Ledger hardware wallet signing into its MoonPay Agents platform, allowing high-value agent wallets to require physical device confirmation for transactions above certain thresholds. OWS's key isolation spec codifies these principles:

• Keys never exist in plaintext in process memory longer than the milliseconds needed to sign
• The agent's language model context never contains key material
• Parent applications cannot access the signing process
• Policy enforcement happens before key decryption, not after

This model matters because the economics of agent wallets create attractive targets. If the agent economy reaches even a fraction of its projected $30 trillion scale, the aggregate value in agent-controlled wallets will dwarf most traditional attack surfaces.

The $30 Trillion Question

Industry forecasts project the autonomous agent economy at $30 trillion by 2030, with AI systems managing a growing share of routine financial decisions. The AI agents market specifically is expected to grow from $7.84 billion in 2025 to $52.62 billion by 2030, reflecting a 46.3% compound annual growth rate.

These projections depend on solving the wallet problem. Today's 250,000+ daily active on-chain agents represent early adoption — the equivalent of the internet's dial-up era. For that number to reach millions or tens of millions, agents need wallet infrastructure that is:

1. Universal — One standard across chains, not chain-specific SDKs
2. Secure — Key isolation that institutions trust with real capital
3. Policy-governed — Spending limits and circuit breakers that satisfy compliance requirements
4. Open — No vendor lock-in that forces agents into a single ecosystem

OWS checks all four boxes. Whether it becomes the dominant standard depends on adoption velocity — and the contributor list suggests strong initial momentum.

What This Means for Developers

If you're building agents that need to move money, OWS dramatically simplifies the integration path. Instead of writing separate wallet management code for Ethereum, Solana, Bitcoin, and every other chain your agent might interact with, you write to one interface:

# Install OWS
npm install @open-wallet-standard/core

# Or for Python
pip install open-wallet-standard

The policy engine is particularly useful for production deployments. You can define per-agent spending limits, restrict which token types an agent can transact, whitelist counterparty addresses, and set automatic circuit breakers — all declaratively, without writing custom authorization logic.

For framework developers building on LangChain, AutoGPT, or similar orchestration tools, the MCP server interface means OWS wallets appear as native tools in the agent's capability set. No wrapper code, no custom plugins.

Looking Ahead

The Open Wallet Standard represents a bet on a particular future: one where AI agents are first-class economic actors with their own wallets, their own transaction histories, and their own financial relationships. In that future, the wallet layer for machines becomes as critical as SWIFT is for banks — a shared infrastructure that makes the entire ecosystem work.

The initial release covers eight chain families, but the modular architecture is designed for extension. Zcash has already submitted a grant application for OWS integration, and other privacy-focused chains are expected to follow. As the ERC-8004 standard for on-chain agent identity matures and regulatory frameworks like the GENIUS Act clarify stablecoin compliance requirements, OWS's policy engine will likely evolve to incorporate Know Your Agent (KYA) verification alongside its existing transaction controls.

MoonPay built the wallet infrastructure it needed, then gave it away. Now the question is whether the rest of the industry builds on it — or keeps reinventing the same wheel.

---

BlockEden.xyz provides robust multi-chain RPC and API infrastructure supporting Ethereum, Solana, Sui, and 20+ blockchains — the same networks where AI agents increasingly need reliable, low-latency access. Explore our API marketplace to power your next agent-native application.