WordPress guide

License-gated WordPress plugin updates after Lemon Squeezy

Lemon Squeezy stops processing on March 31, 2027 (132 days from today). If your premium plugin checks a Lemon Squeezy license before it offers updates, here's how to keep that working on Stripe without asking any site owner to re-enter a key.

What breaks

Every installed copy calls Lemon Squeezy

Most premium plugins sold on Lemon Squeezy activate a key per site and validate it before showing an update, using api.lemonsqueezy.com/v1/licenses/. What happens to that API after the shutdown isn't documented. Plan as if it stops, which means licensed sites stop seeing updates.

The fix is a plugin release that points somewhere else. The hard part is doing it without resetting activations on every customer's sites.

Step by step

Keep updates license-gated, in five steps

  1. 01
    Import keys and site activationsRun the Lemon Squeezy import (dry run first). Keys keep their activation limits and expiry dates, and every activated site keeps its original instance ID, the one your plugin saved in the site's options.
  2. 02
    Change the base URL in your pluginSwap https://api.lemonsqueezy.com/v1/licenses/ for https://rindkey.com/v1/licenses/. Same params, form-encoded like wp_remote_post sends them by default, and the same JSON back. Sites that already activated keep validating with the instance ID they stored.
  3. 03
    Gate updates on validateBefore your update checker offers a new version, call validate with the key and the site's instance ID. Only "valid": true gets the update. An expired key returns valid: false with "This license key is expired.", so yearly update plans stop updating when they lapse, and refunded (disabled) keys stop too.
  4. 04
    Activate and free sitesNew sites call activate with an instance_name such as the site URL; the activation limit is enforced atomically. Call deactivate when the plugin is removed, and customers can free a site themselves in the portal.
  5. 05
    Put the zips where customers can find themUpload each release zip to the product with a version label. Customers download it from their portal through a signed link that expires after 15 minutes. Disabled keys get no download links.
The check

One request in your update checker

Cache the answer (a transient for a few hours works) rather than calling on every page load. Validate responses also carry a signed offline token if you want a grace period when the API can't be reached. See the docs.

// before your updater returns the new version
$res  = wp_remote_post( 'https://rindkey.com/v1/licenses/validate', array(
    'timeout' => 10,
    'body'    => array( 'license_key' => $key, 'instance_id' => $instance_id ),
) );
$data = json_decode( wp_remote_retrieve_body( $res ), true );
$can_update = is_array( $data ) && ! empty( $data['valid'] );
Be clear on the split

What Rindkey does and doesn't do

  • Does: answer "is this key valid for this site?", enforce site limits, keep imported activations, issue keys on new Stripe sales and revoke them on refunds and cancelled subscriptions.
  • Does: keep Lemon Squeezy IDs (store, product, order, customer) in the meta of imported keys, so a plugin that checks meta.store_id or meta.product_id keeps passing.
  • Doesn't: host the update metadata WordPress reads to learn a new version exists, or hand the zip to WordPress's updater. Keep the update server or library you use today and add the check above.

Rindkey isn't affiliated with Lemon Squeezy or WordPress.

See what your store needs before you move

The readiness check is free and read-only. Your Lemon Squeezy API key is used in memory for one request and never stored.