Merchant of Record: What It Is and When SaaS Needs One

A merchant of record (MoR) is the legal seller of a product, even when someone else built it. The MoR takes the payment, issues the receipt, handles refunds and chargebacks, and is on the hook for sales tax and VAT. In a merchant of record SaaS arrangement, the vendor takes on billing and tax for the software business. The SaaS company keeps building software. The MoR owns the transaction. That split sounds simple, but it moves risk, revenue recognition and customer control from one party to another, and those shifts decide whether a SaaS company should use one.

What the merchant of record actually takes on

Payment processors move money. A merchant of record owns the sale. That distinction sits at the center of every MoR decision, so it helps to spell out the obligations.

• Legal seller status. The MoR appears on the customer's receipt and card statement. Disputes with the customer are between the customer and the MoR.
• Sales tax and VAT. The MoR calculates, collects and remits tax in each jurisdiction where it has an obligation. That includes monitoring registration thresholds as they change.
• Chargebacks and fraud. The MoR usually absorbs the loss from a successful chargeback and runs its own fraud screening.
• Refund and cancellation processing. The MoR refunds on the vendor's instruction and handles the customer's complaint about the charge.
• Billing infrastructure. Checkout, card updates, dunning and local payment methods sit with the MoR in a full-service arrangement.

The trade is control for overhead. The SaaS company gives up direct ownership of the customer transaction and receives someone else's team, tax engine and risk budget in return.

How merchant of record payments work on a subscription

Merchant of record payments behave differently from ordinary card processing because the MoR, not the SaaS company, is the party on the recurring charge. The sequence on a typical subscription looks like this:

1. The SaaS company's checkout hands the purchase to the MoR. The customer sees the MoR listed as the seller.
2. The MoR processes the first payment, applies the correct tax rate based on the customer's location, and sends a compliant invoice.
3. On renewal, the MoR charges the stored payment method and keeps the subscription running. Failed cards go into dunning, often with automated retries and customer emails.
4. The MoR remits tax to the relevant authorities on its own schedule.
5. The MoR pays the SaaS company a net amount, usually on a rolling schedule, minus its fee.

The client's experience is the part founders miss. When a customer disputes a charge, they may call the SaaS support line. Support sends them to a seller they have never heard of. Keeping that handoff smooth is a real operational cost of the model.

The revenue and accounting difference that catches teams out

Under a merchant of record setup, the SaaS company is often acting as the supplier to the MoR, not the seller to the customer. Two consequences follow.

First, revenue may be recorded net of the MoR's fee and any tax it collected, not as gross bookings. That changes reported revenue, gross margin and metrics such as net revenue retention if the comparison crosses a switch to or from the model. Finance teams should confirm the treatment with their accountant before migrating a book of business.

Second, the customer relationship is split. The SaaS company usually retains the account, usage data and product relationship. The MoR owns the payment relationship, the receipt and the chargeback record. Some arrangements give the SaaS company a copy of transaction data; others do not. Contract terms on data access and on who handles refund approvals matter more than the headline fee.

When a SaaS company needs a merchant of record

A merchant of record makes sense when the cost of doing billing yourself exceeds the fee. That threshold is different at every stage, so check against the factors below rather than a rule of thumb.

Global customer base with small average deal sizes. Selling a $20 seat into a dozen countries means registering for tax in each one and filing on local deadlines. For a small team, the fixed cost of registrations and filings often outweighs a percentage fee on each transaction.

Rapid country expansion. Adding a new market through the MoR can be a settings change instead of a legal and tax project. The trade is less control over local payment methods and pricing presentation.

Consumer or self-serve checkout. A card-not-present volume-based checkout attracts fraud attempts. Handing fraud screening and chargeback liability to the MoR removes a large part of that exposure, at a price. Crypto acceptance works differently, since on-chain payments have no chargebacks; if your customers ask for that route, treat it as a separate payment option with its own settlement and accounting steps.

Thin finance and legal coverage. A company with no tax specialist and no billing engineer is a strong candidate. A company with both may find in-house processing cheaper and more flexible.

A merchant of record is the wrong fit when the product sells almost entirely in one country, the customer base is enterprise and invoice-based, or the buyer wants named direct billing relationships. In those cases the tax burden is smaller and the lost control matters more.

Comparing merchant of record and payment processor

The choice is usually between a full MoR, a payment processor or gateway paired with a separate tax tool (sometimes called merchant of record-lite), and fully in-house billing. The table below summarizes where each sits. Fee levels and contract terms vary by provider and volume, so treat the comparison as a checklist and verify the specifics directly.

Questions to ask before signing

Terms are negotiated, not fixed. Get answers in writing on the points below.

• Who approves refunds, and how fast does the request reach the MoR?
• Which customer data does the SaaS company receive, and how long does the MoR retain it?
• Does the fee apply to the full transaction amount, including tax, or to revenue net of tax?
• What happens to subscribers if the contract ends? Can billing records move?
• Which countries and payment methods are covered, and which need a separate arrangement?
• Who handles tax rules that change after launch?

Also check the payment schedule and reserves. Some MoRs hold a portion of proceeds against future disputes, which affects cash flow for a growing subscription book.

Practical takeaway

Use a merchant of record when global tax, fraud and chargeback work would cost more than the fee, or when speed to a new market decides the year. Pay attention to revenue treatment, data access and refund control before signing, because those terms shape your metrics and your support workload long after the fee question is settled.

For a company selling in one country with an invoice-based customer base, a processor and a tax tool often fit better. Run the numbers on revenue, tax exposure and support load for your own book; general information only, not financial, legal or tax advice.