An AI agent can find, compare and prepare an order, but in 2026 a person still approves the payment on almost every path: your chat checkout, the assistant's cart, a browser agent, or a signed mandate.
Who authorizes the payment when an AI agent orders from your site?
Published November 4, 2026 · Last reviewed November 4, 2026
AI agents can find, compare and prepare a purchase on your website, but in 2026 the payment authorization still comes from a person on almost every path. What changes is where and when that person says yes. On your own site, a site agent prepares the order and hands the buyer a checkout link to pay. In an assistant’s cart, such as Google’s Universal Cart or Copilot Checkout, the buyer approves on the assistant’s screen and you stay the merchant of record. When a browser agent such as Chrome auto browse fills in your checkout page, it is designed to stop for confirmation before a purchase. A charge with nobody watching happens only inside limits the person approved in advance: an AP2 mandate under Google’s Agent Payments Protocol, now at the FIDO Alliance, a card-network agent token or a wallet limit. Services follow the same rule: the agent prepares the booking, the person pays. Below, as of November 4, 2026, we take the four paths one at a time from the site owner’s side, then who pays when an order goes wrong, the services case and seven things to set up on your site.
Site owners are asking because the pitch has moved. Agentic site products, ours among them, now say that visiting AI agents can ask questions and then book a demo, place an order or start a trial.1 Our stake, up front: Tobira publishes this blog and sells a site agent that can take payment in the chat; it comes up in Path 1 and in the services section. The follow-up from a finance lead or a founder is obvious: if a ChatGPT or Gemini session places that order, who said yes to the charge, and what does my business see?
This is not a protocol explainer; the agent payments stack covers the rails for builders. The question here is at which step a person authorizes the money, and what your site should do around it.
Why a person still approves the payment
Three forces keep a person in the loop, and none of them is going away this year.
The first is the payment system itself. Card networks, issuers and processors are built around a cardholder who authorizes a charge and can dispute it. When an agent is involved, the networks have chosen to extend that model rather than replace it. Mastercard’s Agent Pay registers and verifies agents before they can pay and promises consumers control over what an agent may buy.2 When Google and Mastercard brought their agent payment work to the FIDO Alliance in April, Mastercard’s chief digital officer, Pablo Fourez, set the bar: “user intent must be explicit, verifiable and trusted.”3
The second is product design at the big platforms. With Shopify’s Shop MCP, an agent completes a Shop Pay checkout after the signed-in shopper confirms the total and payment method,4 and the browser agents and Stripe tools in Path 3 stop at the same point.
The third is the buyer. In G2’s 2026 survey of more than 1,000 B2B software buyers, 47% would let agents research and recommend while people keep all final decisions, 9% were comfortable letting agents execute purchases within approved guardrails, and 2% would let them buy without approval in advance.5 Consumers are warier still. In an April 2026 Forrester survey of online adults in the US, UK and Canada, three-quarters were uncomfortable letting an AI agent complete a purchase and pay on its own, even with spending limits set in advance; their comfort, principal analyst Lily Varon wrote, “stops short of letting the agent actually complete a payment.”6 An agent that pays without asking would be solving a problem few buyers say they have.
The approval has not moved to the machine. It has moved to new screens, and your job is to know which one your buyer is looking at.
Path 1: the buyer pays inside your site agent’s chat
This is the path you control most. A site agent sits on your website, answers people and the AI agents that come on their behalf, and carries the conversation to a booking or a checkout without sending anyone to a contact form.
Tobira Site Agent is one example. Its product page describes the step in one line, “Books demos and takes payment. A calendar and checkout right in the chat,”1 and its comparison with a typical AI chatbot puts booking and payment inside the chat, and taking an AI agent’s order, on Site Agent’s side. Payments for consultations and services are listed on the Business and Premium plans. Booking and payment in the chat are the addressable half of an agentic site, explained in our readable vs addressable explainer.
Who approves the charge when the order comes from an AI agent? Tobira’s guest contract, the machine-readable file that tells visiting assistants what they may do, answers in one line: the checkout link it returns is a handoff to the person, and “an AI visitor never completes payment.” The same file sets payment_is_human_action to true and defines the booking states a visiting agent moves through: lead_captured, booking_prepared, payment_pending and booking_confirmed. In payment_pending, requires_user_payment is true and the booking provider returns an HTTPS checkout link.7
Approval here is ordinary card approval: you are the seller, your processor handles the payment, and disputes follow the usual rules. The demo row on our own product page that shows an order paid via Gemini illustrates an outcome; it is not evidence that an agent paid. Under this contract the assistant brings the order to the till and the person pays.
Path 2: the assistant runs its own checkout
On the second path the buyer never reaches your site. The assistant shows the product, builds the cart and takes the payment in its own interface, and your business receives an order.
Here the buyer approves in the assistant, with a wallet they already trust there:
- Google Universal Cart launched in the US on October 15, 2026, in Search and the Gemini app, with checkout built on the Universal Commerce Protocol (UCP). The shopper pays with Google Pay in the cart, or moves the items to your own cart and finishes on your site.8
- Copilot Checkout (with PayPal, Shopify and Stripe at its January 2026 launch) and Perplexity Instant Buy (through PayPal) let the buyer pay inside the chat.910
- ChatGPT went the other way. OpenAI launched Instant Checkout in September 2025 and in March 2026 stepped back, letting merchants use their own checkout while ChatGPT focuses on product discovery (discover in AI, buy on your site covers the shift).11 Its developer docs now recommend checkout on the merchant’s own domain, with an in-chat payment sheet in private beta for select marketplaces.12
Card numbers rarely travel on this path. The Agentic Commerce Protocol (ACP), co-developed by OpenAI and Stripe and still labeled beta (latest stable version April 17, 2026), passes “secure payment tokens between buyers and businesses through AI agents”: a single-use token capped at an amount, tied to one checkout and set to expire.13
Whichever brand it is, you stay the merchant or seller of record: you fulfill the order, send the confirmations and handle customer support.89 What you do not see is the moment of approval. The buyer said yes on Google’s, Microsoft’s or PayPal’s screen, so your evidence of consent is whatever that platform and your processor pass along with the order.
These channels can be on before you decide: Shopify, for example, switches direct checkout on in several AI surfaces by default for eligible stores and lets the merchant turn it off.14 Most B2B and services sellers are not in these carts yet (OpenAI, for one, currently approves commerce plugins in ChatGPT only for physical goods), which is why the next two paths matter more for them.12
Path 3: a browser agent reaches your checkout page
On the third path an agent drives a browser for the person and lands on your normal checkout page. Nothing about your site changed, but the visitor filling in the form is software working inside a human’s session, often with that human’s saved cards.
Google’s browser agents draw the line in the same place. Chrome auto browse, launched in preview for US AI Pro and Ultra subscribers in January 2026 and since extended to Android and to India, is designed to pause and ask for confirmation, or hand the step back, before tasks such as purchases.15 Gemini Spark hands sensitive actions such as payments back to the user.16 Outside Google, OpenAI’s documentation for Site tools in ChatGPT says its normal confirmation policies still apply to consequential actions such as purchases.17 The agent can get the buyer to the payment screen; the buyer confirms or completes the payment.
Stripe has made this explicit for its own checkout pages. Through WebMCP, the draft browser standard that lets a page register structured tools for agents, Stripe’s hosted checkout and payment forms let an agent read the amount due, pick a payment method, fill the form and, where Stripe controls the submit button, start the payment. The submission tool carries WebMCP’s consequentialHint, and Stripe tells agent builders to get the user’s confirmation before calling it: “Don’t interpret the hint itself as confirmation.”18 Stripe labels the capability experimental, and WebMCP is a W3C Community Group draft, not a W3C Standard.19
Shopify has done the same for its merchants. Since September 28, 2026, eligible Shopify checkouts register WebMCP tools that let a browser agent read and update the checkout and submit it only after the buyer confirms; when 3D Secure or other buyer input is needed, control goes back to the buyer, and merchants have nothing to configure. Shopify tells agent builders to show the buyer the current order and total before placing it: “If the total changes, then ask again.”20
What changes on your side:
- The approval prompt is not yours. The browser or the agent shows the “confirm this purchase?” step, in its own words. Your page has to make that step easy to get right: the total, what is being bought, and any renewal terms in plain text the agent can read back to the person, not hidden in an image or a tooltip.
- A hosted checkout gives agents a structured way in. If you use Stripe’s hosted or embedded checkout or a Shopify checkout, the WebMCP tools come from your provider and tell agents to get the buyer’s confirmation, for agents in browsers that support WebMCP. A custom form has to be read and clicked like any other page.
We looked at the design of that confirmation step, and where it falls short, in the approval gate in agentic browsers.
Path 4: signed mandates and agent tokens
The fourth path is the one people imagine when they hear “agents that pay”: the person is not watching when the charge happens. It exists, but only inside limits a person approved earlier, and it shows up at your business mostly through your processor and the card networks.
AP2 mandates. Google published the Agent Payments Protocol in September 2025 and contributed it to the FIDO Alliance on April 28, 2026.3 Version 0.2 describes two signed records: a Checkout Mandate for the order, which the merchant verifies, and a Payment Mandate for the payment, which goes to the credential provider, the networks and the processor. In the direct, human-present mode, the person signs off on the final checkout and its payment on a trusted surface. In the autonomous mode, “the User sees and approves a set of constraints,” and the final mandates are signed by an agent key.21
Card network programs. Visa’s Trusted Agent Protocol, developed with Cloudflare and introduced in October 2025, is aimed at your side of the counter: it helps merchants tell trusted shopping agents from malicious bots and receive details such as whether the consumer already has an account, with minimal changes to the checkout.22 Mastercard’s Agent Pay, announced in April 2025, issues Agentic Tokens to registered and verified agents and makes agent-facilitated transactions recognizable across the value chain.2
Business invoices. The same pattern has reached B2B payments. On October 20, Visa, BILL and Billtrust launched a live pilot in which BILL’s payment agent, registered through Visa’s Trusted Agent Protocol, pays supplier invoices through supplier portals with tokenized card credentials instead of shared portal logins. Visa’s FAQ answers the authorization question directly: the agent “only executes eligible payments that have already been approved by the buyer.”23 For a seller with an invoice portal, the approval happened in the buyer’s payables workflow before the agent arrived.
Wallets with limits. Stripe’s Link agent wallet lets a person approve each purchase or set a budget for the agent to work within,24 and raising an approved amount “requires the customer to approve again.”25 We looked at what that approval does and does not cover in Stripe’s Link agent wallet.
What this means for you: on this path the authorization is real but happened upstream, in a mandate, a token or a wallet setting. Apart from an AP2 Checkout Mandate, which the merchant verifies, your processor and the networks do the checking, not you. Do not assume agent orders arrive labeled: on September 30 Mastercard began rolling out, for testing in the US, a score that tells issuers how likely it is that an AI agent started a transaction.26
If an agent order goes wrong: who pays
Card networks have now written agents into their rules, and the familiar dispute process still applies. Visa’s rules cover purchases that a registered agent platform completes from a cardholder’s instructions, and they make the cardholder responsible for the platform’s actions as if they had made the purchase themselves. The platform must pass you the cardholder’s name and email, plus addresses for shipped goods, and keep an order confirmation with your contact details and refund policy available to the cardholder for at least 120 days.27 Mastercard’s merchant guide says standard chargeback rights and dispute processes apply to agentic transactions.28 Visa chief executive Ryan McInerney told analysts on October 27 that “our rules clarify the roles and responsibilities and processes should something go wrong.”29
That does not make agent orders dispute-proof. A buyer who dislikes what the agent chose can still claim the order was not what they agreed to, which Goodwin partner Ximeng (Sammy) Tang calls “buyer’s remorse dressed up as a Regulation Z dispute.”30 When the issuer credits the buyer in such a dispute, the loss usually lands on the merchant. Visa’s rules cover Visa card payments that a registered agent platform makes for the person, which can happen in an assistant’s checkout or under a mandate (Paths 2 and 4). When the person pays on your own checkout link (Path 1), the purchase is an ordinary card payment; for a browser agent on your checkout page (Path 3), Google tells auto browse users they are responsible for its actions, including unexpected purchases.15 Either way, the defense is the one you already know: terms the agent can read back to the person, and records of what was agreed.
Services: the agent prepares the booking, the person pays
For a consultancy, an agency, a clinic or a training company, “the order” is usually a time slot: a paid consultation, a deposit that holds a session, a first month of a retainer. The authorization question gets sharper here, because the person is committing their own time and accepting cancellation terms, not just buying a box.
The pattern that works splits the job cleanly. The agent prepares; the person authorizes and pays.
Tobira’s guest contract is a concrete example of how that split can be written down for visiting assistants. Besides answering questions (ask_question), its action API supports five actions: list_consultations, list_available_slots, prepare_booking, submit_authorized_contact and check_booking_status. The two that send contact details or prepare a booking need the person’s explicit go-ahead, and prepare_booking is accepted only when authorized_by_user is true and the request carries an idempotency key that stays the same across retries, so a retry can be recognized rather than booked twice. For a paid booking, the next state is payment_pending, and the person gets the checkout link.7
So a visiting assistant can do almost all the work, from the first question to a held slot. What it never does is complete the payment. That is deliberate. Consent to terms: a paid session usually comes with a cancellation and refund rule (Tobira’s own 60-minute consultation, for instance, can be cancelled for a full refund up to 24 hours before the session), and the person, not their assistant, should see and accept it. Visa’s rules ask something similar of the agent platforms that do pay: before paying a merchant with a limited cancellation or refund policy, the platform must get the cardholder’s consent or acknowledgement, at checkout or when the person sets the agent’s instructions, including the date an advance payment stops being refundable.27 Disputes: a payment the cardholder made on a checkout page is a far cleaner record than one an assistant pushed through. Liability: if the agent misquotes a price or a term, the business answers for it, as we covered in chatbot liability; a human checkout step is where the final terms are fixed.
Standards are starting to cover this case too. A UCP charter for local services, opened on October 9, 2026 and approved by the protocol’s Governing Council on November 4, puts appointments and group sessions paid in full at booking in its first phase; deposits, cards held as a guarantee, no-show handling, reservations and rentals wait for a second.31 The group that will write it is still being formed, so the prepare-then-pay handoff remains the practical default. For the wider picture of selling services to agents, see agentic commerce for services; for two assistants negotiating a meeting time between themselves, see when AI assistants schedule meetings with each other.
What to set up on your site
Whatever path your buyers’ assistants take, the same short list keeps the approval step clean and the money on your side.
- Put prices and terms in plain text. The person approves what their assistant reads back to them. Plan, price, currency, taxes, renewal and cancellation rules should sit on the page as text, not in an image, a PDF or a “contact us” box.
- Write down your agent’s payment rule. If you run a site agent, state what it may do with money: answer, prepare, hold a slot, send a checkout link. Require the person’s explicit go-ahead before contact details are sent or a booking is prepared, and make bookings idempotent so a retry does not create a second one.
- Use a checkout the person recognizes. A hosted card checkout or a payment link keeps approval explicit and leaves a clean record. On Stripe’s hosted checkout or a Shopify checkout, browser agents also get tools that tell them to get the buyer’s confirmation.
- Ask your payments provider five questions. Are agent-initiated transactions flagged to me? What evidence of the person’s consent arrives with them? How are disputes on them handled? How do my 3D Secure rules treat agent orders? (Mastercard tells merchants not to block an identified agentic transaction on a 3D Secure failure alone.)28 Can I accept AP2 mandates or network agent tokens, and do I need to?
- Choose your assistant channels on purpose. If you sell physical goods, check which AI carts can sell your products today, whether they are on by default, and which order and customer data reach you. Read their refund and dispute terms like a marketplace contract.
- Keep the outcome with its source. When an order or booking arrives, you should know it came through an assistant, which one, and what was agreed. Keep those terms next to the payment, with the order and account details an agent platform passes you: Visa’s dispute rules now count a cardholder’s login at an agent platform among the evidence in some card-absent fraud disputes.27
- Do not promise what the rails do not do. Saying “AI agents can buy from us automatically” invites questions your checkout cannot answer. Say what is true: an assistant can get the order ready, and the person confirms and pays.
Before you touch payments, the agentic website checklist shows where your site stands, and what is an agentic website explains why the transaction layer is the one that turns a visit into revenue.
What to remember
- A person still approves the payment on almost every path. What changes is where (your checkout, the assistant’s cart, the browser, a mandate) and when (at purchase, or in advance as signed limits).
- Your own chat checkout is the path you control. The agent prepares, the person pays on a checkout link, and you keep a normal card record.
- Agent card payments still follow card rules. Visa’s rules make the cardholder answer for a registered agent platform’s purchases, and disputes reach you through the usual process.
- For services, the agent prepares the booking and the person pays.
We don’t know which of these four paths will carry most agent orders a year from now: AP2 is at version 0.2, WebMCP is a draft and the UCP charter for local services was approved only this week, with nobody yet named to write it. On all four, today, the charge traces back to a person who said yes.
FAQ
Can AI agents make purchases on my website?
They can start and prepare them, and in a few setups complete them within limits a person approved in advance. In 2026 the person usually approves the payment itself: in your checkout, in the assistant’s cart, in a browser confirmation or through a signed mandate.
Who is the merchant of record when an AI assistant sells my product?
You are. Google’s Universal Cart, Copilot Checkout and Perplexity Instant Buy all keep the business as merchant or seller of record. You fulfill the order and handle confirmations and customer support, even though the person approved the payment on the assistant’s screen.
Who pays if an AI agent buys the wrong thing from my site?
If the buyer disputes the charge and wins, usually you do. Disputes on agent card orders reach you, the merchant, through the usual chargeback process, and Mastercard says standard chargeback rights apply to agent transactions. Visa’s rules make the cardholder responsible for a registered agent platform’s purchases as if they made them, but a buyer can still claim an order was not as agreed. Put prices and refund terms in text an agent can read back, and keep the order details the platform sends.
Should my site agent be allowed to pay on a visitor’s behalf?
No. A site agent works for your business, not for the buyer, so it should prepare the order and hand the person a checkout link. Tobira’s guest contract, for example, marks payment as a human action: the agent returns the checkout link and the person pays.
Do browser agents like Chrome auto browse complete payments on their own?
Not by design. Google says auto browse pauses to ask for confirmation, or hands the step back, before tasks such as purchases, and Gemini Spark hands payments back to the user. Google’s help page still lists a purchase made without the user’s permission among the mistakes auto browse can make. Stripe’s and Shopify’s WebMCP checkout tools tell agents to get the buyer’s confirmation before submitting payment.
What should I ask my payment provider about agent payments?
Ask whether agent-initiated transactions are flagged to you, what evidence of the person’s consent comes with them, how disputes on them are handled, and whether you need to accept AP2 mandates or card network agent tokens. Vague answers mean you should treat agent orders like any other card-not-present order, which is how the card networks treat them too.
Sources
Footnotes
-
Tobira Site Agent product page, read on tobira.ai/agentic-site/ on November 4, 2026: feature card “Books demos and takes payment. A calendar and checkout right in the chat.”; the section on visiting AI agents, which ask their questions and move on to a demo, an order or a trial, with illustrative rows such as an order paid via Gemini; the comparison with a typical AI chatbot (booking and payment inside the chat; taking an AI agent’s order or sending a trial link); payments for consultations and services listed on the Business and Premium plans. Names, companies and amounts in the page’s demos are illustrative. Tobira publishes this blog. https://tobira.ai/agentic-site/ ↩ ↩2
-
Mastercard, “Mastercard Unveils Agent Pay, Pioneering Agentic Payments Technology to Power Commerce in the Age of AI,” April 29, 2025: Mastercard Agentic Tokens; trusted AI agents registered and verified; agent-facilitated transactions recognizable across the value chain; consumers to have “complete control over what the agent is allowed to purchase on their behalf”; strong consumer authentication using on-device biometrics. https://www.mastercard.com/news/press/2025/april/mastercard-unveils-agent-pay-pioneering-agentic-payments-technology-to-power-commerce-in-the-age-of-ai/ ↩ ↩2
-
FIDO Alliance, “FIDO Alliance to Develop Standards for Trusted AI Agent Interactions,” April 28, 2026: Google contributed AP2 and Mastercard its Verifiable Intent framework, co-developed with Google and designed to work with AP2, for development in FIDO’s Payments Technical Working Group; Pablo Fourez, Chief Digital Officer, Mastercard: “user intent must be explicit, verifiable and trusted.” https://fidoalliance.org/fido-alliance-to-develop-standards-for-trusted-ai-agent-interactions/ ↩ ↩2
-
Shopify Developers changelog, “Add shopping and Shop Pay checkout to any agent with Shop MCP,” October 13, 2026: with a signed-in shopper, the agent completes the purchase after the shopper confirms the total and payment method. https://shopify.dev/changelog/posts/add-shopping-and-shop-pay-checkout-to-any-agent-with-shop-mcp ↩
-
G2, 2026 Buyer Behavior Report, July 22, 2026: more than 1,000 B2B software buyers and decision-makers; 47% would let agents research and recommend while people keep all final decision-making authority; 9% are comfortable letting agents execute purchases within approved guardrails; 2% would let agents make purchases without pre-approval. https://company.g2.com/news/buyer-behavior-2026 ↩
-
Lily Varon, Forrester, “Consumers Aren’t Ready To Delegate Payments To AI Agents,” June 15, 2026: April 2026 survey of online adults in the US, UK and Canada; three-quarters uncomfortable allowing an AI agent to complete a purchase and pay autonomously, even with spending limits and rules set in advance; their comfort “stops short of letting the agent actually complete a payment.” https://www.forrester.com/blogs/consumers-arent-ready-to-delegate-payments-to-ai-agents/ ↩
-
Tobira guest agent contract for @tobira-ai, schema
2026-05-27.stage1, read November 4, 2026:action_api.authorization.payment(a returned checkout URL is a handoff to the person; “an AI visitor never completes payment”);booking_contractstateslead_captured,booking_prepared,payment_pendingandbooking_confirmed, withrequires_user_payment: trueandpayment_is_human_action: true;ask_questionplus five supported actions in the action API; the person’s explicit authorization required before contact details are submitted or a booking is prepared;prepare_bookingrequiresauthorized_by_userand an idempotency key that stays stable across retries; a 60-minute consultation with free cancellation and a full refund up to 24 hours before the session. https://tobira.ai/api/v1/agents/tobira-ai/guest-agent.json ↩ ↩2 -
Google, “Google’s new Universal Cart launches today in the U.S.,” October 15, 2026: a cart across retailers in Search and the Gemini app with checkout on UCP; pay with Google Pay in the cart or transfer to the merchant’s own cart; the merchant remains seller of record and handles confirmations and customer support. https://blog.google/products-and-platforms/products/shopping/universal-cart-launch/ ↩ ↩2
-
Microsoft Advertising, “Conversations that Convert: Copilot Checkout and Brand Agents,” January 8, 2026: Copilot Checkout in the US with PayPal, Shopify and Stripe; the merchant stays merchant of record. https://about.ads.microsoft.com/en/blog/post/january-2026/conversations-that-convert-copilot-checkout-and-brand-agents ↩ ↩2
-
PayPal, “PayPal and Perplexity Launch Instant Buy Ahead of Black Friday,” November 25, 2025: checkout in the chat with PayPal; the retailer remains merchant of record. https://newsroom.paypal-corp.com/2025-11-PayPal-and-Perplexity-Launch-Instant-Buy ↩
-
OpenAI, “Powering product discovery in ChatGPT,” March 24, 2026: merchants can use their own checkout experiences while ChatGPT focuses on product discovery. https://openai.com/index/powering-product-discovery-in-chatgpt/ ; launch: OpenAI, “Buy it in ChatGPT,” September 29, 2025, https://openai.com/index/buy-it-in-chatgpt/ ↩
-
OpenAI Developers, checkout and monetization guide, read November 4, 2026: external checkout on the developer’s own domain is the recommended and generally available approach; current approval is limited to plugins for physical goods purchases; checkout with the ChatGPT payment sheet is a private beta for select marketplaces. https://developers.openai.com/plugins/build/monetization ↩ ↩2
-
Agentic Commerce Protocol repository, read November 4, 2026: latest stable version 2026-04-17, with the specification labeled beta; payment providers process transactions by passing “secure payment tokens between buyers and businesses through AI agents”; the delegated payment specification describes a vault token limited by an allowance (one-time use, maximum amount, one checkout session, expiry). https://github.com/agentic-commerce-protocol/agentic-commerce-protocol ↩
-
Shopify Help Center, “Agentic storefronts” and “Managing agentic storefronts,” read November 4, 2026: agentic storefronts are active by default for eligible stores; with the default “Allow Shopify to manage for me” setting, direct checkout is activated for the relevant channels (Google AI Mode and Gemini, Microsoft Copilot, Meta surfaces), and the merchant can deactivate it. https://help.shopify.com/en/manual/online-sales-channels/agentic-storefronts ; https://help.shopify.com/en/manual/online-sales-channels/agentic-storefronts/agentic-home ↩
-
Google, “Chrome gets new Gemini 3 features, including auto browse,” January 28, 2026: auto browse, launched in preview for US AI Pro and Ultra subscribers, is designed to pause and ask for confirmation, or have the user complete tasks such as making a purchase. https://blog.google/products-and-platforms/products/chrome/gemini-3-auto-browse/ ; Android in the US: Google, “Tap into the power of Gemini in Chrome on Android,” August 18, 2026, https://blog.google/products-and-platforms/products/chrome/gemini-in-chrome-android-auto-browse/ ; India: Google India, October 7, 2026, https://blog.google/intl/en-in/products/bringing-gemini-in-chrome-with-auto-browse-to-india/ ; Gemini Apps Help, read November 4, 2026: an experimental feature that may ask the user to take over to finalize financial transactions; the user is responsible for Gemini’s actions during a task, including mistakes and unexpected purchases, and completing a purchase without permission is listed among its possible mistakes. https://support.google.com/gemini/answer/16821166 ↩ ↩2
-
Google, “Gemini Spark: new Chrome browsing integration,” July 30, 2026: Spark keeps the user in the loop on sensitive actions such as payments by handing the task back. https://blog.google/innovation-and-ai/products/gemini-app/gemini-spark-updates-july-2026/ ↩
-
OpenAI, ChatGPT Learn, “Site tools,” read November 4, 2026: normal website-access and confirmation policies still apply to consequential actions such as making purchases. https://learn.chatgpt.com/docs/webmcp ↩
-
Stripe Docs, “Use WebMCP to complete Stripe payments in a browser,” read November 4, 2026: supported UIs (full page and embedded Checkout, Elements, hosted invoice page); tools to read checkout context, select a payment method, fill form fields and start payment submission where Stripe controls the submit action; payment submission tools carry WebMCP’s
consequentialHint, and agents are told to get the user’s confirmation before calling them: “Don’t interpret the hint itself as confirmation.”; labeled an experimental capability. https://docs.stripe.com/agentic-commerce/agents/webmcp ↩ -
W3C Web Machine Learning Community Group, WebMCP Draft Community Group Report, dated November 2, 2026; not a W3C Standard and not on the W3C Standards Track. https://webmachinelearning.github.io/webmcp/ ↩
-
Shopify Developers changelog, “WebMCP support for checkout,” September 28, 2026: browser agents can read and update checkouts and submit checkout after buyer confirmation; control returns to the buyer for 3D Secure authentication or blocking UI extensions; no new API and no merchant configuration. https://shopify.dev/changelog/webmcp-support-for-checkout ; Shopify Dev Docs, “Checkout WebMCP,” read November 4, 2026: show the buyer the current order and total and get their permission before completing checkout; “If the total changes, then ask again.” https://shopify.dev/docs/agents/carts-and-checkout/checkout-webmcp ↩
-
Agent Payments Protocol specification, v0.2, read November 4, 2026: Checkout Mandate and Payment Mandate, each with open and closed stages; Human Present (Direct) mode, where the user approves the closed checkout and its payment on a trusted surface; Human Not Present (Autonomous) mode, where “the User sees and approves a set of constraints” and closed mandates are signed by an agent key; merchant verification of the checkout hash and of conformance to open constraints. No release after v0.2 as of November 4, 2026. https://ap2-protocol.org/ap2/specification/ ; overview: https://ap2-protocol.org/ ↩
-
Visa, “Visa Introduces Trusted Agent Protocol: An Ecosystem-Led Framework for AI Commerce,” October 14, 2025, developed in collaboration with Cloudflare: helps merchants recognize trusted agents with commerce intent and separate them from malicious bots; approved agents can pass consumer recognition data, such as whether the consumer has an existing account, and optionally payment information; minimal user experience changes on merchant websites or checkout pages. https://usa.visa.com/about-visa/newsroom/press-releases.releaseId.21716.html ↩
-
Visa, “Visa, BILL and Billtrust Launch First Live Pilot for Trusted AI Agent Payments Between Buyer and Supplier Platforms,” October 20, 2026: BILL’s payment agent registered through Visa’s Trusted Agent Protocol; tokenized payment credentials; agents authenticated to credentialed supplier portals; FAQ: the agent does not make payment decisions and “only executes eligible payments that have already been approved by the buyer.” https://usa.visa.com/about-visa/newsroom/press-releases.releaseId.22856.html ↩
-
Link, agents page, read November 4, 2026: approve the amount of each purchase, or approve a budget and let the agent handle the rest, with a maximum per purchase. https://link.com/agents ↩
-
Stripe Docs, Link agent wallet, “Enable agents to spend,” read November 4, 2026: the agent creates a spend request and the customer approves it; recurring cards carry a per-period limit; “requires the customer to approve again” when the amount is raised. https://docs.stripe.com/agentic-commerce/agents/link-agent-wallet/use-link-wallet-pay-online#increase-the-amount ↩
-
Mastercard, “Mastercard Advances Agentic Commerce With New Trust and Intelligence Services,” September 30, 2026: a probability score indicating the likelihood that a transaction was initiated by an AI agent, rolling out for testing in the US, to help issuers approve legitimate agent-led purchases. https://investor.mastercard.com/investor-news/investor-news-details/2026/Mastercard-Advances-Agentic-Commerce-With-New-Trust-and-Intelligence-Services/default.aspx ↩
-
Visa, “Visa Core Rules and Visa Product and Service Rules,” edition of October 24, 2026, section 4.1.23, Agentic Platform Requirements (last updated April 2026): the agent platform passes the merchant the cardholder’s name, email address, and billing and shipping address if goods are shipped (4.1.23.4); gets the cardholder’s consent or acknowledgement of a merchant’s limited cancellation or refund policy, including the date advance-payment cancellation privileges expire (4.1.23.6); makes an order confirmation with the merchant’s contact details and cancellation and refund policies available for at least 120 days (4.1.23.8); and the cardholder is responsible for the platform’s actions as if the cardholder initiated the transaction (4.1.23.10). Dispute Condition 10.4 compelling evidence includes login IDs for an Agentic Payment Provider. https://usa.visa.com/dam/VCOM/download/about-visa/visa-rules-public.pdf ↩ ↩2 ↩3
-
Mastercard Developers, “Level 1 Agentic Commerce: Enable Agent Support with Minimal Changes,” read November 4, 2026: standard fraud detection, chargeback rights and dispute resolution processes apply to agentic transactions; when a transaction is identified as agentic, skip 3DS initiation or anticipate a non-authenticated response, and do not block it on a 3DS failure alone. https://developer.mastercard.com/merchant-cloud/documentation/tutorials-and-guides/agentic-commerce-guide/21/ ↩ ↩2
-
Visa, fiscal fourth quarter 2026 earnings call, October 27, 2026, remarks by chief executive Ryan McInerney on agentic commerce; transcript published by The Motley Fool, October 28, 2026. https://www.fool.com/earnings/call-transcripts/2026/10/28/visa-v-q4-2026-earnings-call-transcript/ ↩
-
Ximeng (Sammy) Tang, Goodwin, “Authorizing Agentic Payments,” June 11, 2026: merchant exposure on agentic payments includes authorization disputes and buyer’s remorse framed as a billing dispute under Regulation Z, where the issuer must credit the consumer after a reasonable investigation and the loss falls on the merchant in practice. https://www.goodwinlaw.com/en/insights/publications/2026/06/insights-technology-aiml-authorizing-agentic-payments ↩
-
Universal Commerce Protocol GitHub issue #922, “[DTC Charter]: Local Services,” opened October 9, 2026, read November 4, 2026: labeled approved on November 4, 2026, when a maintainer wrote that the Governing Council had reviewed and approved the charter, with nominations for the domain tech council next; phase 1 covers appointments and group sessions paid in full at booking; phase 2 covers deposits, a card held as a guarantee, cancellation and no-show handling, reservations and rentals. https://github.com/Universal-Commerce-Protocol/ucp/issues/922 ↩