LemonSqueezy Merchant of Record: Official Guide

A merchant of record is the legal entity that appears on your customer's bank statement and holds responsibility for the transaction under law. When LemonSqueezy is your MoR, LemonSqueezy is the seller. You are the supplier.

This distinction does real legal work. Tax authorities in Germany, Australia, Canada, and 130-plus other jurisdictions require the seller to register, collect, and remit the correct consumption tax on digital products. If you sell directly as a SaaS founder without an MoR, that registration burden falls on you, individually, in each jurisdiction where you have economic nexus.

LemonSqueezy absorbs all of it. Sales tax, VAT, GST: calculated at checkout, collected from the customer, and remitted to the relevant authority on your behalf. You never file a return in Ireland or register a GST number in Australia. LemonSqueezy does.

Beyond tax, the MoR role also means LemonSqueezy handles PCI DSS compliance, so cardholder data security is not your problem. LemonSqueezy also manages post-sale disputes and chargebacks, which is legal protection, not just operational convenience.

The trade-off is cost and control. You pay a fixed rate of 5% plus $0.50 per transaction with no monthly fees. And because LemonSqueezy is the legal seller, your brand takes a secondary role on receipts and bank statements. Customers see LemonSqueezy on their statements, not your company name. You must disclose this in your terms of service and update customers accordingly before switching.

The LemonSqueezy merchant of record official scope covers three categories of consumption tax and a layer of compliance infrastructure most founders never think about until they need it.

Sales tax (United States). The US has over 10,000 tax jurisdictions. Economic nexus laws mean a SaaS company can trigger a filing obligation in a state where it has no physical presence, purely based on revenue volume. LemonSqueezy monitors nexus thresholds and remits in every applicable US state automatically.

VAT (Europe and UK). EU VAT on digital services uses the customer's location to determine the rate. A customer in France pays 20%. A customer in Hungary pays 27%. LemonSqueezy applies the correct rate at checkout, collects it, and files under the EU's One Stop Shop (OSS) scheme. The UK, post-Brexit, is handled separately. You do not need a UK VAT registration.

GST (Australia, Canada, New Zealand, and others). Each country has its own digital services GST threshold and remittance cycle. LemonSqueezy covers these, including the distinction between Canadian federal GST and provincial sales taxes.

Two things LemonSqueezy does not cover: income tax and B2B reverse charge VAT complexity in certain edge cases. If a German business buys from you and claims reverse charge, the VAT treatment shifts. LemonSqueezy manages the checkout logic, but confirming the business VAT number is valid is a shared responsibility.

For implementation, product classification matters more than most founders expect. LemonSqueezy uses your product category to determine the correct tax treatment. A 'software subscription' and a 'digital download' can attract different rates in several jurisdictions. Classify incorrectly and the tax collected will be wrong, which creates liability even with an MoR in place.

The published rate is 5% plus $0.50 per transaction. No monthly fee, no setup cost, no per-seat pricing.

At low volumes, that fee structure is a good deal. Consider a SaaS with $5,000 MRR processing 200 transactions per month: total MoR fees run roughly $350. A competent international tax accountant charges more than that per hour. The outsourced compliance is worth multiples of the transaction cost.

The math shifts as you scale. At $500,000 ARR, you are paying roughly $25,000 per year in transaction fees to LemonSqueezy. At that point, building on Stripe directly and contracting a specialized SaaS tax firm starts to make financial sense. Professionals who work in this space consistently recommend re-evaluating the MoR arrangement somewhere between $250,000 and $500,000 ARR.

That said, the $25,000 number is only part of the calculation. Add back the cost of an accountant who handles multi-jurisdiction VAT filings, the engineering time to build and maintain a Stripe Tax integration, and the risk of non-compliance penalties if you miss a filing window. For most early-stage teams, the MoR premium pays for itself.

One practical comparison: LemonSqueezy's 5% plus $0.50 is higher than Stripe's base rate (2.9% plus $0.30 in the US) but lower than many full-service MoR competitors like Paddle, which charges a similar percentage but often includes minimums or additional processing fees depending on geography. The LemonSqueezy rate is clean and predictable, which matters when you are forecasting margins at the seed stage.

Stripe acquired LemonSqueezy in 2024. As of 2026, LemonSqueezy operates as a standalone service, not a Stripe product.

What changed: deeper integration with Stripe Tax and Stripe Billing infrastructure. If you are already running inside the Stripe ecosystem, LemonSqueezy now connects more cleanly. The underlying payment rails are Stripe's.

What did not change: pricing, the merchant of record structure, and the core product experience. You still sign up for LemonSqueezy directly, manage your store in the LemonSqueezy dashboard, and get your payouts from LemonSqueezy.

The more significant change is what Stripe is building. Stripe is currently testing Stripe Managed Payments, their own MoR product, in public preview. If Stripe ships a full MoR solution at competitive rates inside their existing infrastructure, the long-term roadmap for LemonSqueezy as a separate product becomes genuinely uncertain.

For a founder choosing a payment infrastructure in 2026, this creates a real consideration. LemonSqueezy works now, has a proven track record, and handles global compliance reliably. But if you are building for the long term and expect to outgrow the indie SaaS tier, betting on LemonSqueezy's indefinite independence carries some platform risk.

The practical answer: use LemonSqueezy if you are under $500,000 ARR and need to ship fast. Watch the Stripe Managed Payments public preview. Plan a migration path before you hit $1M ARR rather than after.

Also worth knowing: vetting to get approved for a LemonSqueezy account has reportedly tightened since the acquisition. Budget a few days for the application process rather than assuming instant access.

The setup sequence matters. Getting it wrong does not break your checkout, but it can break your tax compliance or create customer confusion.

Step 1: Account approval. Apply at LemonSqueezy and wait for approval. Post-acquisition vetting is more thorough than it was in 2022. Approval times vary.

Step 2: Business details. Enter your legal business name, address, and tax ID. These details populate your customer invoices. If your customers are businesses that need compliant VAT invoices, this step is critical. Wrong details here mean invalid invoices, which means your B2B customers cannot claim input tax credit.

Step 3: Product creation and classification. Use the REST API or the dashboard to create your products. The API call for product creation follows LemonSqueezy's standard JSON:API format:

{
  "data": {
    "type": "products",
    "attributes": {
      "name": "My SaaS Product",
      "slug": "my-saas-product",
      "description": "Professional tool for users."
    }
  }
}

Classify each product correctly. SaaS subscriptions, one-time downloads, and license keys can attract different tax treatment in specific jurisdictions.

Step 4: Terms of service update. You are legally required to disclose that LemonSqueezy is the merchant of record and will appear on customer bank statements. This is not optional. Update your ToS before you take your first transaction.

Step 5: Customer notification if migrating. Moving existing subscriptions from Stripe to LemonSqueezy requires migrating subscription data and notifying customers about the billing entity change. LemonSqueezy supports subscription imports, but the customer communication is your responsibility.

Native features you get without additional setup: license key management, an affiliate system, a hosted no-code checkout, and email receipts with your branding. These are included in the transaction fee.

LemonSqueezy is the right choice for a specific kind of company at a specific stage.

Use it if you are an indie SaaS founder, a small team, or a digital product creator with under $500,000 ARR who needs to sell globally without building compliance infrastructure. A SaaS founder with 500 customers across 30 countries reduced their monthly compliance time from 20 hours to 2 hours by switching to LemonSqueezy, saving roughly $3,000 per month in accounting costs. That is a real before-and-after.

The payment recovery features also deliver measurable results. One SaaS with 2,000 subscribers saw LemonSqueezy's dunning logic retain 6% more customers than their previous platform, adding approximately $5,880 in monthly recurring revenue. When you are under $1M ARR, that kind of retention improvement moves the needle.

Reconsider LemonSqueezy if you are scaling past $500,000 ARR and the 5% fee is becoming a material cost center. At that point, a Stripe-native setup with a tax compliance tool and a SaaS-focused accountant may cost less in total. Also reconsider if you need complex enterprise billing, advanced dunning customization, or highly configurable subscription management. LemonSqueezy is built for simplicity, not for complex contract-based billing.

LemonSqueezy is also not the right tool if you are selling physical goods, services billed by the hour, or any non-digital product. The MoR model is built for digital.

For context on alternatives, the LemonSqueezy Alternatives for SaaS Startups page covers the main options and where they differ. The Stripe vs LemonSqueezy for SaaS Startups comparison breaks down the cost and feature tradeoffs in detail.

LemonSqueezy handles how you collect money. It does not handle how customers find you in the first place.

This is where a lot of technically strong founders stall. They ship, they integrate LemonSqueezy, they have a working checkout, and then they wait for traffic that never comes. The payment infrastructure is solid. The growth infrastructure is empty.

The founders who close that gap fastest are the ones who treat growth as a system, not a series of one-off experiments. SEO, paid ads, A/B testing on landing pages, outbound outreach: none of these are hard in isolation, but running all of them simultaneously while also building the product is not something one person can do well.

Revnu is what the founders in that position reach for. It is an AI-powered growth platform backed by Y Combinator (P26 batch, 2026) that deploys autonomous AI agents across SEO, paid advertising, conversion optimization, and outreach. The SEO Content Agent generates and publishes long-form articles targeting queries your customers actually search for. The Ad Campaign Agents run paid campaigns across Meta, LinkedIn, Reddit, and TikTok, reallocating budget daily based on performance. A/B testing runs continuously against headlines, CTAs, and pricing pages, activated by merging a single GitHub PR.

All of those agents share a single intelligence layer, so when the SEO agent finds a topic gaining traction, the ad creative agent uses it. The system compounds.

Vinta.app, a solo-founder Vinted accounting tool, scaled to $10k MRR primarily through Revnu's autonomous blog and programmatic SEO agent without a content team. Artomate.app hit $5k MRR with consistent 20% month-over-month growth driven by Revnu-generated blog content targeting intent-driven keywords.

If you are using LemonSqueezy to handle the revenue side, Revnu handles the side that gets you to revenue. The two tools run in parallel without overlap.

The official LemonSqueezy documentation covers the MoR model, API reference, and tax compliance in detail. Here is what matters most and where to find it.

Official API documentation. The LemonSqueezy REST API is the primary interface for managing products, customers, subscriptions, and orders programmatically. The API follows JSON:API conventions. All management operations, including creating products, retrieving orders, and updating subscription states, go through this interface.

Tax documentation. LemonSqueezy publishes guidance on which tax regimes they cover, how tax is calculated at checkout, and how to verify that your product classification is correct. Read this before you go live. Misclassified products can result in wrong tax rates being applied, and even with an MoR, that creates downstream issues.

Webhook events. LemonSqueezy fires webhooks for purchases, subscription changes, cancellations, and payment failures. These are the events you use to provision access to your product. Webhook handling is your responsibility as the developer. Build it before launch.

Affiliate and license key systems. These are native to the platform and covered in the official docs. The affiliate system lets you set commission rates and generate trackable links. License key management is built for software products that require activation.

For deeper coverage of the tax and MoR mechanics, the LemonSqueezy MoR Tax and VAT Compliance for SaaS guide covers the technical compliance details. The LemonSqueezy Merchant of Record Explained glossary entry is a good starting point if you are new to the concept.

One practical note: LemonSqueezy's support documentation has improved since the Stripe acquisition, but for specific tax questions in unusual jurisdictions, confirm directly with a tax professional rather than relying solely on platform documentation.