x402, MPP, AP2, ACP, UCP and Visa TAP: What Are They Competing to Solve?

An agent buying data or a physical product can encounter x402, MPP, AP2, ACP, UCP and TAP. All relate to agent transactions, but a single ranking would obscure their different jobs.

Ask first: is this an API request or a physical item requiring shipping? Is the missing capability payment interaction, cart management, authorization evidence or recognition of an agent visiting a site?

This compares publicly documented focus areas, not proof that combinations are deployed or interoperable. Sources reviewed October 28, 2026. Check current versions before integration.

Name	Main focus	Typical question	Do not infer
x402	Paid resource requests and payment interaction	How does an API present requirements and handle payment data?	Built-in user budgets and complete after-sales support
MPP	Machine payment interaction and billing modes	How are a charge, session or subscription coordinated?	Interoperability with all x402 clients
AP2	Verifiable agent purchase and payment authorization	How are user permission and constraints verified?	A wallet or funds network
ACP	Agent and merchant commerce and checkout	How are carts, orders and payment data synchronized?	Automatic access to every AI platform
UCP	Capability discovery, negotiation and transaction lifecycle	How does a platform discover merchant capabilities?	Every transaction may occur without user confirmation
Visa TAP	Verifiable agent recognition and associated data	How does a merchant assess request origin and intent?	Agent recognition approves payment

This table describes emphasis, not a rigid layering standard. Scopes overlap and can change; examine the version and integration.

Scenario 1: paying for an API call

flowchart LR U[User sets budget] --> A[Agent requests data] A --> P[x402 or MPP coordinates paid request] P --> W[Compatible wallet or payment method] W --> S[Provider delivers under its terms]

x402 and MPP can both be candidates here. Compare SDKs, payment methods, networks, pricing, fees and support. Sharing HTTP 402 does not ensure interoperability. MPP’s mppx support for compatible x402 exact flows is a specific example, not a blanket guarantee; see MPP’s announcement, x402 HTTP specification and MPP sessions. Budget and key controls need additional design.

Scenario 2: buying a backpack for delivery

flowchart LR A[User expresses need] --> B[Agent and merchant negotiate product and checkout] B --> C[User confirms or supported authorization is verified] C --> D[Submit payment and create order] D --> E[Delivery and order status]

ACP or UCP might manage commercial interaction, AP2 might provide authorization evidence, and a merchant might use a TAP-like mechanism to recognize an agent. This is a functional illustration, not a claim that one platform uses all of them. UCP’s AP2 extension is a documented combination.

Overlap and complementarity

x402 and MPP both address machine access to paid resources. Compare actual methods, billing models and integration rather than assuming one name is more advanced.

ACP and UCP both cover agent commerce and checkout. Compare platform coverage, merchant systems, versions, functions and payment processors. Supporting one does not automatically mean supporting the other. See ACP and UCP.

AP2 and commerce protocols can complement each other: AP2 expresses and verifies authorization, while a commerce protocol manages checkout. Credentials depend on mutual implementation and trust. See AP2.

TAP and checkout protocols can also be combined: one helps validate requests, the other manages products and orders. A valid signature does not approve purchase contents, budgets or card transactions. See Visa TAP.

Practical selection checklist

Define the task: paid API call, metered service or shipped product?
Identify who supplies the agent, wallet, merchant service, processing and confirmation interface.
Verify versions, extensions, assets, networks and payment methods on both sides.
Establish who enforces budgets, holds signing keys and can expire or revoke authorization.
Test how timeouts, declines, non-delivery and duplicate requests are investigated.
Include processing, network, refund, staff and operational costs.

Protocols reduce coordination cost only when participants actually support them, permissions are enforced, and payment and delivery are traceable.

Further reading: x402 V2, MPP sessions, AP2, ACP, UCP checkout and Visa TAP.