Two ways a plugin gets paid for
A plugin lives inside someone else’s product, so the first question is who handles the money. There are two models.
In the first, the marketplace is the shop. The buyer pays the marketplace, the marketplace issues and checks the license, and you receive a payout minus a commission. JetBrains Marketplace works this way. As of November 2026 its documentation sets the commission on each paid plugin purchase at 15%, says the rate can change with one month’s notice, and says it can never be more than 25%. You do not run a license server because JetBrains does.
In the second, you are the shop. The marketplace only distributes the code. You sell through your own checkout, and the plugin has to ask a license service whether the person using it paid. WordPress premium plugins, Chrome extensions and VS Code extensions mostly work this way. This article is about that second model, because it is the one where you build the licensing yourself.
What each marketplace allows
| Platform | Can the store charge for you? | What the rules mean for licensing |
|---|---|---|
| WordPress.org directory | No | Plugins must be GPL-compatible. Trialware (features locked until payment) is not permitted. Updates must not come from other servers. Sell a separate add-on from your own site. |
| WordPress, sold from your own site | Not applicable | You ship the ZIP, license it per site and serve updates yourself. |
| Chrome Web Store | No | Chrome Web Store payments were deprecated in 2020. Use another payment processor and track licenses yourself. |
| VS Code Marketplace | No built-in checkout | The pricing label accepts only Free and Trial. Sell elsewhere and check a key in the extension. |
| JetBrains Marketplace | Yes | JetBrains sells and licenses the plugin for a commission. |
All entries are as documented in November 2026. Marketplaces change their rules, so read the current page before you design around one. If a platform is not in the table, such as Figma, Obsidian, Raycast or Blender, look for its own monetization page and check three things: whether it takes payment, whether it allows an external license check, and whether it allows downloads from your server.
The WordPress split
The WordPress.org guidelines are the most restrictive and the most often misread. They require every file in the directory to be GPL-compatible, and they say trialware is not permitted: a plugin may not contain functionality that is restricted or locked until the user pays or upgrades. Paid functionality in a service is allowed, provided all the code inside the plugin is fully available. The guidelines recommend add-on plugins, hosted outside WordPress.org, to keep the premium code separate.
The practical design is a free plugin in the directory that works on its own, and a paid add-on plugin that you distribute from your site. The add-on carries the license check and fetches its updates from your own server. GPL does not stop you charging for the add-on or for access to updates and support. It applies to the code you distribute.
Putting the check inside the plugin
A plugin can use the same three calls as a desktop app: activate once, validate now and then, deactivate when the customer moves. The differences are in where the plugin runs and what it can store.
| Environment | Where to store the key and token | What to send as the instance | Watch out for |
|---|---|---|---|
| WordPress plugin (PHP) | A WordPress option, or a transient for the check result | The site URL as instance_name |
Many sites share one server IP. Validate at most once a day. |
| Chrome extension | chrome.storage.local |
A random id made at first run, as fingerprint |
Service workers stop after 30 seconds of inactivity. Do not keep state in globals. |
| VS Code extension | context.secrets (SecretStorage) |
The machine name as instance_name |
Secrets are not synced across machines, so each machine activates once. |
| JetBrains plugin | JetBrains licensing | Not applicable | The marketplace handles it. |
Per-site and per-install seats
A WordPress license usually means one site. Use the site URL as instance_name. The buyer then sees https://client-one.example on the device page and can recognize which site holds a seat. If a customer moves a site to a new domain, the old seat stays occupied until they remove it, so tell them where.
A browser extension has no stable hardware identifier. A random id generated on first run and kept in extension storage is the honest option. A reinstall produces a new id and takes another seat, so set the device limit with that in mind. Clavem’s default is 3 devices per key. For an extension that people install on a work and a home browser, 3 is a sensible floor.
Do not validate on every request
Clavem limits the License API to 120 requests per 60 seconds per IP address and 60 per 60 seconds per license key. Hundreds of WordPress sites on shared hosting can share one outbound IP. If every page view triggers a validation, a busy host reaches the IP limit and every plugin on it starts failing with HTTP 429. Validate on a schedule, store the signed token that comes back, and treat the token as the answer between checks. The offline verification page shows how to verify it.
Behaviors every plugin needs
A license that has expired or was refunded is a normal event, not an error. Decide what each state does before you ship.
valid: falsewith statusexpired: keep the plugin running in free mode and show a renewal link. Do not delete the customer’s data.valid: falsewith statusdisabled: the license was revoked or its order was fully refunded. Show a short message and stop the paid features.- HTTP 404: the key is unknown or the device was removed. Ask for the key again.
- Network error, HTTP 429 or 503: do not change anything. Trust the last good token until its
refresh_bytime and try again later.
Treat every response other than a clear valid: true from the server, or a still-fresh verified token, as “paid features off but nothing else broken”. Plugins that fail loudly on a timeout generate support tickets from the people who did pay.
Updates for premium plugins
Premium WordPress add-ons update from your server. Clavem’s releases endpoint returns the newest published release and gives a download link only when the request carries a valid license key in the X-License-Key header. Without one, the endpoint still reports that a new version exists, which lets the plugin show “version 3.2.1 is available, renew to download”. The update checks documentation has the response shape, and the Clavem WordPress guide has working PHP.
Doing this with Clavem
Clavem is a licensing service for software sold through Stripe, so it covers the second model: you sell through your own Stripe checkout and Clavem issues the key. The License API answers CORS requests from any origin, which matters for extensions that call it directly from a service worker or a content script. Keep the call in the background worker where you can, so a page script cannot read the key.
Clavem is not a marketplace and does not list your plugin anywhere. If your platform has its own paid-plugin system and you are happy with its commission, as with JetBrains, using it saves you the licensing work. If you want to keep the whole sale, or the platform cannot charge at all, as with Chrome and VS Code, your own Stripe account plus a license service is the route. Start from the quickstart and the platform examples in the guides.
Questions
Can I sell a WordPress plugin that is also in the WordPress.org directory?
The free version can be. The directory guidelines do not allow trialware, meaning functionality that is locked until payment, and they do not allow serving updates from other servers. The usual pattern is a free plugin in the directory and a separate paid add-on that you host and license yourself.
Can I charge for a Chrome extension through the Chrome Web Store?
No. Google deprecated Chrome Web Store payments in 2020 and told developers to move to another payment processor and track licenses themselves.
Where does a browser extension store its license key?
In extension storage such as chrome.storage.local, not in a global variable. Chrome stops an extension service worker after 30 seconds of inactivity and loses anything held in memory.
Sources
- WordPress plugin directory guidelines (as of November 2026)
- Chrome Web Store payments deprecation notice from the Chrome Web Store team (2020, as of November 2026)
- Chrome extension service worker lifecycle (as of November 2026)
- VS Code, publishing extensions, pricing label (as of November 2026)
- VS Code API, SecretStorage (as of November 2026)
- JetBrains Marketplace, revenue sharing and fees (as of November 2026)