MoonPay Unveils Open Wallet Standard – A Unified, Open‑Source Wallet Layer for AI‑Driven Payments
A new foundation for autonomous finance
New York, March 23 2026 – MoonPay, the crypto‑payments network, announced the release of the Open Wallet Standard (OWS) today. The initiative delivers an open‑source, MIT‑licensed specification that enables artificial‑intelligence agents to interact with blockchain wallets without ever exposing private keys.
“The agent economy has payment rails. It didn’t have a wallet standard. We built one, open‑sourced it, and now the full stack exists.” – Ivan Soto‑Wright, CEO and co‑founder, MoonPay
The announcement follows MoonPay’s rollout of MoonPay Agents in February 2026, a non‑custodial software layer that equips AI agents with wallet access, fund management, and autonomous transaction capabilities via the MoonPay CLI. The new standard is positioned as the missing connective tissue that unifies disparate agent frameworks, key‑management practices, and signing logic under a single, secure interface.
Why AI agents need a shared wallet layer
AI‑driven services—from large language models to autonomous trading bots—have increasingly been tasked with moving value on‑chain. Existing protocols such as x402 (Coinbase/Cloudflare), Google’s Agent Payments Protocol (AP2), Stripe’s Machine Payments Protocol (MPP), and the Ethereum Foundation’s ERC‑8004 provide mechanisms for request/response payment flows, identity registration, and session‑based micropayments. However, each of these assumes the existence of a wallet that the agent can call, without defining how that wallet is stored, secured, or discovered.
MoonPay’s internal experience with MoonPay Agents highlighted a fragmented landscape: every agent implementation maintained its own key store, often in plaintext environment variables or proprietary formats. The result was a lack of portability, duplicated security models, and a high operational overhead for developers who needed to support multiple agents across multiple chains.
The Open Wallet Standard aims to resolve these pain points by:
- Providing a single encrypted vault that lives locally on the user’s device, eliminating reliance on cloud key‑management services.
- Abstracting signing across eight major chain families (EVM, Solana, Bitcoin, Cosmos, Tron, TON, Spark, Filecoin, and XRP Ledger) via a unified interface.
- Enforcing policy‑based signing that checks each transaction against pre‑defined limits, allow‑lists, and other compliance rules before a key is ever decrypted.
- Ensuring zero key exposure to the AI agent, the language model, or any parent process through in‑memory encryption (AES‑256‑GCM) and immediate memory wiping after use.
Industry backdrop: the rise of machine‑payment protocols
| Protocol | Origin | Core Function |
|---|---|---|
| x402 | Coinbase & Cloudflare | HTTP‑native stablecoin payments |
| AP2 | Agent‑driven commerce across 60+ partners | |
| MPP | Stripe & Tempo | Session‑based micropayment streaming |
| ERC‑8004 | Ethereum Foundation | On‑chain identity registries for trustless agents |
These specifications collectively create an emerging stack that lets AI agents request, receive, and settle payments without human intervention. Yet, without a common wallet layer, each protocol must rely on a bespoke key‑management solution, leading to fragmented balances and operational inefficiencies. MoonPay’s OWS is designed to sit beneath these protocols, offering a universal signing backend that can be called by any of them.
How the Open Wallet Standard works
Zero key exposure
The standard encrypts private keys at rest using AES‑256‑GCM. Decryption occurs only within a protected memory region that cannot be swapped to disk. Once a signature is generated, the key material is immediately overwritten, ensuring that neither the AI agent nor the surrounding LLM context ever sees the raw key.
One interface, many chains
A single seed phrase can generate accounts across eight distinct blockchain families. The specification adopts CAIP‑2 identifiers for chain selection, enabling developers to address any supported network with the same signing call. This eliminates the need for separate SDKs per chain and reduces integration complexity.
Policy‑gated signing
Before a transaction is signed, a policy engine evaluates it against configurable rules: spending caps, contract allow‑lists, permitted chains, and time‑bound authorizations. These checks happen prior to any key material being accessed, providing a safeguard against rogue or compromised agents.
Agent‑native SDKs
OWS ships with native bindings for both Node.js and Python, a command‑line interface, and an MCP server endpoint. This means agents built on Claude, ChatGPT, LangChain, or any MCP‑compatible framework can invoke wallet functions through their existing tool‑calling mechanisms without additional wrappers.
Local‑first architecture
All vault data remains on the user’s device. No external key‑management service or cloud storage is required, and the only network interaction is the broadcast of a signed transaction to the appropriate blockchain node.
Open‑source licensing and community backing
The Open Wallet Standard is released under the permissive MIT license, encouraging broad adoption and contribution. The project’s initial commit list includes contributions from a diverse set of organizations:
- PayPal
- OKX
- Ripple
- Tron
- TON Foundation
- Solana Foundation
- Ethereum Foundation
- Base
- Polygon
- Sui
- Filecoin Foundation
- LayerZero
- Dflow
- Uniblock
- Virtuals
- Arbitrum
- Dynamic
- Allium
- Simmer.Markets
- Circle
These contributors span custodial and non‑custodial players, layer‑1 protocols, infrastructure providers, and compliance specialists, underscoring the standard’s cross‑industry relevance.
Potential impact on the AI‑driven payments stack
Consolidated balances
By centralizing funds in a single encrypted vault, agents can avoid the “split‑balance” problem where the same $100 in stablecoins is divided across three independent wallets. A unified view simplifies accounting, reduces transaction fees, and streamlines compliance reporting.
Faster integration cycles
Developers building new AI agents or extending existing ones can now rely on a single, well‑documented signing API rather than crafting bespoke key‑handling code for each blockchain. This could shorten time‑to‑market for AI‑powered fintech products and lower the barrier to entry for smaller firms.
Strengthened security posture
The policy engine and zero‑exposure design address two of the most common attack vectors in autonomous finance: rogue agents that exceed spending limits and key leakage through logs or environment variables. By enforcing limits at the wallet layer, organizations gain an additional compliance checkpoint that can be audited independently of the agent’s business logic.
Compatibility with existing protocols
Because OWS does not replace protocols like x402, AP2, or MPP, it can be layered underneath them. Any protocol that expects a signed transaction can now call a standardized wallet, reducing integration friction for downstream services such as payment processors, marketplaces, or on‑ramp providers.
Analyst perspective
Fintech analysts see the Open Wallet Standard as a logical next step in the evolution of embedded finance for autonomous agents. By providing a shared, open‑source wallet layer, MoonPay addresses a critical infrastructure gap that has limited the scalability of machine‑payment protocols. The broad consortium backing the project suggests a willingness across the ecosystem to co‑operate on foundational standards—a trend reminiscent of early API standardization in open banking.
However, adoption will depend on how quickly major AI platform providers (e.g., OpenAI, Anthropic, Google) incorporate OWS into their tool‑calling frameworks. If integration occurs early, OWS could become the de‑facto wallet interface for AI agents, much like OAuth did for web‑based authentication. Conversely, fragmented adoption could lead to parallel proprietary solutions, re‑introducing the very fragmentation OWS aims to eliminate.
Regulators are likely to view the policy‑gated signing model favorably, as it offers a built‑in mechanism for enforcing AML/KYC limits at the wallet level. While the standard does not itself handle identity verification, its design makes it straightforward to plug in external compliance checks before a transaction is signed.
Bottom line
MoonPay’s Open Wallet Standard delivers a much‑needed, open‑source foundation for AI agents to manage crypto assets securely across multiple blockchains. By unifying key storage, signing, and policy enforcement under a single, MIT‑licensed specification, the project could streamline the burgeoning machine‑payment ecosystem and set a baseline for future regulatory compliance. The involvement of over a dozen heavyweight contributors adds credibility and suggests that the standard may gain traction quickly—provided that the broader AI and fintech communities adopt it in their development pipelines.
Get in touch with our fintech expert
