back to top

MoonPay Introduces a Wallet Standard for AI Agents.

MoonPay Launches Open Wallet Standard to Provide a Unified, Non‑Custodial Wallet Layer for AI Agents

Monday, March 23 2026 – MoonPay announced the Open Wallet Standard (OWS), an MIT‑licensed, open‑source specification that defines how autonomous AI agents can store keys, sign transactions and derive cross‑chain accounts without ever exposing private keys to the agent or the underlying large language model (LLM).


A wallet layer for the emerging “agent economy”

The rapid growth of AI‑driven payment services—often referred to as the “agent economy”—has so far relied on a patchwork of protocols that assume agents already possess a wallet. MoonPay’s OWS seeks to fill that gap by establishing a universal, non‑custodial wallet interface that can be adopted across the various payment stacks that are currently competing for dominance.

The specification was drafted with contributions from more than fifteen leading players in the crypto and payments space, including PayPal, OKX, Ripple, Tron, the TON, Solana and Ethereum Foundations, Base, Polygon, Sui, Filecoin, LayerZero and Circle. By securing a broad coalition, MoonPay hopes to avoid the fragmentation that has plagued earlier efforts.

“The agent economy has payment rails. It didn’t have a wallet standard,” said MoonPay CEO Ivan Soto‑Wright in a statement accompanying the launch.


How OWS is built

OWS is divided into seven independent sub‑specifications covering:

  1. Key storage – encrypted seed phrases that are never exposed in clear text.
  2. Transaction signing – signatures are generated in protected memory and wiped immediately after use.
  3. Policy enforcement – a pre‑signing engine that can enforce spending caps, contract allow‑lists, chain whitelists and time‑bounded authorizations.
  4. Agent access control – mechanisms that determine which AI processes may request a signature.
  5. Key isolation – safeguards against swapping key material to disk.
  6. Wallet lifecycle – creation, rotation and destruction of wallets.
  7. Multi‑chain support – a single seed can derive accounts on eight major chain families (EVM, Solana, Bitcoin, Cosmos, Tron, TON, Spark, Filecoin and XRP Ledger) using CAIP‑2 identifiers.

Developers receive native SDKs for Node.js and Python, a command‑line interface, and an MCP (Message‑based Control Protocol) server that can be plugged into popular LLM frameworks such as Claude, ChatGPT and LangChain.

The core design principle—zero key exposure—means that the private key never leaves the secure enclave that performs the signature, keeping it inaccessible to the agent’s execution environment or any surrounding application.


Context: A crowded field of agentic‑payment protocols

The OWS launch arrives at a moment when several competing infrastructures for AI‑driven payments are already in motion:

  • x402 – a protocol backed by Coinbase that recently added universal ERC‑20 support via Uniswap’s Permit2 and new gas‑sponsorship extensions.
  • Machine Payments Protocol (MPP) – introduced by Stripe and Tempo, this Layer‑1 solution released on March 18 and includes a “sessions” primitive that lets agents pre‑define spending limits and emit continuous micropayments without a separate on‑chain transaction for each interaction.
  • Visa Crypto Labs – currently beta‑testing a command‑line interface (Visa CLI) aimed at AI‑agent payments.
  • Circle’s Nanopayments – a test‑net implementation built on the x402 standard that enables sub‑cent, gas‑free USDC transfers for pay‑per‑call API usage.

MoonPay stresses that OWS is not a competitor to these protocols but rather a complementary layer. In practice, an x402 payment request could be fulfilled by an OWS‑signed authorization, while an MPP session would rely on OWS to sign each streamed micropayment within the pre‑approved limits.


Potential impact and adoption hurdles

Unified balance management – Presently, users who operate multiple AI tools may end up with funds scattered across several wallets, each with its own key management approach. OWS promises a single, cross‑chain wallet that can be accessed by any compliant agent, simplifying balance tracking and reducing the risk of lost or duplicated funds.

Security posture – By enforcing zero key exposure and embedding a policy engine, OWS could raise the security baseline for AI‑driven transactions, addressing concerns about malicious LLMs or compromised execution environments.

Interoperability – The broad list of contributors suggests a willingness to align on a shared interface, which could lower the barrier for new agents to integrate with existing payment rails.

Adoption risk – The biggest uncertainty is whether existing agent frameworks will adopt OWS or continue to rely on proprietary key‑management solutions. The standard’s modular design allows selective implementation, but fragmented adoption could reproduce the very problem OWS aims to solve.

Regulatory considerations – As AI agents begin to handle real‑world value, regulators may scrutinize how keys are managed and how policies are enforced. OWS’s transparent, open‑source nature could aid compliance efforts, but the responsibility will still fall on each operator to configure policy engines appropriately.


Key takeaways

  • MoonPay’s Open Wallet Standard (OWS) provides a non‑custodial, multi‑chain wallet interface tailored for AI agents, with a strong focus on zero key exposure and policy‑driven transaction control.
  • Broad industry backing from payments and blockchain foundations signals a coordinated effort to standardize wallet handling across the nascent agentic‑payment ecosystem.
  • OWS complements, rather than competes with, existing protocols such as Coinbase’s x402, Stripe/Tempo’s Machine Payments Protocol, Visa CLI, and Circle’s Nanopayments, acting as the missing “wallet layer.”
  • Security and usability benefits include unified balance management, cross‑chain account derivation from a single seed phrase, and granular spending controls.
  • Adoption will hinge on integration decisions by AI‑agent platforms; optional modularity may help, but fragmented uptake could limit the standard’s effectiveness.
  • Regulatory and compliance implications remain to be explored, though the open‑source and policy‑centric design offers a foundation for meeting future requirements.

MoonPay’s OWS represents a significant step toward a cohesive infrastructure for AI‑driven finance. Whether it becomes the de‑facto wallet layer for the agent economy will depend on the willingness of developers, platforms and regulators to converge on a shared, open‑source baseline.



Source: https://thedefiant.io/news/defi/moonpay-unveils-wallet-standard-for-ai-agents

spot_img

More from this stream

Recomended