Google Pay preps for AI agents with Universal Commerce Protocol

May 28, 2026 · DigitalEdu

Google Pay

Google Pay is rebuilding its payment infrastructure for a wave of AI-agent transactions. The new Universal Commerce Protocol and server architecture replace human-focused checkout pages with a stable, API-driven backend, letting autonomous agents handle purchases like flights or supplies without navigating visual interfaces.

Meeting note-taker Circleback adds a free tier to attract… NVIDIA and Google infrastructure cuts AI inference costs Pentagon inks deals with Nvidia, Microsoft, and AWS to… Kimi K3 open-weight model: China’s biggest AI is a… The Trump administration is supporting OpenAI in the NYT…

The latest updates introduce the Universal Commerce Protocol and a new server architecture, positioning Google Pay as a central clearinghouse for purchases executed by autonomous agents rather than human users.

AI agents – designed to perform tasks like booking flights or ordering supplies – cannot effectively navigate the multi-step, visually-oriented checkout pages built for human interaction. Google is attempting to replace this UI-dependent model with a stable, API-driven backend for machines.

This restructuring of Google Pay introduces several components:

• Universal Commerce Protocol (UCP): This is a new specification intended to standardise how AI agents communicate with payment and merchant systems. It creates a common language for initiating transactions, confirming inventory, and handling fulfillment details. The objective is to eliminate the need for developers to build bespoke integrations for every merchant or payment provider an agent might interact with.
• New Merchant Commerce Platform (MCP) server: Google is deploying a new server-side system to act as an intermediary. This MCP server manages merchant integrations and analyses transaction trends. For developers building agents, it abstracts away the complexity of the commerce backend. For Google, it centralises a vast amount of transactional data from agent-driven activities.
• Dynamic callbacks for Android native: To facilitate more complex checkouts, Google is enabling dynamic callbacks within its Android Pay API. This allows for real-time adjustments to an order (e.g. updating shipping costs based on a new address or recalculating tax) without forcing the user or agent to restart the entire process. It makes the transaction flow more resilient to mid-process changes.
• Expanded WebView support: The company is extending payment support within WebViews. This is a critical detail, as it allows transactions to be completed inside third-party applications, particularly social media platforms where conversational commerce is expected to increase. Agents operating within these environments can now execute payments natively.

Realities of machine-to-machine commerce

The concept of a customer journey, once defined by clicks and page views, now extends to an agent’s ability to parse product data and execute a transaction via an API.

Marketing leaders now have to consider “search engine optimisation” for machines. Product information, pricing, and availability will need to be presented as machine-readable data, not just persuasive copy for a human audience. If an AI agent cannot parse your inventory data to make a purchasing decision, your business becomes invisible in this new commercial channel.

The introduction of the MCP server also raises questions about data governance and vendor dependency. By routing transactions through its platform, Google gains a privileged view of commerce trends driven by AI agents.

CIOs must assess the long-term implications of building reliance on a proprietary protocol and a centralised data aggregation point. The convenience of a universal standard comes with the strategic cost of platform lock-in.

New architectures for security and trust

Authorising transactions initiated by an autonomous agent presents a new set of security challenges. A faulty or malicious agent could execute unauthorised purchases at scale. 

Google’s answer is the introduction of cross-device biometric authentication. This mechanism allows an AI agent to programmatically request human verification for a transaction. A user could receive a prompt on their phone to approve a purchase an agent has arranged on their laptop.

This approach establishes a “human-in-the-loop” security model for high-value or sensitive transactions. It provides a necessary kill-switch and audit trail for agent activities. Defining the policies for when an agent can act autonomously versus when it must seek human approval becomes a new area of corporate governance. These rules will need to be encoded into the agent’s operational logic, creating a direct link between business policy and software behaviour.

These latest updates to Google Pay are an early but concrete signal of the architectural changes required to support a machine-driven economy. Enterprises that continue to view their digital presence as a collection of websites for human consumption will be unprepared for this next phase of commerce.

See also: Google folds Display Ads into AI-first Demand Gen platform

Want to learn more about AI and big data from industry leaders? Check out AI & Big Data Expo taking place in Amsterdam, California, and London. The comprehensive event is part of TechEx and is co-located with other leading technology events including the Cyber Security & Cloud Expo. Click here for more information.

AI News is powered by TechForge Media. Explore other upcoming enterprise technology events and webinars here.

The post Google Pay preps for AI agents with Universal Commerce Protocol appeared first on AI News.

Source: Original Article

Frequently Asked Questions