Quick answer
Cloudflare’s forthcoming Virtual Wallet design names three useful controls: allowances, merchant allowlists, and maximum transaction size. Treat them as a starting layer, not a complete payment safety system.
Because wallet execution is not yet established by the announcement, use this guide for policy design and the readiness checker for a local pre-launch review.
Minimum policy dimensions
Define and enforce:
- total allowance by agent, user, team, purpose, and time window;
- maximum transaction and cumulative merchant amount;
- allowlisted merchant identity, payment address, network, asset, and resource type;
- approved price range and variance from a quoted amount;
- rate limits, concurrency, retry count, and idempotency key;
- separate read, quote, sign, settle, refund, and withdrawal permissions;
- human approval thresholds and an independent emergency stop;
- receipt, settlement, balance, and resource-delivery reconciliation.
Do not let the agent increase its own cap, edit the allowlist, change the destination after approval, reveal its signing key, or treat an untrusted page instruction as payment policy.
Handle anomalies without expanding authority
Cloudflare describes human review for unexpectedly fast spending and manual overrides. Route alerts to an owner who can inspect the original task, merchant, price, settlement, resource, and previous activity.
If the spend was intended, apply a time-bound, purpose-bound override rather than silently raising the permanent limit. If it was not intended, revoke keys, stop the wallet path, preserve evidence, reconcile transactions, and review prompt-injection and tool-authorization controls.
Test failure paths
Before money can move, test duplicate requests, timeouts after signing, settlement without resource delivery, changed price or destination, exhausted allowance, stale quote, expired key, reviewer absence, compromised agent, incomplete receipt, and emergency revocation.
Read Account Wallet vs. Virtual Wallet for ownership and the x402 guide for payment roles.
Frequently asked questions
Which Virtual Wallet controls did Cloudflare announce?
Cloudflare names allowances, allowlists, maximum transaction sizes, overall delegated spend caps, anomaly review, and human override requests in its forthcoming design.
Is a spending cap enough to make agent payments safe?
No. Add merchant and purpose scope, rate and time limits, credential isolation, idempotency, price validation, receipts, monitoring, revocation, approval, and incident handling.
Should an agent be able to raise its own limit?
No. Limit changes and one-time funding overrides should require an independently authorized human or service outside the agent’s own compromised path.
Official sources
Source check: August 12, 2026. Recheck wallet availability, control semantics, key model, transactions, networks, assets, and incident support.