Mastercard let an agent pay 9 times on one budget.Mastercard 让一个 agent 用同一个预算付了 9 次款。

A wallet amplifies mis-steered spend; the budget cap, not per-payment review, is your only control.

What changed, the best case it's safe, and the setting to check first

OUR READ

Giving an AI agent a wallet amplifies a mis-steered purchasing workflow as fast as a useful one. Per-transaction review disappears; the pre-set budget envelope is the only brake, and the loss inside it is yours.

WHAT HAPPENED

• Oct 20: Mastercard opened Early Access to Agent Pay for Machines — agents discover, negotiate and pay for digital services within a human-set cap (Mastercard; Decrypt).
• It runs on the x402 protocol: on a '402 Payment Required', the agent signs a voucher to pay within its limit.
• In a Cloudflare Connect demo, one agent made 9 payments to 2 providers on a single budget — research plus 8 images — with no separate accounts.

WHY IT MATTERS

A cap bounds your total loss, not misallocation. A bad plan or a prompt-injected instruction can burn the whole envelope on the wrong vendors before you look — and that cost is the operator's, not the network's.

A wallet does not give an agent judgment; it gives its mistakes a way to pay.

BEST CASE AGAINST US

Mastercard enforces the cap at the rail, not in the prompt — the infrastructure-level control experts recommend. With a network-enforced cap and a payee allowlist, the blast radius is bounded and auditable.

DO THIS WEEK

If you let an agent spend, enforce the limit outside the model: a hard cap plus an allowlist of approved payees, and log every payment to its triggering instruction. Start with a throwaway budget.

We'd revise if early-access deployments show network-enforced caps and allowlists hold against mis-steering and injection, with no material misdirected spend.

Research, not investment advice.