Merchant of Record

Also called MoR, MOR, seller of record

The legal entity that appears on the customer's statement and owns the liability: chargebacks, refunds, sales tax and compliance.

What it is

The merchant of record is whoever is legally selling to the cardholder. That entity's name appears on the customer's card statement, that entity is responsible for collecting and remitting sales tax, handling refunds and disputes, absorbing chargebacks, and complying with card network rules and consumer protection law. In a normal merchant account, you are the merchant of record. That is the default and, for most local businesses, the right answer. The concept becomes important when a platform stands between you and the customer. A payment facilitator, a marketplace, a subscription platform or an MoR service like Paddle or FastSpring may become the merchant of record instead of you — taking on the tax registration, the chargeback liability and the compliance burden in exchange for a higher rate and control of the customer relationship. Under the Agentic Commerce Protocol that Stripe and OpenAI shipped, the merchant remains the merchant of record: the merchant still accepts or declines the order, charges the card, calculates and remits sales tax, and owns fulfillment and returns. The trade is always the same. Being merchant of record means lower cost, direct customer relationship, and full liability. Not being merchant of record means higher cost, someone else's name on the statement, and someone else's problem when a dispute lands.

Why it matters to your business

If your business name is not what shows on your customer's statement, you will get more chargebacks. "I don't recognize this charge" is one of the most common dispute reasons, and a mismatched or unrecognizable descriptor manufactures those disputes out of nothing. This is a five-minute fix that almost nobody checks. And if a platform is acting as your merchant of record, you should know it, because it changes who you call in a dispute, who owns your customer data, and how hard it is to leave. That last point is the one people discover too late.

Where it gets contested

The dispute here is about who benefits from the MoR shift and whether merchants understand what they gave up. When a platform becomes merchant of record, the merchant loses direct visibility into the customer, loses the ability to move processing without re-papering the customer relationship, and often loses the transaction data. Platforms argue — correctly — that they are absorbing global tax registration, fraud liability and regulatory compliance that a small seller genuinely cannot handle across dozens of jurisdictions. Where it gets murky is in embedded payments and PayFac models, where the merchant's descriptor and liability position are frequently unclear even to the merchant. Rainforest's 2026 comparison of PayFac platforms flags that Stripe Connect "lacks clarity on who owns risk" and that legacy processors can trap platforms with token export fees and non-solicit clauses. Those are structural warnings about exactly this ambiguity. There is no villain in this one. There is a category of merchant — the local restaurant, contractor or retailer — for whom giving up merchant-of-record status is almost always a bad trade, and a category — the global digital seller with VAT exposure in 40 countries — for whom it is obviously a good one.

How to check it yourself

Run a $1 charge on your own personal card, then look at how it appears in your banking app. If the descriptor isn't your recognizable business name plus a phone number, get it changed today — your processor can update it, usually within a day, at no cost.

Receipts

Claims above that are checkable, with where to check them. Published so you do not have to take anyone's word for it.

Under the Agentic Commerce Protocol, the merchant still accepts or declines the order, charges the card, calculates and remits sales tax, and owns fulfillment and returns
agenticcommerce.dev ↗
Rainforest's 2026 PayFac platform comparison flags that Stripe Connect "lacks clarity on who owns risk" and that legacy processors can trap platforms with token export fees and non-solicit clauses
rainforestpay.com ↗