AI Agents Just Got Their Own Bank Accounts. Here's What Changes.
MoonPay just shipped something that didn't get enough attention.
The Open Wallet Standard (OWS): an open-source protocol that gives AI agents a single encrypted vault for holding funds, signing transactions, and paying for services across every major blockchain.
Not a closed platform. Not a managed service. An open specification that anyone can implement.
This is the missing piece in the agent economy. And it changes what's possible.
What OWS Actually Does
Before OWS, agents had a problem.
They could request services, but they couldn't pay for them autonomously. Every transaction required human approval, API keys, or payment routing through a parent account.
OWS solves this with a wallet primitive:
- Agent-owned wallets — Keys controlled by the agent, not a human
- Multi-chain support — Works across Ethereum, Solana, Bitcoin, and major L2s
- Encrypted storage — Keys secured, not exposed in plaintext
- Transaction signing — Agents can authorize payments without human intervention
- Service discovery — Agents can find and pay for services programmatically
The key insight: this is an open specification, not a hosted service.
Anyone can spin up an OWS-compatible wallet. Anyone can build services that accept OWS payments. The ecosystem doesn't route through MoonPay—it routes through an open standard.
Why This Matters More Than Agent Credit Cards
Stripe's Machine Payments Protocol (MPP) lets agents respond to HTTP 402 challenges.
Visa's agent credit cards give autonomous spending power.
Ramp's corporate cards let AI book travel and software.
All of these require a human to set up an account, link a card, and authorize the agent.
OWS is different:
- No bank account required
- No human in the approval loop
- No centralized platform that can revoke access
- Multi-chain by design (not locked into Visa's network)
The agent gets a wallet. The wallet holds funds. The agent signs transactions. Done.
The Architecture
OWS is structured as seven modular sub-specifications:
- Key Management — How agents generate, store, and use cryptographic keys
- Wallet Operations — Balance queries, transaction history, fee estimation
- Transaction Signing — Standardized signing flow for all supported chains
- Service Discovery — How agents find services that accept OWS payments
- Intent Propagation — Human authorization constraints (optional layer)
- Recovery — What happens when an agent loses keys
- Interoperability — How OWS wallets talk to each other
Each layer is optional. You don't need to implement all seven.
What This Enables
Before OWS:
An agent wants to buy API credits from a service. It needs:
- A human to create an account
- A credit card linked to that account
- Approval for the purchase amount
- Manual tracking of spending limits
After OWS:
The agent generates a wallet, receives funds, finds the service, signs the transaction. No human required at any step.
Use cases that unlock:
- Agents buying compute resources on-demand
- Agents paying for data access without human approval
- Agents settling micropayments for services
- Agents operating autonomous businesses with financial independence
- Agents participating in DAO governance with real voting power
The Stack Comes Together
We now have three layers:
Layer 1: Agent Identity (World AgentKit, Decentralized ID)
- Proves who owns the agent
- Attests to authorization bounds
Layer 2: Trust/Intent (Mastercard/Google Verifiable Intent)
- Proves the agent is acting within human-approved bounds
- Cryptographic proof for each transaction
Layer 3: Payment Execution (OWS, MPP, Agent Cards)
- Actually moves money
- Signs transactions
- Settles payments
OWS is the execution layer. Identity tells you who's spending. Verifiable Intent tells you it's authorized. OWS makes it happen.
The Remaining Gaps
OWS is infrastructure, not a complete solution.
Still needed:
On/off ramps — How do agents get funds in the first place? Humans still need to seed wallets.
Recovery mechanisms — What happens when an agent loses its keys? The spec includes recovery, but implementation matters.
Regulatory clarity — Agents with bank accounts raises questions about liability, taxation, and legal status.
Insurance — If an agent loses funds, who covers the loss?
Audit trails — Enterprises need visibility into agent spending for compliance.
These aren't OWS problems to solve. They're ecosystem problems that become visible once the infrastructure exists.
What Comes Next
The wallet primitive was the last missing piece in the agent payment stack.
With OWS underneath and MPP on top, the plumbing for machine-to-machine commerce is now complete enough for real deployment.
The immediate second-order effect: Stablecoin volume from autonomous agents could become a measurable share of on-chain activity within the next twelve months.
The longer-term question: Whether twenty-plus contributors can maintain consensus on an evolving spec. The governance of open standards is harder than the technical implementation.
The Takeaway
MoonPay built the wallet layer and gave it away as open source.
The smart move: they're not competing on wallet infrastructure. They're competing on the services that run on top of it.
OWS makes agents financially independent. The question isn't whether agents will have their own wallets—it's what they'll buy when they do.
The agent economy just got its bank account. The ATM is next.
Top comments (0)