Merchant of Record vs. Payment Processor: What's the Difference

These two categories of provider get conflated constantly, partly because a merchant-of-record platform necessarily includes payment processing as part of what it does. But the distinction matters for anyone deciding how to accept payments for a software or digital-product business.

A payment processor moves money on your behalf

A payment processor (or "payment service provider") gives you the rails to accept a card or bank payment and routes the funds to your own merchant account. Your company is still the merchant of record: your business name (or a doing-business-as name you registered) appears on the statement, your business absorbs chargeback and fraud liability, and your business is responsible for figuring out and remitting whatever transaction taxes apply in the places you sell.

The processor's job ends at moving the money and giving you tools — hosted checkout pages, a dashboard, an API, fraud screening — to make that easier. It does not make you exempt from tax registration in the countries where your buyers are, and it does not take on liability if your product violates a card network's rules.

A merchant of record stands in as the seller

A merchant-of-record platform is a step further: it doesn't just move money, it becomes the legal seller of the transaction. That means it takes on the merchant-account relationship, the chargeback and fraud liability, and — critically for anyone selling digital goods across borders — the determination and remittance of sales tax, VAT, or GST in the buyer's jurisdiction.

The operational shape is similar from a developer's point of view (checkout sessions, webhooks, a dashboard), but the legal substance underneath is different, and that difference is exactly what an MoR arrangement is priced for.

Where the line actually matters

The distinction shows up concretely in a few places:

Tax registration. If you use a payment processor and sell a digital subscription to a customer in Germany, you (not the processor) are generally the party responsible for German VAT — registration, calculation, collection, and remittance, either directly or through a fiscal representative. If you use a merchant-of-record platform, that obligation sits with the platform for the transactions it processes as merchant of record.

Chargebacks. With a processor, a chargeback dispute is between your business and the card network, mediated by the processor's tools. With an MoR platform, the platform is the party responding to the dispute, because it's the merchant on the transaction — though platforms differ in how (and whether) they pass the underlying cost or a portion of it back to you, so this is worth checking in any specific provider's terms.

Underwriting. A processor requires you to pass its own underwriting to get a merchant account (or a sub-account under its umbrella), and that underwriting can be a real blocker for a new company, a high-risk category, or a business without established processing history. An MoR platform underwrites the platform's relationship with the card networks once, and individual sellers go through a lighter onboarding and compliance review instead.

Neither is "better" in the abstract

A payment processor is the right tool when a company wants to own its own compliance and tax posture — usually because it's already large enough to have that infrastructure, sells overwhelmingly in one jurisdiction, or has specific reasons to control the merchant relationship directly.

A merchant-of-record platform is the right tool when the cost of building and maintaining tax and card-network compliance outweighs the percentage taken at the point of sale — commonly true for smaller teams selling internationally, or teams that would rather have engineers building product than payments infrastructure.

Neither answer is universal, and it's worth revisiting the choice as a business changes shape rather than treating it as fixed at the moment a company first picks a payments stack.