Cashfree Adds Six WebMCP Tools So Browser Agents Can Finish Checkout

Posted on 6th Nov 2026 11:13:39 in Business, Digital Marketing

Tagged as: Cashfree, WebMCP, payment gateway, AI agents, UPI, hosted checkout, online sellers

Cashfree Payments said on November 6 that its Hosted Checkout now publishes a set of tools through WebMCP, a proposed browser standard that lets a web page expose its actions directly to an AI agent working in the same tab. In practice, an agent can now read the order, list the payment methods enabled for it, open one, put the UPI QR code on screen and check whether the payment went through, instead of reading the screen and simulating clicks.

The capability is switched on for redirect-based Hosted Checkout and needs no code change from merchants. Popup, inline, One Click and subscription checkouts do not publish the tools. The shopper still approves every payment: no tool can move money on its own, and a UPI payment still has to be scanned and approved with a UPI PIN.

What Cashfree Actually Shipped

The checkout page registers six named tools, each with a plain-language description, a defined set of inputs and a structured result. That structure is the whole point. An agent no longer has to guess what a button does from a screenshot.

• get_checkout_summary is read-only and returns the merchant name, currency, order amount, the payable amount after offers, the offers applied and still available, and a masked phone number. It is available on every checkout page.
• list_payment_methods returns the payment methods enabled for that order and the tools that work for each one, and lists UPI QR as upi-qr when the QR box is on the page.
• open_payment_method opens a method from that list, doing exactly what a shopper's click would do.
• back_to_payment_methods returns to the main checkout page, the same as the back arrow.
• show_upi_qr displays a QR code for the payable amount, the equivalent of clicking to see the QR. The shopper scans it and approves with a PIN.
• get_payment_status reports not_started, pending, failed or success, but only for the payment started on the current page.

The list of live tools changes as checkout moves between pages, and it also depends on the merchant's own settings, so an agent is expected to read the current tool list rather than assume every option exists. Cashfree warns that tool names and inputs can change as the standard evolves.

Why a Tool List Beats a Screenshot

On an ordinary checkout page, an agent works the way a person would: it reads the rendered page, finds the right element, clicks it and then copes with whatever appears next. Every one of those steps costs tokens, and every one is a chance to stall. A layout change, a theme update or a pop-up that nobody anticipated is enough to break the flow, and the agent hands the task back to the shopper at the worst possible moment.

WebMCP replaces that with a call and a structured answer. Cashfree says the approach can cut the tokens needed to complete a checkout by more than 40 per cent. It also says payment came up repeatedly as an obstacle in conversations with more than 50 founders building AI agents, which is the commercial reason a payments company would build this now rather than wait for the standard to settle.

There is a merchant-side argument too. An agent that reaches the payment step in one call is an agent that is less likely to abandon the order, and because the tools sit on Cashfree's hosted pages rather than in each merchant's integration, the same interaction pattern works across every merchant on supported checkout. An agent that learns to pay on one store can pay on the next.

What the Agent Still Cannot Do

The design deliberately stops short of handing over the payment. The tools run in the shopper's own checkout session, with no API keys and no separate server, and each one can do only what the page itself can already do. None of them accepts card numbers, a CVV, a one-time password or a payment token.

Cashfree marks the QR tool as consequential, which lets the browser or the agent ask the shopper to confirm before it runs. When checkout throws up a convenience fee, a choice of payment route, an autopay setup or a decision about a pending earlier payment, the agent cannot answer on the shopper's behalf; it learns that the shopper has to respond on the page. Results mask the phone number and leave out the email address and the cart items, and merchant-written text such as an offer description is flagged as untrusted content so an agent treats it as data rather than as an instruction.

Agent-started payments run through the same checkout code as any other payment, so offers, fraud checks, risk checks and error handling behave the same way. Merchants confirm the order through the Get Order API or payment webhooks before fulfilment, exactly as they do today.

The Limits That Decide Whether a Merchant Is Covered

The rollout is narrower than the announcement headline suggests, and the details matter for anyone planning around it.

• It works only in Chromium-based browsers that support WebMCP. In Chrome, it is available on Cashfree checkout from Chrome 149 through an origin trial that Cashfree enables on its pages.
• Only checkout pages that open at the top level of the browser window publish the tools. Embedded checkout runs in a cross-origin iframe where browsers disable WebMCP by default, so popup, inline, One Click and subscription checkouts are out.
• The UPI QR tool is not available on the mobile layout of checkout, where the QR code does not sit on the main page. Desktop UPI QR payments are the supported path.
• The confirmation page after a successful payment publishes no tools at all, and payment status covers only the payment started on the current page.
• Cashfree describes the rollout as phased, with browser support and the available tools subject to change.

Where This Sits Against Indian Checkout Reality

India's payment behaviour is unusually concentrated on one rail. The National Payments Corporation of India has said UPI processes more than 24.5 billion transactions a month, valued at around Rs 30 lakh crore, and accounts for about 89 per cent of all digital transactions. A checkout design that treats UPI QR as the one payment step an agent can actually complete is, in that context, covering the default case rather than an edge case.

Cashfree describes itself as the first payments company in India to bring WebMCP to checkout. That is a company claim, not an independently verified ranking, and the standard itself is still a proposal, with Chrome documenting WebMCP as a way to expose tools through JavaScript or annotated HTML forms, with JSON Schema definitions for inputs and expected outputs, aimed at browser workflows with a human in the loop.

One inconsistency is worth noting for anyone who asks their gateway for reports. Cashfree's announcement says the browser marks actions taken through its WebMCP tools as agent actions, so merchants can tell agent-assisted payments apart from direct ones. Its developer documentation says the opposite in plainer terms: agent-assisted payments are standard checkout payments and, in its words, are not marked separately from other payments. Until that is reconciled, do not assume your settlement or dashboard reports will isolate agent-led orders.

What an Online Seller Should Do This Quarter

• Find out which Cashfree checkout you actually run. If integration uses redirect, you are covered already. If it opens in a popup or inline, the tools do not publish, and switching is a design decision rather than a settings toggle.
• Stop treating offer configuration as an afterthought. The order summary an agent reads includes the offers applied and those still available, so discounts that only exist in a banner, a support reply or a coupon code whispered on WhatsApp are invisible to the agent's view of the order.
• Keep fulfillment tied to the confirmation, not the intent. An agent opening a payment method is not a payment. Fulfil on the Get Order API response or the webhook, as your current process already should.
• Test the desktop UPI QR path yourself. It is the only payment step an agent can complete end to end, and it is unavailable on the mobile layout.
• Do not build a parallel "agent checkout". The value here is that the existing page is now legible to an agent, which means the work is in keeping the page clean, the offers configured and the payment methods enabled.

The Bigger Shift

For two decades, a checkout page was written for a human eye: buttons, labels, pop-ups and a layout that had to persuade as much as it had to function. WebMCP adds a second interface to the same page, one that machines call directly, and the first version of it is deliberately modest, covering reading, navigation and the start of a payment rather than the payment itself.

That modesty is the interesting part. The tools describe what the page already does, they cannot exceed it, and the shopper keeps the PIN. If the pattern holds, the next contest in Indian e-commerce will not be over who has the best checkout page but over whose checkout a machine can finish without a person stepping in, and the merchants who notice that early will be the ones who configured their offers, payment methods and confirmations for it.

Sources

• Cashfree Payments — Cashfree Hosted Checkout Is Now Agent-Ready with WebMCP
• Cashfree Developer Documentation — Checkout for AI Agents with WebMCP
• Unite.AI — Cashfree Adds WebMCP Tools to Hosted Checkout for AI Agents
• Chrome for Developers — WebMCP overview
• Moneycontrol — NPCI launches agentic AI platforms for UPI partners