The moment you decide to sell in a new country, you inherit a tax problem. Not eventually – immediately. Germany expects 19% VAT collected and remitted. Japan has its own consumption tax registration threshold. Australia has GST rules that kick in at AU$75,000 in global revenue. Canada has provincial variations sitting on top of federal ones. And in the US you have over 12,000 taxing jurisdictions each with its own rates and rules, and you're on the hook to monitor sales in each one before you hit nexus and trigger registration obligations.
And every jurisdiction expects you to register, collect, and file on their schedule.
That’s before you’ve processed a single payment. It’s before you’ve dealt with a chargeback, issued a refund, or figured out whether a B2B sale to a French company is even taxable the same way a B2C one is.
A Merchant of Record solves this problem. This guide explains exactly what a Merchant of Record is, how the model works, what it costs you to go without one, and how to decide whether it’s right for your SaaS or AI business in 2026.
What Is a Merchant of Record?
A Merchant of Record (MoR) is the legal entity that processes transactions, assumes tax and compliance responsibility, and manages refunds and liabilities for every sale made on your behalf.
When a customer buys your product through an MoR, the MoR – not you – appears as the seller on their bank or credit card statement. The MoR issues the invoice. The MoR collects and remits the applicable taxes. The MoR owns the compliance obligations in every market where a sale occurs.
Your company still owns the product, the customer relationship, and the revenue. But the legal and operational surface area of selling shrinks to almost nothing on your side.
The principal responsibilities an MoR takes on include:
Payment processing: Collecting payment from the buyer in their preferred currency and method
Tax registration and remittance: Registering for VAT, GST, and sales tax in applicable jurisdictions and filing on your behalf
Invoice issuance: Generating compliant invoices that satisfy local legal requirements
Chargeback and dispute management: Handling disputes with payment networks directly
Regulatory compliance: Maintaining PCI DSS, GDPR, and regional standards such as PSD2
The MoR is the legal seller of record. You are the underlying supplier.
How the Merchant of Record Model Works
The MoR model runs on a two-transaction structure that most founders never think about until they’ve already built the wrong payments stack.
Transaction 1: Customer to MoR. When your customer checks out, they are buying from the MoR. The MoR’s name appears at the point of purchase and on the payment statement. The MoR processes the payment, collects applicable taxes, and issues a compliant invoice.
Transaction 2: MoR to Merchant. The MoR then pays you – the underlying submerchant company – after deducting its fees, taxes collected, and any reserves for potential disputes.
This structure removes the need for you to register legal entities in every market you sell into. You don’t need a local subsidiary in Germany to collect German VAT. The MoR handles it.
Merchant of Record vs. Payment Facilitator vs. PSP
These three models get conflated constantly, and confusing them creates real business risk.
Payment Service Provider (PSP): A PSP processes payments but does not assume legal or tax liability for your sales. Stripe, Braintree, and Adyen are PSPs. They move money. They do not file your taxes, manage your VAT registrations, or take a chargeback on your behalf. You retain all compliance obligations.
Payment Facilitator (PayFac): A PayFac aggregates merchants under its own master merchant account. It simplifies onboarding but – like a PSP – does not assume legal liability for your sales or tax obligations.
Merchant of Record: The MoR takes on legal responsibility as the seller in every transaction. It owns compliance, tax registration, and dispute liability.
Responsibility | MoR | PSP | PayFac |
|---|---|---|---|
Processes payments | Yes | Yes | Yes |
Tax registration (VAT/GST/sales tax) | Yes | No | No |
Remits taxes to authorities | Yes | No | No |
Liable for chargebacks | Yes | No | No |
Issues compliant invoices | Yes | No | No |
Appears as seller on statements | Yes | No | No |
Handles regulatory compliance | Yes | Partial | Partial |
The core difference is liability. A PSP gives you infrastructure. An MoR gives you a legal backstop.
Why SaaS and AI Founders Need a Merchant of Record
In order to sell your software globally from day one building a global payments operation from scratch is expensive and slow. You need a tax attorney in every significant market. You need someone managing VAT filings, GST thresholds, and US sales tax nexus rules. You need chargeback management infrastructure. You need PCI DSS compliance.
For an early-stage SaaS or AI product, that overhead can consume more engineering and legal time than the product itself.
The MoR model solves five specific problems for founders:
No foreign entity requirements. Sell in foreign countries without incorporating locally or registering for tax individually.
Instant compliance coverage. The MoR handles VAT, GST, and digital services taxes across jurisdictions as they evolve.
Chargeback protection. Disputes go to the MoR, not your merchant account – protecting your payment processing relationships.
Faster go-to-market. Launch internationally in weeks instead of the months or years it takes to build compliant infrastructure.
Engineering focus. Your team ships product instead of building tax calculation logic or managing payment gateway integrations.
Solo founders and indie developers in particular benefit from MoRs. Without a finance team or legal counsel, the compliance burden of global sales is functionally unmanageable alone.
Key Responsibilities and Compliance Obligations
When an MoR takes on your sales, it accepts a specific and legally significant set of obligations:
VAT and GST collection and remittance across all applicable jurisdictions
US sales tax nexus management across states
Digital services tax compliance in applicable markets (UK DST, France, Spain)
PCI DSS Level 1 compliance for payment data security
GDPR and data privacy compliance for EU customer data
PSD2 Strong Customer Authentication for European transactions
Refund and chargeback liability – the MoR absorbs dispute costs, not you
E-invoicing compliance in markets with mandatory electronic invoicing (Italy, India, others)
The MoR appears as the seller of record on every invoice and payment statement. That legal designation carries real weight: regulators look to the seller of record when auditing tax compliance.
Benefits of Partnering with a Merchant of Record
Operational:
Single integration point for global payments, tax, and compliance
No manual tax filing in new jurisdictions
Reduced engineering overhead for billing and payment infrastructure
Chargebacks handled without touching your merchant account
Strategic:
Immediate access to global markets without foreign entities
Native subscription management (trials, upgrades, proration, dunning)
Support for emerging payment methods: wallets, local payment types, and multi-currency checkout
Fraud detection and prevention
Quick benefits for AI businesses specifically:
Usage-based billing (per token, per API call, per seat/credit)
Metered subscriptions that flex as consumption scales
Compliant invoicing for variable monthly charges
When to Use a Merchant of Record: Matching Model to Stage
The MoR model fits differently depending on where you are.
Indie developers and micro-SaaS founders: Use an MoR from day one. The compliance burden of global digital sales is too high to manage manually, and the cost of DIY infrastructure far exceeds MoR fees at small scale. The no-code and hosted checkout options many MoRs offer mean you can launch in days.
Growth-stage SaaS (Series A–B): MoRs become essential when you’re expanding into new regions, adding enterprise billing structures, or needing multi-currency support. Localization, retention tooling, and subscription lifecycle management matter more at this stage – evaluate MoRs that cover those capabilities, not just tax compliance.
Enterprise and regulated markets: Compliance-first MoRs with strong e-invoicing, procurement workflows, and audit-ready accounting output are the priority. Revenue recognition aligned with ASC 606 and IFRS 15 matters for enterprise customers and investors.
How to Choose the Right Merchant of Record Provider
Evaluate MoR providers against these criteria before you commit:
Billing model coverage: Does it support per-seat, usage-based, hybrid, and proration billing out of the box? For AI products, usage metering and credit-based billing are non-negotiable.
Tax liability clarity: Confirm in writing who registers, collects, files, and remits taxes. Not all providers claiming an MoR model assume full tax liability.
Revenue recognition support: Does the platform output ASC 606 / IFRS 15-compatible data for your accounting close? This matters from Series A onward.
Payment method and currency coverage: Identify your top target markets and confirm the provider supports the local payment types customers actually use there.
Integration footprint: How does the MoR connect to your CRM, analytics stack, entitlement logic, and ERP? A billing system that creates data silos generates more operational overhead than it removes.
Developer experience: SDK quality and API documentation significantly affect how fast you can ship. A lightweight, well-documented SDK reduces integration time and ongoing maintenance burden.
Integration Considerations for SaaS and AI Platforms
Most MoR providers offer four integration paths:
Hosted checkout: The MoR hosts the payment page. Fastest to launch, least customizable.
Embedded SDK: A lightweight SDK handles payment and billing logic within your own UI.
API-first: Full control over the checkout experience via API calls. Highest engineering effort.
No-code setup: Dashboard-based configuration for solo founders or pre-launch products.
Subscription lifecycle events – trials, plan upgrades, proration, renewals, failed payment recovery – should all flow through the MoR’s system or connect cleanly to yours. Audit what data the MoR keeps and what it exposes back to you. Customer-level billing history, subscription state, and entitlement data are often more locked-in than founders expect.
Managing Customer Relationships and Data
The MoR appears as the seller on your customer’s payment statement can have real implications.
When a customer sees an unfamiliar company name on their credit card bill, they often don’t recognize the charge. They contact their bank rather than your support team. That creates chargebacks you didn’t expect and churn you can’t address.
Some MoRs allow white-labeled or co-branded billing statements. If brand recognition matters to your customers – and it usually does – verify what the payment statement looks like before you sign a contract.
The division of customer responsibilities typically looks like this: the MoR handles payment-related support (refunds, billing disputes, invoice requests), while you retain ownership of product support, customer success, and subscription decisions. In practice, blurry handoffs between MoR and submerchant support teams create friction. Map this out before you launch.
Step-by-Step Checklist for SaaS and AI Founders
Before you commit to an MoR – or decide to build your own stack – run through this:
Map your billing requirements for the next 12 to 24 months. Do you need usage metering, per-seat billing, AI credit sales, or enterprise invoicing? Define this before you talk to a vendor.
Calculate the true cost of building yourself. Include tax attorney fees, tax software subscriptions, finance team time on filing, developer time on payment infrastructure, and chargeback handling costs. Most founders undercount this.
Confirm legal and tax liability assignments in writing. Ask directly: Who is the seller of record on invoices? Who files VAT returns? What happens in a tax audit?
Test accounting and revenue recognition outputs. Request a sample data export. Confirm it maps to your accounting standards before you have a thousand subscribers locked in.
Verify payment method coverage in your target markets. Credit cards are not universal. Local payment methods drive conversion in high-priority markets.
Pilot with a subset of customers before full migration. Monitor dispute rates, chargeback incidents, and customer confusion around billing statements. Catch problems before they scale.
Frequently Asked Questions
What is the difference between a Merchant of Record and a payment processor?
A payment processor moves money between parties but assumes no legal or tax liability for the sale. A Merchant of Record is the legal seller – it owns tax registration, remittance, and compliance obligations in every jurisdiction where a transaction occurs.
Who is legally responsible for taxes and compliance when using an MoR?
The Merchant of Record is the legally responsible entity. It registers for applicable taxes, collects them at point of sale, and remits them to the relevant authorities. Your company is not the seller of record and does not carry those obligations.
How does an MoR affect my customer relationship and branding?
The MoR’s name appears on the customer’s payment statement and invoice. This can cause recognition issues if the MoR name differs significantly from your product name. White-labeled billing options exist but vary by provider – verify this before signing.
Can a Merchant of Record support usage-based and AI-specific billing models?
Yes. Leading MoRs now support per-seat, usage-metered, token-based, and hybrid billing models. For AI products with variable consumption, confirm the MoR supports real-time usage ingestion and mid-cycle billing adjustments.
When should a SaaS or AI company consider moving away from an MoR?
At significant scale – typically when payment infrastructure control, custom compliance management, or proprietary checkout experiences become strategic requirements. Migration is complex and should be planned well in advance, not triggered by dissatisfaction with a single incident.
