Lemon Squeezy became part of Stripe in July 2024

The workload

An acquisition of a merchant-of-record platform by a payments company changes what a founder is actually buying when they sign up: the entity processing sales, filing tax, and standing behind chargebacks is no longer independent. Verified: Lemon Squeezy's own announcement, published 26 July 2024 and retrieved 16 September 2026, states that Stripe acquired Lemon Squeezy and notes that Lemon Squeezy had processed its own payments on Stripe's infrastructure since its founding, meaning the two companies had an existing technical relationship before the deal.

What the documents show

Verified: the announcement states the acquisition closed in 2024, frames the deal in terms of shared mission and customer values rather than financial rationale, and does not disclose a purchase price or other deal terms; no figure is stated, and none should be assumed. The announcement is a self-reported account by the acquired party, published on its own blog rather than an independent filing, and it promises continuity of product and reliability. A follow-up document, Lemon Squeezy's update on the integration, published 29 April 2025 and retrieved 16 September 2026, states that Stripe Managed Payments, a merchant-of-record product built directly into Stripe, was announced for private preview beginning summer 2025, with self-serve tools to follow later that year. That second document is the clearest evidence of what changed operationally in the nine months after the announcement, beyond the ownership statement itself.

The operating cost

Neither document states an acquisition price, so no dollar figure can be reported here; the announcement limits itself to describing continuity of product and team rather than transaction economics. What can be stated is a structural cost to founders already using Lemon Squeezy: continued reliance on the platform now depends on Stripe's own product roadmap and pricing decisions for its merchant-of-record line, not on an independent company answerable to Lemon Squeezy customers alone. This is an editorial observation about dependency risk rather than a claim either document makes directly.

The stop condition

The documents name no expiration for the transition; the 2025 update states self-serve tools for Stripe Managed Payments would arrive later in 2025 without a specific date, and existing users were told no immediate action was required. Editorially, the point to revisit is whenever Stripe formally sunsets the standalone Lemon Squeezy product or merges its fee schedule into Stripe's own, since neither document commits to keeping the two priced or branded separately indefinitely.

• Has Stripe Managed Payments reached general availability, and on what terms relative to the Lemon Squeezy fee described elsewhere on this site?
• What operational commitments, if any, has Stripe made about keeping Lemon Squeezy separately branded?
• Does relying on an acquired subsidiary's merchant-of-record status carry different risk than relying on Stripe's own tax product directly?

The acquisition itself is well documented by the parties involved; what it means for a specific founder's fee and continuity depends on product decisions that neither the 2024 nor the 2025 document fully resolves.