When an AI agent needs to pay for a cup of coffee, the industry is currently split between two irreconcilable visions of how commerce should function. One camp, anchored by the x402 protocol, treats payments as machine-to-machine data packets. The other, led by Google’s Universal Commerce Protocol (UCP) and Mastercard’s AP4M, attempts to wrap the existing, regulated world of credit cards in a new digital interface.
The x402 protocol, which processed over 100 million transactions on Base by Q1 2026, is built on the premise that financial friction is a bug to be eliminated. However, its success is strictly confined to the machine-to-machine layer. There is no public audit of “Category 3” transactions — actual buyer-seller commerce.
Google’s UCP operates at the checkout layer, preserving the traditional merchant-of-record model. Where x402 asks the agent to hold a crypto wallet, UCP asks the agent to negotiate capabilities with the merchant.
The developer’s choice reveals where they believe the agent economy begins. If you view agent commerce as an extension of cloud computing, you build on x402. If you view it as an extension of retail, you build on UCP. Stripe’s decision to support both paths is a tacit admission that the industry has no consensus.
According to a 2026 survey by Product.ai, only 14% of U.S. consumers trust an AI to execute a purchase on their behalf. The technology is currently optimized for machine-to-machine efficiency, but it has yet to solve the human-centric problem of trust.