# Merchant of record in agentic commerce

When an AI agent buys from your store, who owns the sale? What OpenAI, Google, Microsoft and Perplexity each say, who handles tax, refunds, support and disputes, and what to keep ready.

By Valerii Checha, 16 Nov 2026

A shopper asks an AI assistant for a desk lamp, approves the price, and the order goes through without the shopper ever opening your site. Whose sale was that? Who charges the tax, who takes the return in three weeks, and who answers the email that says the lamp arrived in pieces?

On every platform we read, the store is still the merchant of record, the seller the shopper actually bought from (our gloss). OpenAI writes that it "is not the merchant of record in the Agentic Commerce Protocol". Google tells merchants "You will remain the seller of record", Microsoft writes "With Copilot Checkout, you stay the merchant of record", and Perplexity says retailers "stay at the center of the transaction as the merchant of record". So the tax, the refunds, the support and the fulfilment stay with you on the platforms that write the duties down, and Google's US contract spells them out line by line.

Merchant of record is a legal and tax status, so none of this is legal or tax advice, and the contract you sign is the one that counts. What we can do is quote what each platform has published about it.

## What does merchant of record mean in agentic commerce?

In our words, the merchant of record is the business that sells to the buyer and carries the duties of the sale: charging the payment, collecting the tax, honouring returns and answering complaints. The [glossary](https://storewalk.ai/blog/agentic-commerce-glossary#merchant-of-record) has the term with UCP's own wording.

It matters in agentic commerce because the platform can look like the shop. The checkout appears inside ChatGPT, Gemini or Copilot, the shopper pays with a wallet the platform knows, and the store may never see the session. OpenAI describes the split in one sentence: "The checkout session is rendered in the OpenAI UI, but the actual checkout state and payment processing occurs on the merchant's systems."

The protocols were written that way on purpose. The ACP README promises agent platforms that they can let users "transact directly with businesses in your application, without being the merchant of record." UCP's checkout capability says "The business remains the Merchant of Record (MoR), and they don't need to become PCI DSS compliant to accept card payments through this Capability." The protocols themselves are explained in [ACP explained](https://storewalk.ai/blog/acp-explained) and [UCP explained](https://storewalk.ai/blog/ucp-explained).

## What does each AI platform say about who sells?

Pick a platform. Each line is quoted from the platform, and "after the order" says where its pages go quiet:

Who sells when an agent buys: each platform in its own words.

ChatGPT and ACP (OpenAI, Stripe). Who is the seller: “OpenAI is not the merchant of record in the Agentic Commerce Protocol.” The ACP README promises agent platforms they can let users buy from businesses “without being the merchant of record.” Who takes the payment: “Merchants are expected to bring their own PSP and handle payments just as they do for accepting any other digital payment.” The checkout is “rendered in the OpenAI UI, but the actual checkout state and payment processing occurs on the merchant’s systems.” After the order: The merchant sends order events back: “Merchants POST order events so ChatGPT can stay in sync with fulfillment-grade truth”, with refunds, returns and disputes as order adjustments.

Sources: [OpenAI: Agentic Commerce key concepts](https://developers.openai.com/commerce/guides/key-concepts), [GitHub: Agentic Commerce Protocol README](https://github.com/agentic-commerce-protocol/agentic-commerce-protocol) and [ACP: checkout webhooks, 2026-04-17](https://github.com/agentic-commerce-protocol/agentic-commerce-protocol/blob/main/spec/2026-04-17/openapi/openapi.agentic_checkout_webhook.yaml).

Google: UCP checkout and Universal Cart (AI Mode, Gemini). Who is the seller: “You will remain the seller of record”, and with checkout on Google’s surfaces “keeping you the merchant of record.” Google’s US Checkout Addendum: “Merchant is the merchant of record for all items sold through the Program”. Who takes the payment: Shoppers pay with Google Pay; the addendum lists “(b) processing payments in connection with User’s order” among the merchant’s duties. The UCP spec: the business does not “need to become PCI DSS compliant to accept card payments through this Capability.” After the order: The addendum also lists “(c) handling all customer or product-related issues and communications with a User”. Universal Cart: “you will receive direct confirmations and customer support from the merchant”.

Sources: [Google Merchant Center Help: UCP-powered checkout](https://support.google.com/merchants/answer/16837055?hl=en), [Google: Checkout Addendum to the Merchant Center Terms of Service (US)](https://merchants.google.com/files/tos/ucp_integration/US/1_00_tos.html) and [UCP: Checkout capability](https://ucp.dev/latest/specification/shopping/checkout/).

Microsoft Copilot Checkout (PayPal, Stripe, Shopify). Who is the seller: “With Copilot Checkout, you stay the merchant of record.” Who takes the payment: “For merchants who want to onboard using PayPal or Stripe : We’re now accepting applications.” “If you’re on Shopify, you’ll automatically be able to sell in Copilot Checkout”, after “an opt-out window”. After the order: The post does not describe refunds, returns or support after the order.

Source: [Microsoft Advertising: Copilot Checkout and Brand Agents (8 Jan 2026)](https://about.ads.microsoft.com/en/blog/post/january-2026/conversations-that-convert-copilot-checkout-and-brand-agents).

Perplexity with PayPal (US users). Who is the seller: “Through our partnership with PayPal, retailers stay at the center of the transaction as the merchant of record.” Who takes the payment: PayPal powers the checkout inside Perplexity, by Perplexity’s own description. After the order: The post does not describe refunds, returns or support after the order.

Source: [Perplexity: Shopping that puts you first (25 Nov 2025)](https://www.perplexity.ai/hub/blog/shopping-that-puts-you-first).

Every platform we read says the store stays the seller. That is where they agree; the detail of who does what after the order is written down in very different amounts.

The agreement is complete on the headline and patchy on the detail. OpenAI and Google document the after-sale side in specifications and contracts. Microsoft's and Perplexity's announcements state the seller and stop there, which is fine for a launch post and less helpful for a finance team. For Google, the same answer covers Universal Cart: Google writes that whichever way the shopper checks out, "you will receive direct confirmations and customer support from the merchant, and they will remain the seller of record."

## Who handles tax, refunds and disputes for an agent's order?

Choose a duty to see what each platform's pages say about it, and where they say nothing:

Tax, refunds, support and disputes: what each platform’s pages say.

Sales tax:

- ChatGPT and ACP: The merchant “calculates and charges sales tax”.
- Google: “(e) calculating and remitting all applicable taxes related to an order.”
- Copilot Checkout: Not stated on the pages we read.
- Perplexity: Not stated on the pages we read.

Our reading: Tax stays with you on the two platforms that write it down. Ask your tax adviser about the rest.

Sources: [OpenAI: Agentic Commerce key concepts](https://developers.openai.com/commerce/guides/key-concepts) and [Google: Checkout Addendum to the Merchant Center Terms of Service (US)](https://merchants.google.com/files/tos/ucp_integration/US/1_00_tos.html).

Refunds and returns:

- ChatGPT and ACP: Refunds go back to ChatGPT as order adjustments; the delegate payment RFC lists “refund semantics” as out of scope.
- Google: Return policies in Merchant Center are “a Merchant of Record requirement and will be referenced on the checkout screen”, with “return cost, return speed (window), and a link to the full policy.”
- Copilot Checkout: Not stated on the pages we read.
- Perplexity: Not stated on the pages we read.

Our reading: Your returns policy is the one that applies. Google shows it at checkout, so it has to be right in Merchant Center as well as on your site.

Sources: [ACP: checkout webhooks, 2026-04-17](https://github.com/agentic-commerce-protocol/agentic-commerce-protocol/blob/main/spec/2026-04-17/openapi/openapi.agentic_checkout_webhook.yaml), [ACP: delegate payment RFC](https://github.com/agentic-commerce-protocol/agentic-commerce-protocol/blob/main/rfcs/rfc.delegate_payment.md) and [Google for Developers: Prepare your Merchant Center account](https://developers.google.com/merchant/ucp/guides/overview/merchant-center).

Customer support:

- ChatGPT and ACP: Not stated on the pages we read.
- Google: Support details in Merchant Center are “used to generate the “Contact Merchant” link on the order confirmation page.” The addendum: “(c) handling all customer or product-related issues and communications with a User”.
- Copilot Checkout: Not stated on the pages we read.
- Perplexity: Not stated on the pages we read.

Our reading: The shopper who bought inside an assistant contacts you, not the assistant. Make sure they can find you.

Sources: [Google for Developers: Prepare your Merchant Center account](https://developers.google.com/merchant/ucp/guides/overview/merchant-center) and [Google: Checkout Addendum to the Merchant Center Terms of Service (US)](https://merchants.google.com/files/tos/ucp_integration/US/1_00_tos.html).

Payment and fraud checks:

- ChatGPT and ACP: The merchant “analyzes payment and risk signals on their own stack, and charges the payment method with their existing payment processor.”
- Google: “(b) processing payments in connection with User’s order”; Payments Data may be used to “process payments, provide customer support, and perform fraud detection services”.
- Copilot Checkout: Onboarding through PayPal or Stripe, or automatically through Shopify.
- Perplexity: Checkout powered by PayPal.

Our reading: Your payment provider still processes the payment, so it has to accept the agent platform’s token or wallet.

Sources: [OpenAI: Agentic Commerce key concepts](https://developers.openai.com/commerce/guides/key-concepts), [Google: Checkout Addendum to the Merchant Center Terms of Service (US)](https://merchants.google.com/files/tos/ucp_integration/US/1_00_tos.html), [Microsoft Advertising: Copilot Checkout and Brand Agents (8 Jan 2026)](https://about.ads.microsoft.com/en/blog/post/january-2026/conversations-that-convert-copilot-checkout-and-brand-agents) and [Perplexity: Shopping that puts you first (25 Nov 2025)](https://www.perplexity.ai/hub/blog/shopping-that-puts-you-first).

Fulfilment and shipping:

- ChatGPT and ACP: The merchant “determines fulfillment options”.
- Google: “(d) fulfilling, shipping, and handling orders”.
- Copilot Checkout: Not stated on the pages we read.
- Perplexity: Not stated on the pages we read.

Our reading: Nothing changes in your warehouse. The order arrives by another door.

Sources: [OpenAI: Agentic Commerce key concepts](https://developers.openai.com/commerce/guides/key-concepts) and [Google: Checkout Addendum to the Merchant Center Terms of Service (US)](https://merchants.google.com/files/tos/ucp_integration/US/1_00_tos.html).

Disputes and chargebacks:

- ChatGPT and ACP: ACP order adjustments can record “disputes”; the pages we read assign no other duty.
- Google: UCP order adjustments can record “disputes”; the addendum puts “all aspects of the transaction” on the merchant without naming chargebacks.
- Copilot Checkout: Not stated on the pages we read.
- Perplexity: Not stated on the pages we read.

Our reading: No platform page we read explains chargebacks for agent orders. Your card provider’s rules are the ones to read.

Sources: [ACP: checkout webhooks, 2026-04-17](https://github.com/agentic-commerce-protocol/agentic-commerce-protocol/blob/main/spec/2026-04-17/openapi/openapi.agentic_checkout_webhook.yaml), [UCP: Order capability](https://ucp.dev/latest/specification/shopping/order/) and [Google: Checkout Addendum to the Merchant Center Terms of Service (US)](https://merchants.google.com/files/tos/ucp_integration/US/1_00_tos.html).

Tax and fulfilment are written down clearly where they are written down at all, and both stay with the store. Disputes and chargebacks are the gap: ACP and UCP both let an order record a dispute as an adjustment, but none of the pages we read says how a chargeback on an agent's order is decided. That is between you, your payment provider and the card network, and the card networks' own programmes are compared in [Visa Intelligent Commerce vs Mastercard Agent Pay](https://storewalk.ai/blog/visa-intelligent-commerce-vs-mastercard-agent-pay).

Refunds have a small twist for ACP. Its delegate payment RFC lists "refund semantics" as out of scope, so the refund itself runs through your payment provider as usual. What ACP adds is reporting: "Merchants POST order events so ChatGPT can stay in sync with fulfillment-grade truth", and in the 2026-04-17 spec a refund is an entry in the order's `adjustments`.

## What does Google's Checkout Addendum say?

Google's UCP checkout in the US comes with a contract, the Checkout Addendum to the Merchant Center Terms of Service. Google's help page says it "applies to the United States only." It is the most specific statement of a merchant's duties we found on any platform:

> Merchant is solely responsible for all aspects of the transaction between the Merchant and the User, including: (a) providing Google with item information, including price and availability and any legally required notices and disclaimers; (b) processing payments in connection with User's order; (c) handling all customer or product-related issues and communications with a User; (d) fulfilling, shipping, and handling orders; and (e) calculating and remitting all applicable taxes related to an order.

It also says "Merchant is the merchant of record for all items sold through the Program, including, if applicable, items sold by Third-Party Sellers", which matters to a marketplace that hosts other sellers. And it limits what you may do with the payment data Google passes you: only "process payments, provide customer support, and perform fraud detection services". Staying the seller, then, comes with a fence around that data. We quote the addendum here; we do not interpret it, and anyone signing it should read all of it.

Google's developer pages add the practical side. Return policies in Merchant Center are "a Merchant of Record requirement and will be referenced on the checkout screen", and "You must include return cost, return speed (window), and a link to the full policy." Your support details are "used to generate the "Contact Merchant" link on the order confirmation page." Google, in other words, will show your returns policy to the shopper for you, so it had better match what you do.

## Does staying the seller mean keeping the customer?

Partly, and the platforms put it differently. Google's developer page says "You remain the Merchant of Record. Keep all of your customer data and relationships", and "You retain full ownership of your customer relationships, data, and the post-purchase experience." The addendum's limit on payment data sits beside that. OpenAI's key concepts page describes what the merchant does and does not discuss who owns the relationship afterwards.

Our summary: the seller side is the same on every platform, and only OpenAI and Google write the duties down, while the benefit side varies. Where the duties are written down, they stay with you. How much of the customer you keep depends on the platform and its terms, which is a good reason to read them before your first agent order turns up, rather than after the first refund request.

## What does a store need ready to stay merchant of record?

Most of it is what a store already needs for its own checkout, made findable for a shopper who never saw your site. Tick off what you have; the ticks stay in your browser:

Staying the seller: what to keep ready, ticked off in this browser.

On the page, each item has a tick box; ticks stay in your browser only.

- Your return policy states its window and cost, on your site and in Merchant Center. Google needs “return cost, return speed (window), and a link to the full policy”. Our EVAL-002 checks your site’s version. Sources: [Google for Developers: Prepare your Merchant Center account](https://developers.google.com/merchant/ucp/guides/overview/merchant-center) and [Storewalk: EVAL-002, return policy machine-readable](https://storewalk.ai/checks/EVAL-002).
- A shopper can reach you by email, phone or a contact page, not only a chat bubble. Google builds its “Contact Merchant” link from your Merchant Center details. Our POST-003 checks your site. Sources: [Google for Developers: Prepare your Merchant Center account](https://developers.google.com/merchant/ucp/guides/overview/merchant-center) and [Storewalk: POST-003, support contact structured](https://storewalk.ai/checks/POST-003).
- Your payment provider accepts the agent platform’s payment token or wallet. OpenAI expects merchants to “bring their own PSP”. Our TRX-003 checks what your provider documents. Sources: [OpenAI: Agentic Commerce key concepts](https://developers.openai.com/commerce/guides/key-concepts) and [Storewalk: TRX-003, PSP supports agent payment tokens](https://storewalk.ai/checks/TRX-003).
- Tax is calculated on your side for orders that arrive through an agent. Both OpenAI’s docs and Google’s addendum put tax with the merchant. Sources: [OpenAI: Agentic Commerce key concepts](https://developers.openai.com/commerce/guides/key-concepts) and [Google: Checkout Addendum to the Merchant Center Terms of Service (US)](https://merchants.google.com/files/tos/ucp_integration/US/1_00_tos.html).
- Refunds and returns are sent back to the platform, where it asks for them. ACP: “Merchants POST order events so ChatGPT can stay in sync”, with refunds as adjustments. Source: [ACP: checkout webhooks, 2026-04-17](https://github.com/agentic-commerce-protocol/agentic-commerce-protocol/blob/main/spec/2026-04-17/openapi/openapi.agentic_checkout_webhook.yaml).
- Your purchase terms, privacy, return and refund policies apply to agent orders too. Google’s addendum defines “Merchant Purchase Terms” as including “any applicable privacy, return, and refund policies”. Source: [Google: Checkout Addendum to the Merchant Center Terms of Service (US)](https://merchants.google.com/files/tos/ucp_integration/US/1_00_tos.html).
- Someone qualified has read the platform’s merchant terms before you sign. Google’s US Checkout Addendum is a contract. This article quotes it; it does not interpret it. Source: [Google: Checkout Addendum to the Merchant Center Terms of Service (US)](https://merchants.google.com/files/tos/ucp_integration/US/1_00_tos.html).

Our scan covers the parts that live on your site. [EVAL-002](https://storewalk.ai/checks/EVAL-002) checks that your return policy states a window an agent can read, [POST-003](https://storewalk.ai/checks/POST-003) that a shopper can reach a human by something other than a chat widget, and [TRX-003](https://storewalk.ai/checks/TRX-003) that your payment provider documents a way to accept an agent's payment token. It does not read Merchant Center, your contracts or your tax set-up. The [shipping and returns guide](https://storewalk.ai/guides/shipping-returns-policies-for-agents) covers how to write the policies so an agent can read them. Once they are written, [scan your store](https://storewalk.ai/) to check that an agent can find them, which is a gentler test than a customer's first complaint.

## Frequently asked questions

### Is OpenAI the merchant of record for ChatGPT purchases?

No. OpenAI's commerce docs say "OpenAI is not the merchant of record in the Agentic Commerce Protocol", and that merchants "bring their own PSP and handle payments" as for any other order.

### Is Google the seller when a shopper buys in AI Mode or Gemini?

No. Google's help page says "You will remain the seller of record", and its US Checkout Addendum says the merchant "is the merchant of record for all items sold through the Program".

### Who pays sales tax on an AI agent's order?

On the platforms that write it down, the store. OpenAI's docs say the merchant "calculates and charges sales tax", and Google's addendum lists "calculating and remitting all applicable taxes" among the merchant's duties. Ask a tax adviser how that applies to you.

### Who handles returns and refunds?

The store, through its own policy and its own payment provider. Google shows your Merchant Center return policy at checkout, and ACP asks you to report refunds back to ChatGPT as order adjustments.

### Does Storewalk check merchant of record?

Not as a status, since that is a legal question. Our scan checks what agents need from a seller: a readable return policy, a reachable contact and an agent-ready payment provider. Those are three of [the things that stop agents buying](https://storewalk.ai/blog/why-agents-cant-buy) from a store.

The sources below were last checked on the date shown.

## Sources

- [OpenAI: Agentic Commerce key concepts](https://developers.openai.com/commerce/guides/key-concepts)
- [GitHub: Agentic Commerce Protocol](https://github.com/agentic-commerce-protocol/agentic-commerce-protocol)
- [ACP: checkout webhooks, 2026-04-17](https://github.com/agentic-commerce-protocol/agentic-commerce-protocol/blob/main/spec/2026-04-17/openapi/openapi.agentic_checkout_webhook.yaml)
- [UCP: Checkout capability](https://ucp.dev/latest/specification/shopping/checkout/)
- [UCP: Order capability](https://ucp.dev/latest/specification/shopping/order/)
- [Google Merchant Center Help: UCP-powered checkout](https://support.google.com/merchants/answer/16837055?hl=en)
- [Google for Developers: Prepare your Merchant Center account](https://developers.google.com/merchant/ucp/guides/overview/merchant-center)
- [Google: Checkout Addendum to the Merchant Center Terms of Service (US)](https://merchants.google.com/files/tos/ucp_integration/US/1_00_tos.html)
- [Microsoft Advertising: Copilot Checkout and Brand Agents (8 Jan 2026)](https://about.ads.microsoft.com/en/blog/post/january-2026/conversations-that-convert-copilot-checkout-and-brand-agents)
- [Perplexity: Shopping that puts you first (25 Nov 2025)](https://www.perplexity.ai/hub/blog/shopping-that-puts-you-first)

Last checked 4 Nov 2026
