When Stripe acquired Lemon Squeezy in July 2024, Patrick Collison mentioned the need to "scale up Merchant of Record sales."

On January 28, 2026, JR Farr, co-founder of Lemon Squeezy, publicly wrote: the team is participating in building Stripe Managed Payments and hopes to make it easy for existing Lemon Squeezy users to migrate.

Starting April 6 of the same year, the legal seller entity for Managed Payments changed from LemonSqueezy LLC to Sold through Link, LLC.

Stripe's official explanation states that this is an entity change of the same underlying MoR service, which does not affect transactions or pricing.

At this point, things are clear.

The core reason for Stripe's acquisition of Lemon Squeezy is not to operate two unrelated MoRs long-term, but to bring in the team, product experience, and operational capabilities, and then make MoR a native capability on its own platform.

The Lemon Squeezy brand still exists, but the underlying structure is shifting towards Managed Payments.

Why does Stripe choose to push itself from payment infrastructure to "global commercialization infrastructure" through acquisition?

Two Entry Points, but Different Purposes

Lemon Squeezy and Stripe Managed Payments indeed coexist now, but they serve different customer entry points.

Lemon Squeezy starts from the sales tools for developers.

A small team of three developed an AI video tool, lacking both a tax team and dedicated payment engineers. They need a solution that can be launched quickly: create products, set prices, manage subscriptions, issue licenses, handle taxes, and collect payments. Payment is just one part of this sales system. Such customers have a higher requirement for "out-of-the-box" solutions than familiarity with the underlying payment systems, allowing Lemon Squeezy to reach independent developers and small teams who have not deeply used Stripe.

Stripe Managed Payments takes a different path. It serves businesses that are already using Stripe Payments, Checkout, or Billing. These businesses do not need to purchase a new software sales platform; they simply want to offload indirect taxes, fraud, dispute resolution, and transaction-level customer service to MoR in certain markets or transactions. Stripe allows enabling services on a transaction, market, or product basis rather than mandating that all sales be processed through MoR. Businesses continue to assume seller responsibility domestically while enabling Managed Payments for certain digital product transactions in Europe—a hybrid model that significantly lowers switching costs for companies already embedded in the Stripe ecosystem.

The former addresses the customer acquisition entry, while the latter resolves upgrades within the ecosystem.

This is the observable arrangement at present.

However, based on the migration direction disclosed by Lemon Squeezy itself, in the long term, the underlying capabilities will continue to integrate into the Stripe platform rather than maintain two independent MoR infrastructures permanently. Whether the brand continues to exist independently is another matter.

Why Sold through Link, instead of having Stripe act as the legal seller directly?

This is currently the detail that is easiest to overlook and most worthy of further observation.

In Managed Payments transactions, consumers see "Sold through Link."

Checkout, receipts, order management, subscription management, and after-sales support are all conducted through Link.

The card statement descriptor is LINK.COM* [Merchant defined description]. Link is not just a wallet for speeding up checkout; in these transactions, it also serves as the interface between consumers and MoR.

Why not use Stripe Payments as the legal seller directly? One practical effect is the isolation of risk and brand.

Sold through Link, LLC is the legal entity providing MoR services, while other Stripe fees are collected by local Stripe entities, with separate billing.

For merchants, the legal seller is an entity under the Link system, not their own company;

for consumers, what appears on the bill is Link, not an unfamiliar merchant name.

This reduces the probability of disputes from “not recognizing this charge” and consolidates transaction-level customer service to Link support.

But the boundaries of responsibility must be clear.

MoR bears the responsibility for card organization dispute resolution, which does not automatically equate to merchants being completely financially exempt. Principal, fees, fraud losses, and recovery arrangements still depend on specific terms.

During refunds, in certain jurisdictions, Stripe still needs to retain and pay taxes, and the merchant's account balance will decrease accordingly.

Merchants may still be involved in issues related to product defects, contractual responsibilities, and partial refund decisions. These details impact actual costs more than simply looking at "who is the legal seller."

Strategically, Link gains a cross-merchant consumer interaction entry here.

If more digital product subscriptions, refunds, and customer service increasingly flow through Link in the future, Stripe would hold both the merchant-side payment relationships and the consumer-side account relationships. This is an observable product design direction, while whether Link will further become a stronger consumer relationship platform is still speculative.

A specific number: an AI SaaS with $10 million in annual revenue

Beyond Strategic Analysis, Merchants Really Care About Money.

Let's look at a simplified example.

Assume an American AI SaaS company with annual revenue of $10 million, primarily selling subscriptions, with an average order value of $100, where 60% of sales are domestic and 40% international. We will only compare payment processing + MoR related fees, not considering gross profit margin differences of subscription products, nor the labor costs of an internal tax team (which varies greatly and can only be qualitatively assessed).

Pure Stripe Payments (acting as the seller): Approximately 2.9% + $0.30 for domestic cards, plus an additional 1.5% for international cards, possibly with a 1% currency conversion fee. Businesses need to handle indirect tax compliance (registration, declaration, payment) themselves, as well as disputes and customer service. The rates are the lowest, but compliance and operational costs are borne by the business. For companies with tens of millions in annual revenue and a significant proportion of overseas sales, the fixed costs of tax compliance are often non-negligible.

Lemon Squeezy: Base 5% + $0.50, with potential additional fees for subscriptions of 0.5%, international transactions of 1.5%, etc. MoR handles taxes, disputes, and some customer service. The rates are significantly higher than pure payments, but it offloads the responsibility for global indirect taxes and transaction operations. This is very attractive for small teams, while for companies with established payment and finance teams, the additional rates need to be offset by savings in compliance costs.

Stripe Managed Payments: Standard Stripe payment fee + 3.5%. The effective fee rate for domestic card transactions is around 6.4% + $0.30 (specifics depend on whether taxes are included). It allows for mixed use—only enabling for certain overseas markets while continuing with standard Stripe for domestic. This way, businesses do not have to shift their entire collection structure, only paying an additional 3.5% where MoR is needed. For companies already deeply integrated with Stripe, this is the lowest-switching cost MoR option.

In calculation, if 40% of revenue from overseas goes through Managed Payments while domestic continues with standard Stripe, the overall fee rates may be more controllable than using all of Lemon Squeezy or Paddle, while still outsourcing high compliance-cost markets. However, 3.5% is not pure profit; there are costs for tax declaration, dispute resolution, and customer service. For merchants, the real calculation is whether the additional fees can cover the tax compliance, chargeback losses, and customer service labor they would originally have to bear. If the proportion of overseas income is high, tax registration is complicated, and the dispute rate is not low, the overall costs of using MoR could be lower; if primarily domestic with low dispute rates and already having a tax team, purely paying for services often makes more financial sense.

This calculation does not have a single answer, but at least it illustrates that the value of Managed Payments does not lie in being "cheaper than Lemon Squeezy," but rather in allowing companies already using Stripe to enable MoR as needed and by market, without migrating platforms.

What It Means for Other MoRs

For Paddle, competition is no longer just about functional comparison. Stripe can now allow existing customers to open MoR directly in a familiar payment system, thereby reducing technical switching costs. Paddle's advantages still lie in more mature software sales tools and depth in specific markets, but customers who "are already using Stripe and do not want to adopt a new system" may be drawn away by Managed Payments.

For players like Polar, Creem, and Dodo, which focus more on developer experiences, differentiation will continue to concentrate on access policies, risk tolerance, support for specific categories, price transparency, and responsiveness. Stripe's product access and checkout customization have clear limitations; not all digital products and all countries can use Managed Payments.

Stripe itself is not leading in all dimensions. MoR is not an all-powerful exemption; the boundaries of responsibility and recovery terms need to be examined individually.

For AI export enterprises, the real dividing line is not "who is MoR," but rather: who bears the tax, dispute, and customer service responsibilities behind this transaction, to what extent, and how money is settled when problems arise.

Long-term Direction

Over the past decade, Stripe has made the process of "collecting money" for global businesses simple enough. Now it wants to simplify the process of "selling things globally" as well. The acquisition of Lemon Squeezy is not to maintain another MoR company, but to thoroughly learn how to help developers sell software and then embed that into its core payment system. Sold through Link pushes this relationship further—legal seller, billing descriptions, subscription management, and transaction customer service are all starting to appear on the consumer side. When the tax, dispute, and customer service responsibilities of a transaction no longer rest solely on the merchant, the revenue logic of payment companies will extend from "processing fees" to "sales responsibility fees." This is not simply a matter of rates increasing by 3.5%. It means the role of the legal seller is starting to be repriced. Who has the qualification to stand in the middle of the transaction, bear more, and earn more will determine who truly holds the infrastructure of digital commerce in the next phase.

免责声明：本文章仅代表作者个人观点，不代表本平台的立场和观点。本文章仅供信息分享，不构成对任何人的任何投资建议。用户与作者之间的任何争议，与本平台无关。如网页中刊载的文章或图片涉及侵权，请提供相关的权利证明和身份证明发送邮件到[email protected]，本平台相关工作人员将会进行核查。