Merchant of Record in Conversational Commerce: A Complete Guide
Understand the Merchant of Record model and its hidden cost: losing ownership of your customer data. Learn how Querytail's sovereign pass-through approach keeps you in control.
When a customer buys a product through an AI conversation, who is legally responsible for that transaction? This question sits at the heart of conversational commerce, and the answer involves a concept called the Merchant of Record, or MoR.
In traditional e-commerce, the MoR is straightforward. On Amazon, Amazon is the MoR (when you sell through their platform). On Shopify, you are typically the MoR, and Shopify provides the infrastructure. But conversational commerce, where transactions happen through an Agentic Client Advisor, introduces new complexity. And with that complexity comes a risk that most platforms won't tell you about: when someone else becomes the MoR, they become the legal seller, and your customer data, your lifetime value, and your direct relationship go with them.
This guide explains what a Merchant of Record is, why the "Platform as MoR" model is a data trap for merchants, and how Querytail takes a fundamentally different approach: keeping you as the merchant of record while handling the technical complexity through your own PSP.
What is a Merchant of Record?
A Merchant of Record is the entity that is legally and contractually responsible for a transaction. The MoR is the merchant of record, and this role comes with specific obligations.
In practice, the MoR:
- Accepts payment from the customer
- Bears the chargeback risk if the customer disputes the transaction
- Is responsible for collecting and remitting sales tax and VAT
- Must comply with consumer protection regulations in the customer's jurisdiction
- Maintains PCI DSS compliance (Payment Card Industry Data Security Standard) for payment data handling
- Issues refunds when necessary
- Provides customer support for transaction disputes
When you buy something on Amazon, Amazon is the MoR (even if you're buying from a third-party seller). Amazon holds the customer relationship, handles the payment, and bears the liability. The third-party seller ships the product, but Amazon is the one who must comply with consumer protection laws in every jurisdiction where they operate.
On Shopify, the brand is the MoR. Shopify provides payment infrastructure, but you as the brand are responsible for tax collection, compliance, and chargeback liability.
In conversational commerce, the MoR distinction becomes critical because the customer is interacting with an AI system that can facilitate payment. If the Agentic Client Advisor can complete a transaction without redirecting to a separate payment page, someone must be legally accountable for that transaction. The MoR model defines who that is.
Why MoR status matters in conversational commerce
Conversational commerce is different from traditional e-commerce in one key way: the entire purchase journey happens in a single conversation. The customer discusses products, asks questions, decides, and completes payment, all without leaving the chat interface.
This creates a legal and operational challenge. In a typical Shopify or WooCommerce setup, the payment gateway (Stripe, Adyen, etc.) handles the payment, and the brand bears the MoR responsibility. But in conversational commerce, when payment happens inside the AI conversation itself, the liability structure becomes less clear.
Three models can address this:
Model 1: Brand as MoR
You, the brand, assume MoR status. Your Agentic Client Advisor can process payments directly in-chat. You are responsible for all compliance, tax collection, and chargebacks. This model gives you the most control but requires significant compliance infrastructure. You need PCI DSS certification, multi-currency and multi-tax-jurisdiction support, and chargeback management systems.
Model 2: Platform as MoR (the "data trap")
A platform provider (like an AI Commerce Layer) assumes MoR status on your behalf. The platform handles payment processing, tax collection, and compliance. You benefit from reduced operational burden, but there is a critical trade-off that most platforms downplay: the platform becomes the legal merchant of record. This means the customer relationship, the transaction data, and the long-term value belong to the platform, not to you. You become a supplier to the platform's store, not a brand selling directly to your customers.
Model 3: Hybrid model
You and a platform provider share MoR responsibilities. For example, you might be responsible for customer support and refund decisions, while the platform handles payment processing and tax collection. This model balances control and operational overhead, but requires clear contractual agreements about liability boundaries.
Querytail takes a fourth approach: sovereign pass-through. Instead of becoming the MoR (and capturing your customer data in the process), Querytail integrates directly with your existing PSP. You remain the legal seller, you own 100% of the customer data, and your Agentic Client Advisor still completes transactions directly in-chat, with zero redirects. This is the "Bring Your Own PSP" model, and it is the foundation of our commerce infrastructure.
The three MoR models explained
Understanding these models helps you choose the approach that fits your business structure and risk tolerance.
Brand as Merchant of Record
If you choose to be the MoR, you assume direct liability for every transaction. This model makes sense if you want complete control over pricing, payment methods, and customer experience. However, it also means you must:
- Obtain PCI DSS Level 1 certification (the highest compliance standard)
- Implement secure payment processing infrastructure
- Handle tax calculation and remittance for every jurisdiction where you sell
- Manage payment failures, chargebacks, and disputes
- Maintain compliance with consumer protection laws in each region
This approach works well for large brands with dedicated compliance and payments teams. It's less practical for smaller businesses or brands launching conversational commerce for the first time.
When a platform is the MoR, the platform provider becomes the legal seller. You're responsible for fulfilling orders, but the platform owns the transaction, the customer data, and the billing relationship.
Benefits include lower complexity and faster setup. But the drawbacks are structural: the platform captures your customer lifetime value (LTV), controls your pricing flexibility, and can change terms at any time. You lose direct ownership of the data that powers your marketing, your retention strategy, and your future growth. This is the model Amazon uses, and it is the model most AI commerce platforms replicate.
Most AI commerce platforms operate as MoR because it is simpler for them, not because it is better for you.
Hybrid MoR models
Some arrangements split MoR responsibilities. For example, a brand might be the MoR for customer-facing obligations (returns, refunds, support) while a payment processor serves as the MoR for the payment transaction itself.
Hybrid models are common in complex B2B scenarios or when brands integrate multiple specialized platforms. However, they require careful legal documentation to avoid gaps in responsibility.
How Querytail's sovereign approach works: Bring Your Own PSP
Querytail explicitly avoids the MoR "data trap." We believe merchants should own their customer relationships and their data. Instead of acting as a middleman, our infrastructure, powered by our Agentic Commerce Clearing (ACC) layer, acts as a seamless pass-through. ACC is a non-custodial clearing layer that binds every conversion to the agent or channel that generated it, computes commission accruals, emits settlement instructions, and writes signed audit records, all on your own payment rails without ever holding funds. We integrate directly with your existing PSP and anti-fraud tools. This means your Agentic Client Advisor completes transactions directly in-chat, but you remain the legal seller, retaining 100% ownership of the customer data, the checkout experience, and the long-term relationship.
Here is what this means in practice:
When a customer decides to purchase through your Agentic Client Advisor, Querytail orchestrates the payment through your own PSP (Stripe, Adyen, or whichever processor you already use). The customer does not see a separate checkout page. The transaction happens inside the conversation, using the Semantic Firewall to ensure payment data is processed securely and accurately. But the charge appears on your merchant account, not ours.
This approach has several advantages:
You remain the merchant of record. Your company name appears on the customer's bank statement. The customer data flows into your CRM. The lifetime value stays in your business. No platform takes a cut of your relationship.
Conversational continuity. The customer never leaves the chat. They describe what they want, the Agentic Client Advisor recommends products, they ask questions, and they complete the purchase, all in one place. This reduces friction and increases conversion rates.
Your existing tools, amplified. Querytail connects to your PSP, your anti-fraud engine, and your tax compliance software. You do not replace your payment stack. You supercharge it with conversational AI.
Payment method flexibility. Through your PSP's integration, customers can pay with Apple Pay, Google Pay, cards, bank transfers, or other local payment methods, all without leaving chat.
By orchestrating the transaction directly to your PSP, we ensure the customer never leaves the conversation, while your backend receives the data as if they checked out traditionally. For a deeper technical dive into how this sovereign 30-second payment experience works, read our guide on In-Chat Checkout: from prompt to payment.
You maintain full control over pricing, product information, customer data, and service. Querytail provides the AI intelligence and the orchestration layer. The commerce stays yours.
Legal and compliance implications
Understanding MoR responsibility helps you anticipate compliance requirements and operational costs.
Tax and VAT collection
The MoR is responsible for calculating and collecting sales tax (in the United States) or VAT (in Europe and other regions) based on the customer's location.
For domestic sales, this is relatively straightforward. If you sell only in one country or a few states, tax rates are predictable.
Cross-border sales create complexity. If you sell from the United States to the European Union, you must collect VAT at the rate applicable in the customer's country. If you operate as the MoR, you must integrate with tax-compliance software and file VAT returns in multiple jurisdictions.
With Querytail's pass-through model, your existing tax compliance tools handle rate calculation. Querytail's infrastructure passes the customer's location data to your tax engine so the correct rate is applied automatically, just as it would in a traditional checkout flow. You remain the collecting entity.
Consumer protection and refund liability
MoR status makes you responsible for honoring refunds and handling disputes according to local consumer protection laws.
In the EU, consumers have a 14-day right to return goods (with some exceptions). In the US, refund policies vary by state. Because you remain the MoR in Querytail's model, you retain full control over your refund policies. Querytail's Agentic Client Advisor can initiate the refund process conversationally, but the funds flow through your PSP, and the decision stays with your team.
Chargeback liability
When a customer disputes a charge with their credit card company, the chargeback is filed against the MoR. If you're the MoR and lose a chargeback dispute, you lose the revenue and pay a chargeback fee.
This is a significant financial consideration. High chargeback rates can damage your relationship with payment processors and increase processing fees. In Querytail's model, chargebacks are filed against you (as the MoR), but our Agentic Client Advisor helps reduce chargebacks proactively by ensuring product accuracy through the Semantic Firewall and by resolving customer concerns before they escalate. You maintain your direct relationship with your PSP and your chargeback history, which is healthier for your business long-term than hiding behind a platform intermediary.
PCI DSS compliance
PCI DSS is a security standard for handling payment card data. There are four compliance levels, with Level 1 being the most stringent. Most platforms that handle card data directly require at least Level 2 or 3 compliance.
If you're the MoR and accept card payments directly, you must achieve PCI DSS compliance. This involves security audits, encryption protocols, and regular testing. Compliance certification costs thousands of dollars annually.
Because Querytail's pass-through model routes payments directly to your PSP, PCI DSS compliance is handled the same way it would be in any standard e-commerce integration. Your PSP tokenizes the card data. Querytail never touches sensitive payment information. Your systems interact with Querytail through secure APIs, and the compliance obligation stays with your PSP, exactly where it belongs.
How MoR interacts with payment processors
Payment processors like Stripe and Adyen sit between the MoR and the customer's bank. The MoR initiates a payment request, the processor securely transmits it to the bank, and the processor communicates back about success or failure.
The MoR doesn't directly access the customer's card data. Instead, the processor tokenizes the card (converts it into a secure reference) and handles the sensitive information. This is why PCI DSS compliance is critical for whoever holds the tokens.
Integration flow
With Querytail's pass-through model:
- The customer decides to purchase through your Agentic Client Advisor
- Querytail orchestrates the payment request to your PSP (Stripe, Adyen, or your current processor)
- Your PSP collects payment method details (card, Apple Pay, Google Pay, bank account, etc.)
- Your PSP transmits the request to the customer's bank
- The bank approves or declines
- Your PSP returns the result to Querytail
- Querytail confirms the transaction in the chat
- Your fulfillment system and CRM receive the full order details and customer data
You see orders in your fulfillment dashboard and in your PSP dashboard, exactly as you would with a traditional checkout. The difference is that the customer completed the entire journey inside the conversation.
Payment method support
Because Querytail connects to your PSP, you have access to all the payment methods your processor supports:
- Credit and debit cards (Visa, Mastercard, American Express, Discover)
- Digital wallets (Apple Pay, Google Pay)
- Bank transfers (ACH in the US, SEPA in Europe)
- Regional payment methods (iDEAL in the Netherlands, Giropay in Germany, etc.)
Customers can choose their preferred method without leaving the chat. Each method is processed through the same secure infrastructure, so your operational workflow remains consistent.
Trust and the customer perspective
From the customer's perspective, MoR status directly affects whether they feel safe completing a transaction.
Conversational commerce is still relatively new. Many customers are cautious about buying through an AI interface. If the purchase process requires redirecting to an external payment page, customers may lose confidence. The redirect can feel like a bait-and-switch: they were talking to a helpful AI, and now they're on a generic payment page that could belong to anyone.
When payment happens in-chat, the experience feels integrated and trustworthy. The Agentic Client Advisor remains present, answering final questions. The customer sees consistent branding throughout. The transaction happens in the same context as the product discussion.
This matters psychologically and operationally. Studies in traditional e-commerce show that checkout friction (redirects, extra form fields, unclear security) increases cart abandonment. Conversational commerce should reduce friction, not add it. In-chat payment, enabled by Querytail's pass-through orchestration, accomplishes this.
Additionally, customers are more likely to trust a transaction when they see a familiar brand name on their bank statement. With Querytail's model, the charge comes from you, not from a platform intermediary they have never heard of. This reinforces your brand at the most critical moment of the customer relationship: the moment they pay.
Cross-border commerce and MoR simplification
International selling creates substantial compliance complexity. You must handle:
- Currency conversion
- Local tax and VAT requirements
- Consumer protection laws in each country
- Payment method preferences (what's popular varies by region)
- Language and localization
MoR status amplifies this complexity if you're the MoR. You're responsible for understanding VAT thresholds in every EU country, calculating tax correctly, filing returns, and handling disputes under local consumer protection laws.
Querytail simplifies this without becoming the MoR. Our infrastructure connects to your tax compliance tools and your PSP's multi-currency capabilities, so you can:
- Calculate local tax automatically through your existing tax engine
- Accept payment in the customer's local currency through your PSP
- Maintain consumer protection compliance with your legal team
- Support payment methods popular in each region through your processor
- Keep all customer data in your systems, regardless of geography
This allows you to expand internationally while retaining full ownership of the customer relationship. You maintain control of pricing, data, and compliance strategy. Querytail provides the AI orchestration layer that makes it all happen inside the conversation.
Comparing MoR in Agentic Commerce vs. traditional marketplaces
The Merchant of Record concept isn't new. Amazon, eBay, and Shopify all rely on MoR models. But Agentic Commerce (where an AI agent facilitates the sale) introduces unique considerations.
Traditional marketplace (Amazon)
Amazon is the MoR. You (the seller) list products on Amazon's platform. A customer buys through Amazon, and Amazon processes the payment. Amazon holds the customer relationship and bears compliance liability. You ship the product and handle customer service. Amazon takes a commission and assumes all MoR obligations.
Benefits: minimal compliance burden for sellers
Drawbacks: Amazon controls pricing, branding, customer communication, and takes a significant commission
Direct sales on Shopify
You are the MoR. You own the store, build the customer relationship, and handle payments through Shopify's infrastructure. Shopify provides the payment processing and infrastructure but doesn't assume MoR status. You're responsible for tax, compliance, and chargebacks.
Benefits: complete control over customer experience and brand
Drawbacks: you must handle compliance and risk
Agentic Commerce with Querytail (sovereign pass-through)
You are the MoR. Your Agentic Client Advisor (powered by Querytail) facilitates the sale. The customer conversation happens in your interface. You control the customer experience, product information, pricing strategy, and the entire customer data set. Querytail orchestrates the payment through your PSP via the Agentic Commerce Clearing (ACC) layer, but never becomes the seller.
Benefits: full customer ownership, full data sovereignty, conversational checkout without friction, no platform intermediary
Drawbacks: you maintain MoR compliance responsibility (with your existing tools)
The key difference is that Querytail does not replicate the Amazon model. We do not sit between you and your customer. We amplify your existing commerce stack with AI intelligence while your customer relationship, your data, and your revenue stay exactly where they belong: with you.
Frequently asked questions
Q: If I remain the MoR, do I still get In-Chat Checkout?
A: Yes. That is the entire point of Querytail's approach. Our Agentic Client Advisor completes transactions inside the conversation, and the payment is routed directly to your PSP. The customer never leaves the chat, and you never lose ownership of the transaction.
Q: What happens if a customer wants a refund?
A: You handle refunds through your PSP, exactly as you would with a traditional checkout. Querytail's Agentic Client Advisor can initiate the refund conversation with the customer, but the financial operation flows through your payment infrastructure. You maintain full control over refund policies and timing.
Q: Do I need to change my current PSP to use Querytail?
A: No. Querytail integrates with your existing PSP (Stripe, Adyen, or others). That is the "Bring Your Own PSP" model. You keep your processor, your rates, your chargeback history, and your merchant account. Querytail adds the AI conversation layer on top.
Q: What payment methods can customers use?
A: Whatever your PSP supports. If your Stripe or Adyen account is configured for credit cards, Apple Pay, Google Pay, bank transfers (ACH/SEPA), and regional payment methods like iDEAL or Giropay, all of those are available inside the chat. Querytail does not limit your payment options.
Q: Why don't other AI commerce platforms offer this model?
A: Because the Platform-as-MoR model is more profitable for platforms. When the platform is the merchant of record, the platform captures the customer data, controls the pricing, and takes a larger commission. Querytail was built on the principle that merchants should own their commerce, not rent it.
Q: What about compliance? Don't I need more infrastructure if I'm the MoR?
A: If you already sell online (via Shopify, WooCommerce, Magento, or any e-commerce platform), you already handle MoR obligations for your existing checkout. Querytail does not add compliance burden. It simply extends your existing checkout into the conversation. Your tax tools, your anti-fraud engine, and your PSP work exactly the same way.
Q: What happens if there's a security breach or payment dispute?
A: Because Querytail never stores or processes payment card data (it routes everything to your PSP), the security model is the same as your current checkout. Your PSP handles PCI DSS compliance and tokenization. If a customer disputes a charge, the chargeback goes to your merchant account, and you resolve it with your PSP as you normally would.
Q: How do you handle multi-currency transactions?
A: Multi-currency is handled by your PSP. Querytail passes the customer's location and currency preference to your processor, which handles conversion at your configured rates. You see the settlement in your usual reporting dashboard.
Conclusion
The Merchant of Record is a legal concept that becomes critically important in conversational commerce. Someone must be responsible for collecting payment, managing compliance, and bearing liability. The question is: should that someone be you, or a platform intermediary that captures your customer data in the process?
Querytail's answer is clear. You should remain the seller. Your customer data, your LTV, and your billing relationship should stay with you. The AI layer should amplify your commerce, not replace your ownership of it.
Most AI commerce platforms take the easier path: they become the MoR, they capture the data, and they position this as a feature. Querytail takes the harder path, the sovereign path, because we believe that brands building long-term value need to own their customer relationships from Day 1.
Conversational commerce is expanding the ways customers discover and buy products. With Querytail's pass-through model, you can offer frictionless transactions inside the conversation while keeping full control of the commerce itself. Do not let AI steal your customers.
AI Commerce Technology Series.
This article is part of Querytail's AI Commerce Technology series. Next in the series: How Agent Cards work: structured product data for AI engines. Explore the full series:
- The Semantic Firewall: how zero-hallucination AI works
- In-Chat Checkout: from prompt to payment
- Merchant of Record in conversational commerce (you are here)
- How Agent Cards work
Querytail is the AI Commerce Layer for e-commerce brands. Request a demo.
You can also contact our team with any questions, or if you are a brand looking for early access, apply for the Design Partner program.