Paddle vs Lemon Squeezy for Developer SaaS: Real Fees and MoR Traps Tested

You've built a SaaS product, you want to sell it globally, and you really don't want to register for VAT in 40 countries. A Merchant of Record (MoR) platform sounds like the answer — until you read the fine print and realize the fee structure could quietly eat 10–15% of every transaction you make.

Paddle and Lemon Squeezy are the two most talked-about MoR options in the indie developer space right now. Both promise to handle tax compliance, chargebacks, and global payments. But they're built for different stages, have meaningfully different fees, and each has traps that aren't obvious until you're already processing real revenue.

What a Merchant of Record Actually Does (and Why It Matters)

When a platform acts as your Merchant of Record, it legally becomes the seller of your product. The customer's invoice comes from Paddle or Lemon Squeezy — not from you. That single fact is why developers reach for these platforms: the MoR collects tax, remits it to the relevant authorities in each country, and absorbs the liability for getting it wrong.

Without an MoR, selling software to EU customers means you're responsible for collecting and remitting VAT yourself. For US customers, digital goods have varying state-level sales tax rules. Doing this yourself is a real compliance burden — and getting it wrong is expensive. An MoR turns a tax accounting problem into a platform fee.

The tradeoff is that you give up direct control over the payment relationship, and you pay a cut of every sale. How big that cut is — and what you give up beyond money — is exactly what this article breaks down.

What You'll Learn

• How Paddle and Lemon Squeezy structure their fees and what triggers higher rates
• What the MoR model actually covers and where gaps exist
• Developer experience differences: APIs, webhooks, and checkout customization
• The real gotchas that bite developers after they've launched
• Which platform fits which stage of a SaaS business

Paddle: The Established Player

Paddle has been operating since 2012 and has processed payments for tens of thousands of software businesses. In 2023, Paddle acquired ProfitWell and integrated subscription analytics directly into its dashboard. That acquisition tells you something about who Paddle is targeting: companies with meaningful recurring revenue that want billing, analytics, and compliance in one place.

Paddle offers two products: Paddle Billing (the modern API-first product) and the legacy Paddle Classic (older overlay checkout model, still widely in use). If you're starting fresh, you want Paddle Billing. The two are not interchangeable, and documentation for Classic still clutters search results, which can confuse setup.

Paddle's Fee Structure

Paddle Billing charges 5% + $0.50 per transaction on their standard plan. There's no monthly platform fee. For a $29/month subscription, that's $1.45 + $0.50 = $1.95 taken per renewal, or about 6.7% effective rate. At $99/month it drops to roughly 5.5%. The $0.50 fixed component hurts on low-ticket items significantly.

Paddle does offer custom pricing for businesses processing higher volumes, but you need to be doing serious revenue before that conversation starts. There's no published threshold, and smaller indie developers generally don't qualify.

Lemon Squeezy: The Developer-First Challenger

Lemon Squeezy launched in 2021 and was acquired by Stripe in 2023 — a fact that matters for long-term confidence in the platform. It's visually polished, the onboarding is smooth, and the developer documentation is notably clean. It positions itself squarely at indie hackers, solo founders, and small dev teams.

One thing Lemon Squeezy does differently from day one: everything is API-first. You can sell digital products, SaaS subscriptions, and software licenses all through a single consistent interface. The product catalog model (where each product has variants, prices, and checkout links) is intuitive enough that many developers can go from signup to a working checkout link in under an hour.

Lemon Squeezy's Fee Structure

Lemon Squeezy charges 5% + $0.50 per transaction on their standard plan — identical to Paddle Billing at face value. They also offer a Lemon Squeezy Plus plan at $49/month, which reduces the transaction fee to 3.5% + $0.30. If you're processing more than roughly $3,300/month, the Plus plan pays for itself.

Here's the math at $5,000 MRR:

• Standard plan (assume 50 transactions at average $100): 5% of $5,000 = $250, plus 50 × $0.50 = $25. Total: $275.
• Plus plan: 3.5% of $5,000 = $175, plus 50 × $0.30 = $15, plus $49 plan fee. Total: $239.

The Plus plan saves you $36/month at $5k MRR and the gap widens fast as volume grows.

Fee Structures Side by Side

The payout schedule difference is real. Paddle's configurable payouts (which can be weekly) matter a lot for cash flow if you're bootstrapped. Lemon Squeezy's net-30 monthly cycle means you might wait up to 60 days to see revenue from early-month sales. This is one area where Paddle has a genuine edge for operators who care about tight cash flow at the indie developer stage.

Tax Compliance: Where the Real Value Hides

Both platforms cover the full MoR tax surface: EU VAT (including OSS), UK VAT, Australian GST, Canadian GST/HST, and US state sales tax. Neither requires you to register anywhere yourself. That's the baseline and both deliver it reliably.

Where they diverge is in the details. Paddle has been doing this longer, which means edge cases — Canadian provincial tax, Indian GST rules, Brazilian digital services tax — are more thoroughly handled. Lemon Squeezy covers the major jurisdictions well but is still catching up on less common ones. For a product selling primarily to North America, Europe, and Australia, both are sufficient. For serious global reach into Asia-Pacific and Latin America, Paddle has more coverage today.

One MoR trap to know: chargebacks and refunds are handled by the platform, not you. This is mostly a benefit, but it means you don't have direct control over refund policy enforcement. If a customer disputes a charge to their bank, the platform handles the dispute process. Lemon Squeezy's chargeback defense has been anecdotally weaker than Paddle's in community discussions, though neither platform publishes win rates publicly.

Checkout and Buyer Experience

Lemon Squeezy's checkout is genuinely attractive. The default overlay checkout looks modern, handles localized pricing, and converts well. You can customize colors and add your logo without writing code. For a simple subscription or one-time product, you can share a checkout link with zero backend work.

Paddle Billing's checkout is also overlay-based and similarly polished, but customization requires more configuration. Paddle does offer more sophisticated pricing model support: usage-based billing, per-seat pricing, and trial logic are all first-class features. If your SaaS has a complex billing model, Paddle's infrastructure handles it more flexibly.

Both platforms support multiple currencies, though the currency shown to the buyer depends on their location. Neither lets you explicitly set prices in every currency independently on the standard plans — they use dynamic conversion based on a base price you set.

Developer Experience and API Quality

Lemon Squeezy's API is clean and well-documented with a JSON:API response format. Webhooks fire reliably, the event payload is predictable, and the SDK for JavaScript/TypeScript is actively maintained. The developer experience clearly had intentional design put into it. If you're building a custom onboarding flow or sync-ing subscription state to your own database, the webhook events you need are all there.

Paddle Billing's API is more powerful but has a steeper learning curve. The pricing structure (price entities attached to product entities, discount objects, subscription items) requires understanding Paddle's data model before it clicks. Once it does, it's flexible — but initial integration takes longer than Lemon Squeezy. Paddle's official SDKs cover PHP, Node, Python, Go, and .NET.

A practical integration pattern for either platform looks like this: listen for subscription webhooks, update your user's plan in your database, and gate features accordingly.

// Example: Lemon Squeezy webhook handler (Express)
app.post('/webhooks/lemonsqueezy', express.raw({ type: 'application/json' }), (req, res) => {
  const signature = req.headers['x-signature'];
  // Verify HMAC signature before processing
  if (!verifySignature(req.body, signature, process.env.LS_WEBHOOK_SECRET)) {
    return res.status(401).send('Invalid signature');
  }

  const payload = JSON.parse(req.body);
  const eventName = payload.meta.event_name;

  if (eventName === 'subscription_created' || eventName === 'subscription_updated') {
    const customerId = payload.meta.custom_data?.user_id;
    const status = payload.data.attributes.status;
    // Update your DB: set user plan based on status
    updateUserSubscription(customerId, status);
  }

  res.sendStatus(200);
});

One thing to know about Lemon Squeezy specifically: custom_data passed at checkout is your main mechanism for linking a Lemon Squeezy customer to your own user record. If you don't pass a user identifier at checkout time, reconciling who paid for what becomes a manual headache. This is a known gotcha that catches developers early on.

This kind of integration consideration is similar to the authentication decisions you face when picking a provider — just as with choosing monitoring tools, the real cost often shows up post-integration, not in the initial signup.

Common Pitfalls and MoR Traps

You Don't Own the Customer Relationship

This is the most important structural fact about MoR platforms. The customer's payment method is stored with Paddle or Lemon Squeezy, not with you. If you ever want to migrate away, you cannot port payment credentials. You'd need to ask every active subscriber to re-enter their card on a new platform. For a product with hundreds of subscribers, that migration is painful and will cause significant churn.

Lemon Squeezy's Payout Delay

The net-30 monthly payout cycle is easy to overlook during evaluation. If you launch on December 1st and have a great first month, you see that money in early February. For a bootstrapped product where runway matters, plan your cash flow model around this delay before you commit. The same goes for refunds — they come out of future payouts, not immediately reimbursed.

Paddle's Entity Lock-In

Paddle's data model creates entities (subscriptions, discounts, customers) that are opaque to your own system unless you sync them. If your database gets out of sync with Paddle's state — say, a webhook is missed — debugging requires cross-referencing two systems. Building a robust webhook retry and idempotency layer is not optional; it's required for production reliability.

Both Platforms Review Products

Because the MoR absorbs legal liability, both Paddle and Lemon Squeezy review products before approving them for sale. Lemon Squeezy has been known to decline products that are borderline in their terms — certain types of AI tools, content generators, and adult-adjacent software have been rejected. Paddle is generally more permissive but also reviews anything that looks unusual. Build your approval process into your launch timeline.

Currency Exposure on Lower Plans

If your customers pay in EUR or GBP and your payout currency is USD (especially on Lemon Squeezy), there's currency conversion happening at the platform's rate, not yours. In periods of high exchange rate volatility, this can quietly erode effective revenue. Paddle's multi-currency payout option mitigates this for higher-volume sellers.

These kinds of structural traps are worth comparing across the tools you use to run your business — similar dynamics show up when picking services like hosting platforms with tiered pricing that look cheap until you hit a wall.

Wrapping Up: Which One Should You Pick?

Both platforms are legitimate and both solve the core MoR problem well. The decision comes down to your current stage and what you're optimizing for.

Choose Lemon Squeezy if: you're a solo developer or early-stage indie hacker, you want the fastest path from idea to working checkout, and your revenue is under $5k/month where the Plus plan math doesn't yet dominate. The DX is genuinely excellent and you'll be up and running faster.

Choose Paddle if: you have complex pricing requirements (usage-based, per-seat, enterprise tiers), you need faster and more flexible payouts, or you're planning to grow to a scale where migration would be costly. Paddle's infrastructure has more headroom.

Here are the concrete next steps based on where you are:

1. Under $1k MRR: Start with Lemon Squeezy Standard. Zero platform cost, fast onboarding, good enough for most early SaaS products. Store your user_id in custom_data from day one.
2. $1k–$10k MRR: Evaluate whether Lemon Squeezy Plus pays off yet with your transaction count. Also reassess if payout timing is causing cash flow friction — if it is, Paddle becomes more attractive.
3. $10k+ MRR: Seriously model the fee difference and contact Paddle about custom pricing. The migration cost from Lemon Squeezy (re-collecting payment methods) is real, so don't wait until you're at $50k MRR to make this decision.
4. Complex billing model: Go to Paddle Billing from the start. Trying to retrofit usage-based billing onto Lemon Squeezy's product model is friction you don't want mid-growth.
5. Either platform: Build webhook handling with idempotency keys, verify every signature, and test your subscription lifecycle end-to-end in sandbox mode before going live. The bugs you catch there are free; the ones you catch in production cost you subscribers.

If you're also evaluating the full cost of your developer tooling stack, it's worth working through similar comparisons for other services — the pattern of "cheap until you grow" appears across hosting and infrastructure too, and modeling the full picture early saves you migrations later.