Why aren't wallets enough for agent payments?

A wallet only signs. Production agent payments need a policy layer in front (budgets, allowlists, signer isolation) and an operations layer behind (receipts, settlement, audit, failure handling). Half the stack lives below the signature.

What fields should an agent-payment receipt have?

Minimum: request_id, amount, asset, chain, recipient, signer address, timestamp, status (pending/confirmed/voided/refunded), and settlement_ref (tx hash, channel state hash, or facilitator ID). Receipts must be addressable via GET /receipts/ and retained for years.

When should I use channel settlement instead of per-request settlement?

Channel settlement (AMP-style) wins when individual customers hit your endpoint hundreds or thousands of times per session. For 1,000 calls, per-request settlement needs ~1,000 on-chain transactions; channels need about three. The trade-off is more state to operate: dispute windows, watchtowers, force-close timeouts.

What audit surface do agent-payment APIs need?

One boring endpoint: GET /usage?address=...&from=...&to=... returning paginated receipts in a stable, versioned schema, accessible to the signing address itself. The customer's compliance team will eventually ask for it. Build it now; CSV export comes later if requested.

AI Payments

After the Signature: Receipts, Settlement, and Audit for AI Agent Payments

May 8, 2026

•

9 min read

•

Aggelos Kappos(Founder @ QBT Labs)

AI Agent PaymentsReceiptsSettlementAudit Logsx402AMPPayment InfrastructureStablecoin Micropayments

Loading article...

AI Payments

How API Providers Can Monetize AI Agents

Subscriptions and API keys were built for humans, not agents. A practical guide to x402, AMP, and MPP — plus a concrete provider checklist for shipping agent-native pricing in under a week.

AI Payments

Beyond the Wallet: A Builder's Guide to Policy-Controlled Agent Payments with x402

Giving an agent a wallet is the easy part. Production agent payments need budgets, allowlists, signer isolation, receipts, and policy before any signature is produced.

AI Payments

Why AI Agents Still Can't Work Alone: The $0 Problem

AI agents can reason and plan, but they can't pay. x402 lets agents pay for APIs mid-workflow — no wallets, no humans.

Related Articles

How API Providers Can Monetize AI Agents

Beyond the Wallet: A Builder's Guide to Policy-Controlled Agent Payments with x402

Why AI Agents Still Can't Work Alone: The $0 Problem