MoonPay's Open Wallet Standard Targets AI Payments

MoonPay just put a number on the problem it wants to solve: more than 15 organizations backed its new Open Wallet Standard, and the company says its platform already reaches over 30 million customers in 180 countries. That matters because AI agents can now make decisions fast, but payments still break down the moment they need a wallet that works across chains.

MoonPay’s answer is a non-custodial software layer for agentic payments. The pitch is simple: let AI agents hold value, sign transactions, and move across blockchains without exposing private keys to the model itself.

Why MoonPay thinks wallets are the missing layer

The agent economy has been getting plenty of attention, but payments have lagged behind the hype. Models can draft code, book meetings, and trigger workflows, yet they still need a trusted payment path before they can buy compute, settle invoices, or move funds onchain.

MoonPay says the Open Wallet Standard, or OWS, is built to fill that gap. The company launched it on March 23, 2026 as an open-source framework that keeps keys encrypted at rest, uses policy-based signing, and supports local-first storage. In other words, the AI can act, but only inside rules set by a human or an application owner.

• Open-sourced on GitHub, plus distribution through npm and PyPI
• Backed by 15+ organizations, including the Ethereum Foundation, Solana Foundation, and PayPal
• Supports eight chain families, including Bitcoin, Ethereum, and Solana
• Designed for policy-gated signing so spending limits can be enforced before a transaction leaves the wallet

The big idea is less about one more wallet SDK and more about a common contract for machines that need money. If an AI agent can work across chains with the same wallet logic, developers stop rebuilding the same plumbing for every ecosystem.

That is where MoonPay is making its bet. The company already sits in the middle of crypto payments for consumers and businesses, so it has a direct incentive to standardize the part of the stack that gets messy fastest.

Who is behind the standard

MoonPay is not pitching this as a closed product line. It is publishing OWS as open infrastructure and inviting other companies to build around it. That matters because standards only matter when other people adopt them, and MoonPay seems to understand that it needs allies, not just users.

The company says the standard has support from more than 15 organizations, including several major blockchain foundations and payment players. It also says OWS is available globally for developers through public code repositories, which makes it easier to inspect, fork, and test without waiting for a private rollout.

“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,” said Ivan Soto-Wright, CEO and co-founder of MoonPay.

That quote matters because it frames the product as infrastructure, not a feature. MoonPay is trying to define the layer where autonomous software meets money, and it wants that layer to be shared rather than proprietary.

The company also says it recently integrated Ledger hardware signing into its agent stack. That is a practical clue about where the market is heading: more automation, but with tighter controls around key custody and transaction approval.

What OWS changes for builders

For developers, the most interesting part of OWS is not the branding. It is the combination of non-custodial storage, encrypted keys, and policy gates that can keep an agent from draining a wallet just because a prompt went sideways.

That matters for any workflow where software needs to spend money on its own, including onchain commerce, automated treasury operations, and machine-to-machine settlement. It also matters for teams building across multiple chains, because fragmentation is one of the biggest reasons agent payment systems stay stuck in demos.

• MoonPay says it supports 8 chain families, which is a wider base than many single-chain wallet tools
• The company reports 500+ enterprise partners, giving it a larger distribution channel than most wallet startups
• MoonPay says its payments network reaches 180 countries, which suggests the standard is being built for global use from day one
• Keys remain hidden from the AI model, which reduces the chance that a prompt injection or model error exposes sensitive material

There is also a developer ergonomics angle here. If the same wallet standard works across frameworks, teams can spend less time on custom integrations and more time on policy design, transaction logic, and user experience.

That said, standards only matter if the implementation is boring in the best way. Developers want predictable signing, clear failure modes, and enough documentation to avoid turning wallet policy into another brittle custom layer.

How MoonPay compares with the rest of crypto infra

MoonPay is entering a crowded field, but the comparison set is a little unusual. It is not competing only with wallet apps. It is also competing with custody providers, payment processors, and infrastructure teams trying to make AI agents safe enough to touch money.

What gives MoonPay an edge is its existing distribution. A company with 30 million customers and 500+ enterprise partners can push a standard faster than a small protocol team can. But it still needs developers, foundations, and payment companies to treat OWS as more than a MoonPay initiative.

• Ledger focuses on hardware-backed key security, while MoonPay is pushing a software standard for agent wallets
• Circle has stablecoin rails and payments APIs, but OWS targets the wallet layer where agents actually sign
• OKX Wallet and other consumer wallets serve humans first, while OWS is built for autonomous software
• PayPal brings mainstream payments scale, but MoonPay is framing this as a cross-chain standard for developers

There is a clear strategic angle in that comparison. If OWS gains traction, MoonPay can sit underneath a lot of agent payment products without owning all of them. That is a better position than trying to win every wallet user one by one.

Still, standards are won in the details. The real test is whether other teams adopt OWS for production systems, especially when they need audit trails, spending caps, and chain-specific behavior that does not break under load.

What happens next

MoonPay has made a strong first move by turning agent payments into a standards problem instead of a one-off product problem. The next step is adoption: if developers use OWS for real agent workflows over the next few quarters, MoonPay could become a default layer for machine-to-machine crypto payments.

If adoption stalls, the standard becomes another well-meaning repo with a press release attached. My guess is the deciding factor will be whether payment teams can plug OWS into existing systems without rewriting their stack. If that works, expect AI agents to start paying for APIs, compute, and onchain services with far less human babysitting than today.

For builders, the takeaway is simple: agent payments are moving from theory to implementation, and wallet design is now part of the AI infrastructure conversation. The question is no longer whether agents will need money. It is which wallet standard they will trust when they do.

For more on crypto infrastructure and AI agents, see our coverage of AI agents and crypto payments and wallet security for autonomous AI.