Cashfree Adds WebMCP Tools to Hosted Checkout for AI Agents

Cashfree Payments announced on November 6, 2026, that its Hosted Checkout now supports WebMCP, allowing browser-based AI agents to read orders, navigate payment methods, display UPI QR codes and check payment status. The company said the tools can reduce the tokens required to complete a checkout by more than 40%.

The capability is built into Cashfree’s existing Hosted Checkout and is live on redirect checkout without merchant code changes. Checkout for Agents is rolling out in phases, with browser support and available tools subject to change. Cashfree describes itself as the first payments company in India to bring WebMCP to checkout.

Structured Tools Replace Simulated Clicks

Cashfree identified payment as a recurring obstacle in conversations with more than 50 founders building AI agents. On a conventional page, an agent must interpret buttons and fields, simulate clicks and respond to layout changes or pop-ups. Each additional step consumes tokens and creates another opportunity to stall or enter incorrect information, turning checkout friction into both a computing-cost issue for users and a potential lost sale for merchants.

WebMCP gives agents named tools that return structured results, reducing the need for visual interpretation. The checkout publishes six: get_checkout_summary, list_payment_methods, open_payment_method, back_to_payment_methods, show_upi_qr and get_payment_status. Their availability changes with the page and merchant settings, so agents need to read the live tool list rather than assume every option is present.

The order-summary tool returns the merchant name, currency, order amount, payable amount after offers, applied and available offers, and a masked phone number. The status tool reports not_started, pending, failed or success, but only for the payment started on the current page. Tools run in the shopper’s own browser checkout session, without API keys or a separate server, and cannot do anything the page itself cannot already do.

UPI Approval Stays with the Shopper

In the UPI flow, the agent reads the order and lists the payment methods enabled for it before requesting the QR code. Cashfree marks show_upi_qr as consequential, allowing the browser or agent to ask for confirmation before running it. The shopper must scan the code with any UPI app and approve the payment with their UPI PIN; the agent can then read the payment status. For other payment methods, the agent can list and open an option, but the shopper completes payment on the page.

Human intervention also remains necessary when checkout presents a convenience fee, payment-route choice, autopay setup or a decision about a pending previous payment. No tool independently moves money or accepts card numbers, CVV, one-time passwords or payment tokens. Results omit email addresses and cart items, while merchant-supplied text such as offer descriptions is marked as untrusted data rather than instructions for the agent.

Agent-assisted payments otherwise use the same checkout code, offers, fraud and risk checks, and error handling as a shopper-initiated payment. Merchants confirm them through the same Get Order API or payment webhooks before fulfillment. Because the tools reside on Cashfree’s hosted pages, an agent can use the same interaction pattern across merchants using supported Hosted Checkout pages instead of learning a separate payment flow for each one.

Browser and Checkout Limits Define the Rollout

Support requires a Chromium-based browser with WebMCP. On Cashfree checkout, the capability is available from Chrome 149 through an origin trial that Cashfree enables on its pages. Chrome’s WebMCP overview describes WebMCP as a proposed standard that uses JavaScript or annotated HTML forms to expose tools, with JSON Schema definitions for inputs and expected outputs, and positions the API primarily for local browser workflows with a human in the loop.

Only redirect-based Hosted Checkout pages opening at the top level of the browser are supported. Popup, inline, One Click and subscription checkouts do not publish the tools; embedded checkout runs in a cross-origin iframe, where WebMCP is disabled by default. The UPI QR tool is limited to the desktop layout, and the post-payment confirmation page exposes no tools. Tool names and inputs can change as the standard evolves.

The result is a bounded form of agentic commerce: agents gain a consistent way to read orders and prepare payments across supported merchants, while shoppers retain control of credentials, authorization and checkout exceptions. For merchants and agent developers, practical use therefore depends as much on browser support and checkout configuration as on the agent’s own capabilities.