Merchant of Record in Conversational Commerce: Who Owns the Sale?

A shopper can discover a product through an AI assistant, ask follow-up questions and still buy from the merchant's own store.

The conversational interface does not, by itself, determine who sells the product.

That is why the merchant of record question matters.

What does merchant of record mean?

The merchant of record (MoR) is the party identified as the seller under the relevant commercial and payment arrangements.

Its responsibilities may include collecting payment, issuing receipts, handling refunds and disputes, and meeting applicable tax and consumer obligations.

The precise allocation depends on the contracts, market and checkout architecture.

A payment service provider can process a card payment without becoming the seller.

Likewise, an AI interface can help someone choose a product without becoming the MoR.

Why the distinction matters

An AI-assisted journey has three distinct roles: product guidance, order and checkout, and payment processing.

Conflating them makes it difficult to understand who controls the customer relationship and who is accountable when something goes wrong.

For example, a shopper can receive advice on a merchant's site, continue to its checkout and pay through its existing payment provider.

Adding AI to discovery need not change the merchant's seller-of-record model.

Some platforms also support purchases within a conversational interface, but that does not automatically make the platform the MoR.

The Agentic Commerce Protocol documentation describes a model in which the merchant remains responsible for its order and payment stack.

Each integration still needs to be assessed on its own terms.

Questions to ask before changing the journey

• Who is named as the seller in the order confirmation and customer terms?
• Who receives the order, payment status and customer-service information?
• Who decides the final price, availability, shipping and refund policy?
• Which provider handles card data, and what remains in the merchant's PCI DSS scope?
• Who handles tax, chargebacks, complaints and returns under the applicable contracts?
• Can the merchant continue to understand and serve the customer after the purchase?

These questions are more useful than asking whether the purchase button appears inside a chat.

Data access and customer ownership are contractual and operational questions, not automatic consequences of MoR status.

Where Querytail fits

Product Engine structures and enriches merchant-approved product knowledge so AI shopping experiences can explain products in context.

Brand Agent uses that knowledge to guide shoppers on the merchant's site.

The merchant's own commerce and payment arrangements remain the place to confirm the order and complete payment.

Querytail is not the seller or the payment processor.

For the practical journey from recommendation to purchase, read From prompt to payment.

If your products need more context before a customer can buy with confidence, request a demo and share your store URL.