Merchant of Record (MoR) Model: Legal Tax Responsibility for SaaS Developers

Introduction to the Merchant of Record Model

A Merchant of Record (MoR) is a legal entity that serves as the official seller of record in a transaction between a business and its customers. The MoR takes on the responsibility for processing payments, managing tax compliance, ensuring regulatory adherence, and handling financial liabilities associated with online sales. This model is particularly valuable for SaaS developers and indie software publishers who want to focus on product development rather than complex tax compliance issues.

How the Merchant of Record Model Works

Legal Structure and Transaction Flow

When a SaaS company or indie developer uses a Merchant of Record service, two distinct transactions occur:

  1. First Transaction: The end customer purchases from the MoR (not directly from the SaaS developer)
  2. Second Transaction: The MoR pays the SaaS developer (minus fees and taxes)

This structure creates a legal separation that shifts tax and compliance responsibilities from the developer to the MoR provider. The following flowchart illustrates this process:

┌─────────────────┐     Purchase     ┌─────────────────┐
│                 │  ───────────►    │                 │
│   End Customer  │                  │  Merchant of    │
│                 │  ◄───────────    │     Record      │
└─────────────────┘   Receipt/       └─────────────────┘
                      Invoice               │
                                            │ Remittance
                                            │ (minus fees & taxes)
                                            ▼
                                    ┌─────────────────┐
                                    │                 │
                                    │  SaaS Developer │
                                    │                 │
                                    └─────────────────┘

Legal Responsibilities Assumed by the MoR

The Merchant of Record assumes several critical legal and financial responsibilities:

  1. Tax Calculation and Collection: Determining the correct tax rates based on customer location and product type
  2. Tax Filing and Remittance: Submitting tax returns and payments to relevant authorities
  3. Payment Processing: Managing the entire payment infrastructure
  4. Regulatory Compliance: Ensuring adherence to financial regulations across jurisdictions
  5. Fraud Prevention: Implementing and maintaining fraud detection measures
  6. Chargeback and Refund Management: Handling disputes and returns
  7. Currency Conversion: Managing international payments and exchange rates
  8. PCI DSS Compliance: Maintaining payment card industry security standards

Legal Shift of Tax Responsibilities

From Developer to MoR

The most significant benefit of the MoR model is the legal transfer of tax obligations. Without an MoR, SaaS developers would need to:

  1. Register for tax collection in multiple jurisdictions
  2. Calculate correct tax rates for each customer location
  3. File tax returns in each jurisdiction
  4. Maintain compliance with changing regulations
  5. Handle tax audits and inquiries

With an MoR, these responsibilities are legally transferred to the MoR provider, who becomes the entity responsible for tax compliance. This transfer is not merely administrative but represents a true legal shift of liability.

Legal Basis for the Shift

The legal basis for this shift stems from the reseller relationship established between the MoR and the developer:

  1. The MoR purchases the right to resell the software from the developer
  2. The MoR then sells the software to the end customer
  3. As the legal seller, the MoR bears the tax collection and remittance obligations
  4. The developer receives wholesale payments that typically don’t trigger the same tax obligations

This arrangement is recognized by tax authorities worldwide, provided the contractual relationship is properly structured and documented.

Comparative Analysis of Major MoR Providers

Feature Comparison Table

Feature Paddle Gumroad LemonSqueezy Fungies.io
Base Fee 5-10% + $0.50 per transaction 3.5% + $0.30 per transaction 5% + $0.50 per transaction 4% + $0.30 per transaction
Subscription Management Advanced Basic Advanced Advanced
Countries Supported 245+ 200+ 200+ 190+
Tax Jurisdictions 200+ 180+ 190+ 170+
Checkout Experience Overlay, Embedded, Hosted Hosted Overlay, Hosted Overlay, Embedded, Hosted
Payment Methods Credit/Debit Cards, PayPal, Apple Pay, Google Pay, Wire Transfer Credit/Debit Cards, PayPal Credit/Debit Cards, PayPal, Apple Pay, Google Pay Credit/Debit Cards, PayPal, Apple Pay, Google Pay
Currencies Supported 25+ 20+ 20+ 15+
API Flexibility Extensive Limited Moderate Extensive
Analytics & Reporting Advanced Basic Advanced Moderate
Fraud Protection Advanced Basic Advanced Advanced with AI
Customer Support 24/7 Limited Business hours 24/7
Ideal For Enterprise SaaS Digital creators Small-medium SaaS Indie developers & AI startups

Provider-Specific Strengths

Paddle

  • Comprehensive enterprise-level solution
  • Extensive API capabilities for custom integrations
  • Advanced subscription management with dunning
  • Strong focus on SaaS-specific features
  • Global payment methods and currencies

Gumroad

  • Simplest setup process
  • Lower fees for higher volume
  • Built-in audience and discovery features
  • Good for one-time digital product sales
  • Community-focused approach

LemonSqueezy

  • Modern, user-friendly interface
  • Strong subscription analytics
  • Competitive pricing structure
  • Growing ecosystem of integrations
  • Excellent developer documentation

Fungies.io

  • Specialized for indie developers and AI startups
  • No hidden fees
  • Beautiful checkout solutions
  • No-code store builder
  • AI-powered fraud detection

Practical Implications for SaaS Developers and Indie Publishers

With MoR vs. Without MoR: Responsibility Comparison

Responsibility With MoR Without MoR (Direct Selling)
Tax Registration MoR handles in all jurisdictions Developer must register in each jurisdiction where sales exceed thresholds
Tax Calculation Automatic by MoR Developer must implement tax calculation logic or use third-party services
Tax Filing Handled by MoR Developer must file in each jurisdiction or hire accountants
Payment Processing Integrated by MoR Developer must integrate payment processors and handle security
Compliance Updates MoR stays current Developer must monitor regulatory changes globally
Fraud Management MoR’s responsibility Developer must implement fraud detection systems
Chargebacks Handled by MoR Developer must respond to and manage disputes
Customer Payment Issues First-line support by MoR Developer handles all payment support
International Expansion Immediate with existing MoR Requires research and setup for each new market
Legal Liability MoR assumes primary liability Developer bears full liability

Resource Requirements Comparison

Human Resources Needed

Role With MoR Without MoR
Tax Specialists Not required 1-3 FTEs or external consultants
Compliance Officers Not required 1 FTE or external consultant
Payment Operations Minimal 1-2 FTEs
Financial Analysts Minimal 1 FTE
International Tax Consultants Not required External consultants per region

Time Investment (Monthly)

Activity With MoR Without MoR
Tax Compliance 0-2 hours 20-40 hours
Payment Reconciliation 1-2 hours 10-20 hours
Regulatory Updates 0 hours 5-10 hours
Customer Payment Support 1-5 hours 10-30 hours
Financial Reporting 1-3 hours 10-20 hours

Cost Implications

Direct Costs

Cost Category With MoR Without MoR
Service Fees 3.5-10% of revenue 1-3% payment processing fees
Tax Registration Included $500-$5,000 per jurisdiction
Tax Filing Included $200-$1,000 per filing per jurisdiction
Compliance Software Included $200-$1,000 monthly
Payment Infrastructure Included $100-$500 monthly + setup costs

Indirect Costs

Cost Category With MoR Without MoR
Compliance Risk Minimal High (potential for fines)
Opportunity Cost Low (focus on product) High (resources diverted from core business)
Scaling Friction Low High (each new market adds complexity)
Time to Market Fast Delayed by compliance setup

Real-World Implementation for Different Business Sizes

Solo Developers and Micro-SaaS

For individual developers or very small teams (1-3 people), the MoR model offers significant advantages:

  • Immediate Global Reach: Sell worldwide from day one without tax registration concerns
  • Focus on Product: Dedicate limited resources to product development rather than compliance
  • Predictable Costs: Service fees are proportional to revenue, avoiding large upfront compliance investments
  • Reduced Complexity: Simplified financial operations with consolidated reporting

Recommended MoR Providers: LemonSqueezy or Fungies.io for their indie-friendly pricing and simplicity

Small SaaS Teams (4-20 employees)

Small teams benefit from the MoR model through:

  • Scalable Operations: Grow without proportionally increasing compliance workload
  • Market Expansion: Enter new markets without additional compliance research
  • Resource Allocation: Keep the team focused on product and customer acquisition
  • Risk Mitigation: Reduce exposure to compliance errors during growth phases

Recommended MoR Providers: Paddle or LemonSqueezy for their balance of features and pricing

Medium to Large SaaS Companies

Even larger companies can benefit from the MoR model:

  • Compliance Outsourcing: Delegate specialized tax knowledge to experts
  • Operational Efficiency: Streamline financial operations across multiple products
  • Risk Management: Transfer compliance liability to a specialized partner
  • Focus on Core Competencies: Maintain organizational focus on product innovation

Recommended MoR Providers: Paddle for its enterprise features and global reach

Case Studies: MoR Impact on SaaS Businesses

Case Study 1: TypingMind (AI Startup)

Challenge: Managing sales tax was a “constant headache” and “complicated and intimidating task” for this AI startup.

Solution: Switched to LemonSqueezy as their MoR provider.

Results:

  • Eliminated all tax compliance concerns
  • Increased MRR by 1300%
  • Generated $200,000 in revenue within 4 months of switching
  • Founder could focus entirely on product development and marketing

Case Study 2: Anonymous SaaS Company (50 employees)

Challenge: Expanding internationally triggered tax registration requirements in multiple countries.

Solution: Adopted Paddle as their MoR.

Results:

  • Avoided establishing legal entities in 12 countries
  • Saved approximately $500,000 in compliance costs
  • Accelerated international expansion timeline by 18 months
  • Reduced finance team requirements by 3 FTEs

Case Study 3: Solo Developer with Educational Software

Challenge: Received notice of tax non-compliance from three US states and faced potential penalties.

Solution: Migrated to Fungies.io as MoR.

Results:

  • Resolved compliance issues immediately
  • Expanded sales to 30+ countries without additional compliance work
  • Maintained lean operation with zero compliance staff
  • Focused 100% of development time on product improvements

Limitations and Considerations of the MoR Model

Potential Drawbacks

  1. Cost: The percentage-based fees can become significant at higher revenue levels
  2. Brand Control: The MoR appears as the merchant on customer credit card statements
  3. Integration Complexity: Some customization limitations compared to direct selling
  4. Dependency: Business operations rely on the MoR’s systems and stability
  5. Data Access: Some customer payment data remains with the MoR

When MoR May Not Be Ideal

  1. Very High Volume/Low Margin: When transaction fees significantly impact profitability
  2. Highly Customized Checkout: When unique payment flows cannot be accommodated
  3. Specific Payment Methods: When required payment options aren’t supported by MoRs
  4. Regulatory Requirements: When specific industries require direct merchant relationships

Sources

  1. Paddle – “What is a merchant of record (MoR) + why use one for payments and sales tax?” (August 1, 2024)
  2. SubscriptionFlow – “Understanding the Importance of a Merchant of Record for Digital Products” (April 1, 2024)
  3. Fungies.io – “The Vital Role of Sales Tax Compliance in SaaS Business Success” (September 17, 2024)
  4. LemonSqueezy – “Everything you need to know about a Merchant of Record vs a Seller of Record” (January 26, 2024)
  5. Cleverbridge – “What is a Merchant of Record (MoR)?” (March 12, 2024)
  6. FastSpring – “What Is a Merchant of Record? (And Why Should You Care?)” (September 24, 2024)
  7. PayPro Global – “Merchant of Record Compliance: Regulations, Tax, and Fees” (December 11, 2023)
  8. The Payments Association – “Understanding the merchant of record model: A key to simplified global payments” (November 11, 2024)
  9. CheckoutPage – “What is a Merchant of Record (MoR)? (And do I really need one?)” (January 24, 2025)
  10. Easy.tools – “Merchant of Record – Is it always the best choice?” (January 30, 2025)


user image - fungies.io

 

Duke Vu is the CEO & Co-Founder of Fungies.io, a fintech company headquartered in Warsaw, Poland, that operates as a Merchant of Record for SaaS businesses and digital product sellers worldwide. Fungies takes on full legal and tax liability for global transactions — handling VAT/GST collection, remittance, fraud prevention, chargebacks, and compliance across 100+ countries — so that developers can sell globally without hiring a tax lawyer. With over 5 years of experience building payment infrastructure and digital commerce tools, Duke has helped thousands of software companies and indie creators set up compliant, high-converting checkout experiences. Prior to Fungies, Duke co-founded SV Solutions LLC and has been an active builder at the intersection of payments, developer tooling, and fintech. He is a frequent speaker at developer and payments conferences, and is passionate about removing the friction between great software and global revenue. 📍 Warsaw, Poland | 🔗 linkedin.com/in/duke-vu-h/

Post a comment

Your email address will not be published. Required fields are marked *