What 'Merchant of Record' Actually Means
The term gets used loosely in payments marketing. Here's what it actually changes about who's liable for what when a sale happens.
If you've shopped for payments infrastructure for a software or digital-product business, you've run into the term "merchant of record" (MoR) — usually in a sales pitch, rarely with a precise definition. It's worth being precise about, because it describes a real legal and operational shift, not a marketing flourish.
The seller on the receipt
Every card transaction has a merchant of record: the legal entity that is contractually the seller to the customer and to the card networks. That entity's name is what shows up on the customer's bank statement. It's the entity that agreed to Visa and Mastercard's operating rules. It's the entity that's on the hook if a chargeback comes in.
When a software company processes payments directly — through a payment processor connected to its own merchant account — that company is the merchant of record. It carries the relationship with the card networks, it's liable for fraud and chargebacks, and in most jurisdictions, it's the entity responsible for calculating, collecting, and remitting transaction taxes on the sale.
A merchant-of-record platform changes who occupies that role. The platform becomes the seller on the transaction. The software company is still the one building and supporting the product, still owns the customer relationship in every way that matters commercially, but the platform is the legal party to the sale itself.
What actually moves
Three things change hands when a platform becomes the merchant of record instead of the software company:
Card network liability. Chargeback handling, fraud liability, and the underlying merchant account relationship become the platform's responsibility, not the software company's. This is the mechanism that lets a small or newly formed company accept cards globally without underwriting its own merchant account in every market it sells into.
Tax determination and remittance. Sales tax, VAT, and GST on digital goods are determined by where the buyer is, not where the seller is — and the rules differ by product type, buyer status (business vs. consumer), and jurisdiction. When a platform is the merchant of record, it's the one responsible for calculating the applicable tax, collecting it as part of the sale, and remitting it in the buyer's jurisdiction. It does not, on its own, make the underlying software company's income tax obligations disappear.
Compliance surface. PCI DSS scope, card network rules, and a chunk of AML/KYC obligations move to the platform's side. The software company still has its own obligations — as a business, as an employer, as a data controller — but the payments-specific compliance burden narrows to what's still on it: things like maintaining accurate product/pricing information and honoring its own terms with customers.
What doesn't change
A merchant-of-record arrangement is not a white-label acquisition of your business. The software company still:
- Sets its own pricing and product structure
- Owns the customer relationship, support, and product roadmap
- Is responsible for the accuracy of what it's selling and how it's described
- Retains its own tax obligations that have nothing to do with the sale itself (payroll tax, corporate income tax, etc.)
It's also worth being clear about what an MoR platform is not automatically providing: it is not a guarantee of legal compliance in every market, a substitute for a company's own terms of service, or a certification of any kind. Serious MoR providers are explicit about what's covered and what isn't, and a company selling internationally should confirm the specifics for the markets that matter to it rather than assume blanket coverage.
Why this exists as a category
The underlying reason this model exists: card network underwriting and tax remittance obligations are expensive and slow to build correctly, and doing them wrong has real consequences — failed audits, blocked payouts, disputes with tax authorities. A platform that specializes in being the merchant of record can amortize that operational cost across many sellers, in the same way that a payroll provider amortizes the cost of getting withholding calculations right across many employers.
The tradeoff is a percentage of revenue, taken at the point of sale, in exchange for not building and maintaining that infrastructure yourself. Whether that tradeoff makes sense depends on how much of your sales are cross-border, how much friction your team wants to carry, and how far along you are — it's a real decision, not a foregone conclusion, and it's one worth revisiting as a business scales into new markets rather than deciding once and forgetting about it.