Glossary

What is a merchant of record?

The merchant of record is the business legally responsible for a sale. What it handles, and why agentic commerce protocols keep the seller in that role.

The merchant of record is the business legally responsible for selling to the customer and processing their payment, including refunds, chargebacks, tax and payment compliance.

How does it work?

Stripe defines the merchant of record as the entity legally authorised and responsible for processing customer payments, and liable for the financial, legal and compliance aspects of the transaction. That covers handling refunds and chargebacks, calculating, collecting and remitting sales tax or VAT, and meeting rules such as PCI DSS and anti-money-laundering requirements. A business that takes payments directly through a processor like Stripe stays the merchant of record; the processor handles the payment, not the legal sale. In agentic commerce the question becomes: when an AI assistant buys something for a user, who is the seller? The Agentic Commerce Protocol, developed by Stripe and OpenAI, answers that businesses keep their customer relationships as the merchant of record, with control over which products can be sold, how they're presented and how orders are fulfilled. The agent and the AI platform coordinate the checkout; they don't become the seller. That keeps refunds, disputes and tax where they already are.

In practice

If you sell through agents, check which party each integration makes the merchant of record, because that decides who handles refunds, who appears to the customer as the seller and who owes the tax. Under ACP it stays you. If you build an agent that buys things, your users' disputes still go to the seller and the card or payment provider, not to you, but you should keep a record of what the agent bought and why so the user can raise one. If you pay by stablecoin transfer rather than card, read the seller's refund terms: a confirmed on-chain transfer has no chargeback process.

What it does not mean

  • The merchant of record isn't necessarily the payment processor. Stripe says a business taking direct payments through it remains the MoR.
  • An AI agent or platform completing a checkout doesn't become the merchant under ACP.
  • It isn't the same as the brand on the product. A reseller or marketplace can be the MoR for goods it didn't make.
  • Nothing here is tax or legal advice; who is MoR in a given contract is set by that contract.

Where does Veyra fit?

Veyra is never a merchant of record. It is on the payer side only: it doesn't accept payments for merchants, doesn't sell anything on your behalf and doesn't handle refunds or disputes. Once a payment is confirmed on-chain, Veyra can't reverse it; get_payment returns the transaction reference and explorer link you'd use as proof of payment with the seller.

Veyra's spend policy for one agent endpoint: per-transaction limit, daily limit, auto-approve limit, ask-up-to limit and recipient allowlist
What this looks like in Veyra: one spend policy per agent endpoint, with a per-payment cap, a daily cap, an auto-approve band, an ask band and a recipient allowlist, all checked on the server. Try the free policy generator →

Sources

Guides that use this term

This page explains how agent payments and the related technology work. It is not financial, investment, legal or tax advice. Protocols and provider features change; check the linked official sources before relying on a detail.