Clavem

Selling and licensing a Chrome extension with Stripe

The Chrome Web Store no longer sells extensions, so you charge with your own payment system and check a license key from the extension. Use a Manifest V3 service worker with an alarm for the daily check, keep the instance id in local storage, and never download code to turn features on.

The store lists, you charge

Chrome Web Store payments were switched off in stages. Google’s deprecation notice to developers, dated 21 September 2020, said you could no longer create new paid extensions or in-app items, that free trials would be disabled on 1 December 2020, and that from 1 February 2021 existing items could no longer charge with Web Store payments. The notice told developers to move to third-party providers, which is also what the current store docs say: a published item “can be free, or you can charge for it using any payment system you like”.

So for a paid Chrome extension, the Chrome Web Store is how people find and install it, and payment is yours. Stripe takes the card, Clavem issues the key. Unlike JetBrains or Figma, the store offers no paid listing you could choose instead, so there is no trade-off to weigh: this is the setup.

Other browsers’ add-on stores have their own rules. Check each one’s terms before you assume the same arrangement.

What is specific to extensions

Manifest V3 service workers sleep. A background page that stays alive is gone. A service worker starts, handles an event and stops. Use chrome.alarms for the daily re-check, and keep state in chrome.storage, not in variables.

No host permission needed. Chrome’s docs say a request to an origin the extension has no host permission for is treated as an ordinary cross-origin request. The License API answers with Access-Control-Allow-Origin: *, so calls from the service worker work without a host permission, which also means no extra permission prompt at install.

No remote code. The program policies say developers must not obfuscate code and must not run logic fetched from a remote source, with narrow exceptions for documented APIs. So you cannot turn paid features on by downloading a script after validation. Ship all code in the package, gate features by the license state, and keep paid logic that must stay secret on a server.

Sync can double-count devices. chrome.storage.sync copies data to every browser signed in to the same Google profile. If the license is in sync, a second computer gets the key and token but has no instanceId of its own, so it either fails the instance check or activates again and uses another seat. Keep the instance id in chrome.storage.local, and treat a sync copy of the key as a convenience that triggers a fresh activate on the new machine.

No hardware id. Extensions cannot read one. Generate a random id on first run, store it locally and send it as fingerprint, with an instance_name such as Chrome on Windows.

A service-worker check

const API = 'https://clavem.io/v1/licenses';

async function call(action, body) {
  const res = await fetch(`${API}/${action}`, {
    method: 'POST',
    body: new URLSearchParams(body),
    signal: AbortSignal.timeout(8000),
  });
  return { status: res.status, body: await res.json() };
}

chrome.alarms.create('license-check', { periodInMinutes: 24 * 60 });

chrome.alarms.onAlarm.addListener(async ({ name }) => {
  if (name !== 'license-check') return;
  const { license } = await chrome.storage.local.get('license');
  if (!license) return;
  try {
    const { status, body } = await call('validate', {
      license_key: license.key,
      instance_id: license.instanceId,
    });
    if (status === 200) {
      await chrome.storage.local.set({ license: { ...license, token: body.token, valid: body.valid } });
    } else if (status === 404) {
      await chrome.storage.local.remove('license'); // key or device removed: ask again
    }
  } catch {
    // Offline or timed out: keep the stored token and try at the next alarm.
  }
});

The manifest needs the storage and alarms permissions. A form-encoded body is a simple request, so the browser sends no preflight. On a 429 or 5xx the code above changes nothing, which is what you want. To check without a network, verify the signed token’s Ed25519 signature with Web Crypto; see offline verification.

Setting Suggested value Why
License type Annual subscription, or one-time for a simple tool Browser tools need upkeep as Chrome changes
Device limit 3 Work and home computers, plus one reinstall
Trial 7 to 14 days kept in storage.local Cheap to run; no license exists before purchase
Updates The Web Store delivers them You cannot self-update an extension outside the store

Because the store ships updates to everyone, you cannot withhold a new version from an unpaid user. What a new version does without a valid key is what you control.

Doing this with Clavem

Create a product, connect Stripe, map the Stripe price. A buyer gets a key by email and an order page. In the extension, the options page takes the key, calls activate, stores the result and shows the state. The Chrome extension guide has the full flow, and the offline guide has the token check. If you do not need a store-hosted checkout, a Stripe Payment Link in the extension’s welcome page is enough.

Guides to follow

Questions

Can I sell a Chrome extension through the Chrome Web Store?

Not with Google's own payments. Google deprecated Chrome Web Store payments in September 2020, stopped new paid items at once and ended charging for existing ones on 1 February 2021. Its docs now say a published item can be free or you can charge using any payment system you like.

Can the extension download paid code after the license check?

No. The Web Store policies forbid executing logic fetched from a remote source except through specific documented APIs. Ship the paid code in the package and gate it with the license state, or move the paid logic to a server you control.

Sources

  1. Chrome Web Store payments deprecation notice, repost on chromium-extensions (checked November 2026)
  2. About the Chrome Web Store (checked November 2026)
  3. Chrome Web Store program policies (checked November 2026)
  4. Cross-origin network requests in extensions (checked November 2026)