How Do Autonomous Agents Pay?

Autonomous agents pay through machine-native rails: a wallet the agent controls under a policy, programmable money such as stablecoins that settles without a human at a terminal, and protocols like HTTP 402 that let a server charge for a call. The distinguishing requirement is not the rail but the gate — a policy plane that checks a proposed payment against authority, limits and risk, and either allows it, denies it, or escalates to a human, before anything is signed.

Rail

Wallet + programmable money (e.g. stablecoins)

Protocol

HTTP 402 / x402 for pay-per-call

The gate

Policy before signing: allow / deny / escalate

Record

Signed receipt + ledger entry

The click becomes a policy

A human wallet asks a person to approve each payment. An agent cannot pause for a click on every call, so the approval becomes a policy plane: the agent proposes a structured operation, the policy checks it, and only then does the signer act. Escalation to a human is a first-class outcome for anything out of policy, never a failure.

Credit cards and bank accounts were not designed for this. Machine-to-machine commerce wants payments that are programmable, gated by policy, idempotent, and accompanied by a machine-readable receipt — which is why stablecoins and HTTP-native payment protocols keep appearing in agent designs.

Related standards

x402 / HTTP 402AP2

Questions

Can AI agents have wallets?

Yes — an agent wallet is a wallet the agent operates under a policy that sets what it may spend and when a human must approve. The policy plane, not the key, is what makes it safe.

Why do agent payments need receipts?

So a third party can verify what was paid and why, and so the ledger can record it. An economic action with no receipt cannot be audited.