What Matters
Machine-to-machine payments require more than a wallet. Software must discover a price, prove authority, choose an asset and network, settle once, receive the service, reconcile the outcome and handle disputes. Stablecoins and x402 can reduce human checkout friction, but they do not remove budgets, identity or accounting.
DN Evidence Block
Reviewed: 20 November 2026. Primary evidence: x402 and Coinbase Developer Platform documentation, Circle stablecoin-payment materials and ERC-4337.
Boundary: protocols, networks, supported assets, fees and compliance requirements change. This is an architecture guide, not a guarantee of settlement or legal availability.
Six Payment Patterns for Agents
| Pattern | Best suited to | Settlement | Main control |
|---|---|---|---|
| Prepaid balance | Repeated calls to one provider | Offchain ledger, periodic funding | Top-up and exposure limit |
| Subscription or invoice | Known business counterparties | Card, bank or stablecoin invoice | Contract and reconciliation |
| x402 request payment | Payment-gated HTTP APIs and tools | Structured 402 challenge and onchain settlement | Per-resource price and approval |
| Smart-account payment | Bounded autonomous wallets | UserOperation, paymaster or token payment | Session key and spending policy |
| Batch or channel settlement | High-frequency low-value calls | Vouchers or accumulated settlement | Credit exposure and close-out |
| Escrow or milestone | Delayed or subjective services | Release after evidence or approval | Acceptance and dispute process |
1. Machine Discovery Needs a Payment Contract
The buyer agent needs a machine-readable description of the resource, price, asset, network, expiry, recipient, input and expected output. x402 uses HTTP 402 Payment Required with structured payment requirements, while discovery systems can expose resources and schemas to agents.
Discovery metadata is an advertisement, not proof of quality. The client should verify the domain, service identity, payee and output schema before approving payment.
2. Authority Must Be Narrower Than the Wallet Balance
A machine wallet should use a session key, smart-account module or policy service that limits value, asset, network, payee, time and method. A model prompt should not be the only barrier between a tool call and an unrestricted transfer.
High-value payments, new payees, recurring commitments and changes to limits should require external approval. Separate the owner or recovery key from the runtime.
3. x402 Is a Payment Loop, Not a Business Contract
An x402 client requests a resource, receives payment requirements, creates a payment payload and retries. A facilitator can verify and settle before the server returns the resource. This is well suited to APIs and tools with deterministic delivery.
The protocol does not decide whether the price is fair, the service is accurate or a refund is owed. Those questions require product terms, evidence and support.
4. Stablecoin Choice Is a Risk Decision
Agents should identify the issuer, exact contract, chain, decimal precision, redemption terms and bridge status. A similarly named wrapped token can have different issuer and bridge risk. The payee may also be unable to use the asset or network.
Maintain an allowlist and test small payments. Price goods in a unit the parties understand and record the exchange rate when accounting requires fiat reporting.
5. Idempotency Prevents Double Payment
Every purchase should have an immutable request or invoice ID. If a network, API or facilitator times out, the agent must check whether payment settled and whether the service was delivered before retrying.
The seller should reject duplicate IDs or return the original result. The buyer should reconcile wallet receipt, service receipt and local job state.
6. Receipt Design Matters
A useful receipt links buyer, seller, resource, amount, asset, network, transaction or settlement reference, request ID, timestamp and outcome. It should preserve enough evidence for accounting, disputes and incident review without exposing secrets.
Signed receipts can support later reputation and credit decisions. A transaction hash alone does not prove that the correct service was delivered.
7. Batch Settlement Creates Credit Risk
Batching or channels can make sub-cent interactions economical by accumulating claims before settlement. The trade-off is counterparty exposure between checkpoints. Set maximum outstanding value, settlement frequency and a stop condition when a voucher or payment fails.
8. Compliance and Tax Still Apply
Machine speed does not exempt payments from sanctions, consumer, money-transmission, tax, Travel Rule or recordkeeping requirements. The required controls depend on parties, geography, purpose and provider role.
Do not automate identity or location evasion. Route uncertain transactions to review and retain the exact entity and product used.
DN Rule
Payment is complete only when settlement and service outcome are reconciled. A successful transaction with a failed API response is an exception, not success.
DN Machine-Payment Authority Planner
Score one payment workflow. Higher scores indicate broader authority and weaker outcome controls.
Worked Example
A research agent discovers a paid market-data endpoint priced at 0.02 USDC per call. Its policy approves the domain, Base network, USDC contract, $2 daily cap and 20-cent outstanding batch limit. Each request has an idempotency key.
The endpoint times out after settlement. The agent checks the resource receipt before retrying and obtains the original result. Without that check, the machine could pay twice for one output.
Methodology and Limitations
DN mapped machine payments across discovery, authority, settlement, receipts, accounting and disputes. We did not audit a facilitator, stablecoin or wallet implementation. Legal obligations vary by role and jurisdiction.
Frequently Asked Questions
What is a machine-to-machine payment?
A payment initiated and received by software services under pre-authorized rules, with machine-readable price, identity, receipt and settlement evidence.
Does x402 mean an agent can spend without limits?
No. x402 can automate payment-gated HTTP requests, but the client should enforce budgets, approved assets, networks, payees and per-request approval policies.
Are stablecoin payments final immediately?
Blockchain settlement may be fast, but business finality also depends on confirmations, token issuer risk, reversals in offchain systems, compliance and the service outcome.
How do agents avoid paying twice?
Use immutable request IDs, idempotency keys, payment receipts, service outcome reconciliation and a rule that a timeout is not proof of failure.
When is escrow needed?
Escrow is useful when delivery is delayed, subjective or disputed. Low-value deterministic API calls may use immediate payment with receipts instead.
Primary Sources
Editorial disclosure: no wallet, stablecoin issuer or payment protocol paid for inclusion.