Lemon Squeezy is shutting down. Here's what it means for your store and what to do this week.
Updated November 2026 · Lemon Squeezy stops processing payments March 31, 2027
Lemon Squeezy is winding down. Stripe bought it in 2024 and is folding it into Stripe Managed Payments, its own merchant-of-record product. New store sign-ups closed on November 16, 2026. Payment processing stops on March 31, 2027.
If you sell anything through Lemon Squeezy (a SaaS subscription, a Notion template, an ebook, a WordPress plugin, a desktop app), you need to be live on a different provider before that date. This page covers what actually happens, what breaks, and the order to do things in so you don't lose revenue in the switch.
The timeline
| Date | What happens |
|---|---|
| 2024 | Stripe acquires Lemon Squeezy |
| November 16, 2026 | New store sign-ups close. Lemon Squeezy announces the wind-down |
| Now → March 2027 | Existing stores keep selling. Lemon Squeezy contacts each business with next steps |
| March 31, 2027 | Payment processing stops. Checkouts and renewals fail after this |
Lemon Squeezy says it is reaching out to every business individually. Read that email properly, especially anything about exporting data and moving payment methods. Those two details decide how hard your migration is.
What actually breaks on March 31
Most founders think of the migration as "move my products somewhere else". Products are the easy part. Here's everything attached to them:
- Checkout. Every "Buy" button, checkout link and overlay on your site points at Lemon Squeezy. They stop taking money.
- Subscription renewals. This is the expensive one. Renewals that would have happened in April just don't, and many founders won't notice for weeks.
- License keys. If your app checks keys against the Lemon Squeezy license API, every install of your app is calling an endpoint that goes away.
- Webhooks. Your app probably grants access on
order_createdorsubscription_createdand removes it onsubscription_expired. Those events stop arriving. - Customer portal. The "manage subscription" and "update card" links your customers use stop working.
- Affiliates. The built-in affiliate program doesn't come with you. Affiliates stop earning the day checkout moves.
- Tax. Lemon Squeezy was your merchant of record and handled VAT and sales tax. Whatever you move to has to keep doing that, or you take on the tax registration yourself.
Your options
You have two broad choices.
Stripe Managed Payments. This is the path Lemon Squeezy is steering everyone toward. Stripe acts as merchant of record, so tax stays handled. For a lot of SaaS businesses it's the least-friction choice, especially if you may want the rest of Stripe later. Check that it supports your seller country and product type before you commit. The announcement already mentions sellers outside supported countries running into problems.
Another merchant of record. Paddle, Polar, Dodo Payments and Creem all do the same core job as Lemon Squeezy. They differ on country coverage, license keys, affiliates, fees and how much they suit SaaS vs digital downloads. We compare them in detail in Lemon Squeezy alternatives.
The wrong reason to pick a provider is "it's the one I saw on Twitter today". The right reasons are: it pays out to your country, it supports what you sell (subscriptions, license keys, downloads, usage billing), and you can move your existing customers onto it without making them all re-enter a card.
What to do this week
You have months, not days. But the work that takes longest is waiting on other people (provider approvals, payment-data transfers, app store reviews for an update), so start those now.
1. Export everything
Before anything else, pull a complete copy of your store: products, variants, prices, customers, subscriptions (with next billing dates), orders, license keys (with activation counts), discount codes and affiliates. Do it through the API, not just the dashboard CSVs, because the API gives you the IDs and relationships you'll need for mapping. We wrote a full export guide with code.
2. Count what's at stake
Open your export and answer three questions:
- How many active subscriptions do you have, and what monthly revenue do they carry?
- How many license keys are activated in the wild?
- How many affiliates sent you a sale in the last 90 days?
If all three are near zero, your migration is mostly a catalog rebuild and a weekend of work. If any of them is large, that's where the risk is, and where planning pays for itself.
3. Pick your destination
Shortlist two providers. Check seller-country support, payout methods, the features you rely on, and whether they'll accept a payment-method transfer. Apply early, because some providers review your domain and products before they approve you.
4. Ask about moving payment methods
This is the question that decides your churn. Lemon Squeezy is the merchant of record, so your subscribers' cards are stored under its account. If those cards can be moved to your new provider (through a PCI-compliant data transfer), subscribers carry on paying and never notice. If they can't, every subscriber has to re-enter a card, and some won't. Ask Lemon Squeezy support and your new provider now. More on this in migrating subscriptions.
5. Set a cutover date well before March 31
Pick a date in January or February 2027. That leaves time to find what breaks, ship an app update for license keys, give re-subscribing customers more than one reminder, and still have slack. Leaving it to the last week of March is how founders end up with a weekend of failed renewals and no time to fix them.
A realistic sense of effort
| Your store | Rough effort |
|---|---|
| One-time digital products, no license keys | 1–3 days |
| SaaS with a few dozen subscribers | 1–2 weeks |
| SaaS with hundreds of subscribers, license keys or affiliates | 2–6 weeks including a staged cutover |
The calendar time is mostly waiting and testing, not typing.
Common mistakes we're already seeing
- Rebuilding products but forgetting grandfathered prices. Early customers on old prices suddenly get charged the new price on the new provider.
- Cancelling Lemon Squeezy subscriptions before the replacement exists. Customers lose access, then email you angry.
- Switching webhooks in one go. Run old and new handlers side by side during cutover so access is never wrongly revoked.
- Not shipping an app update for license keys in time. Desktop and plugin users on old builds get locked out.
- Emailing customers from a payment provider instead of from you. It reads like a phishing attempt and kills re-subscribe rates.
Bottom line
Lemon Squeezy isn't going away tomorrow, but every week you wait shortens the time you have for the parts that need other people: approvals, payment-data transfers, app updates and reminder emails. Export your data this week, pick a destination this month, and plan to cut over in early 2027.
Don't want to do this yourself? We'll do the whole migration at a fixed price.
Questions
When does Lemon Squeezy stop processing payments?+−
March 31, 2027. New store sign-ups already closed on November 16, 2026.
Will my Lemon Squeezy subscriptions keep renewing until then?+−
Yes, existing stores keep processing until the shutdown date. Renewals after March 31, 2027 won't be collected unless the subscription has moved to another provider.
Why is Lemon Squeezy shutting down?+−
Stripe acquired Lemon Squeezy in 2024 and is consolidating into a single product, Stripe Managed Payments, rather than running two merchant-of-record platforms.
Do I have to move to Stripe?+−
No. Stripe Managed Payments is the official path, but Paddle, Polar, Dodo Payments and Creem are also merchants of record and can replace Lemon Squeezy.
What happens to my license keys?+−
Apps that validate against the Lemon Squeezy license API will stop validating after shutdown. You need to move keys to a new system and ship an app update before the deadline.