Wallet
Security and privacy
The boundaries between your Wallet account, agent, and payment method.
Wallet keeps the agent’s authority narrow: the agent can propose actions, while you approve the authorization and Wallet protects the payment-method details.
Trust boundaries
You | Sign in, review the request, approve or decline an authorization, and manage cards and profile data. |
|---|---|
Your agent | Uses the MCP tools for the connected account. It cannot approve its own authorization or view card details. |
Yuno | Hosts card enrollment and retains sensitive card information. |
Wallet | Stores safe payment references, evaluates purchase intents, and issues the current temporary mock credentials. |
Local development
Only connect trusted MCP clients to a local Wallet server. Do not paste a card number, CVC, PIN, password, Wallet session token, or API secret into an agent conversation.
Release limitation
Temporary mock cards only
This version does not charge cards or contact merchants, processors, or payment networks. Its synthetic `000000` credentials are non-chargeable, are not derived from Yuno Vault cards, and do not work at real or sandbox processors.