A Map of the Agentic Payment Ecosystem

When an agent buys data, books a service or pays an API, the participants are often grouped together as “agent payment companies.” A wallet, a payment protocol and a card network have different jobs. Start with each participant’s role in the task and transaction, rather than memorizing product names.

flowchart TD U[User or company: goal and permissions] --> A[Agent: discover and choose] A --> C[Authorization and policy: is purchase allowed?] C --> W[Wallet or payment credential] A --> M[Merchant: product or digital service] W --> N[Payment network or blockchain] M --> V[Payment verification or processing] V --> N M --> D[Delivery, receipt and support] D --> U

This is a functional map. Arrows show possible relationships, not a required sequence; each layer need not be a separate product.

The layers

Layer	Question	Examples and boundaries
User and agent	Who defines the task and who chooses?	The user can request recommendations or authorize a bounded purchase
Authorization and policy	Is the purchase permitted?	Budget, recipient, duration and approvals; enforcement differs by product
Wallet and credentials	What payment capability is used?	Cards, accounts or blockchain signatures; a wallet may not directly hold funds
Commerce and payment interaction	How are products, checkout and payment requirements expressed?	Standards handle different information and apply to different situations and versions
Networks and settlement	How do messages and funds move?	Card networks or blockchains, depending on the path
Delivery and records	What was bought and was it delivered?	Orders, API responses, receipts, reconciliation and support

Where do protocols and companies fit?

x402 concerns payment requirements and interaction when requesting a resource; AP2 defines verifiable records related to checkout and payment authorization. They may work together in different architectures, but names alone do not prove that two products interoperate.

A company’s wallet, payment service and company profile are separate records. Compare wallets on control and integration; use company profiles to understand the broader ecosystem. Do not add protocols, products and companies together and call the result a count of competing products.

Where to go next

Follow a complete example purchase.
Understand user authorization.
Learn what an agent wallet does.
Explore x402 for a concrete protocol example.

A real implementation must still establish who enforces rules, who pays network costs, how failures are handled, and what refund or dispute routes exist. A diagram helps locate questions; it cannot verify an implementation.

Sources reviewed October 28, 2026. The diagram is conceptual, not a product architecture or test.