How to Sell a Chrome Extension in 2026: License Keys, Payments and Tax
To sell a Chrome extension, publish it free in the Chrome Web Store and sell the Pro version from your own checkout. Your extension then unlocks Pro when the buyer enters a license key. With Pocketsflow, each sale creates the key automatically, your extension checks it against two public endpoints with no secret key inside the code, and the sale costs 4.7% + $0.30 with sales tax and VAT handled. Pocketsflow is the seller, so a refund switches the key off by itself.
Why you sell outside the Chrome Web Store
Google's developer agreement says Google has no obligation to process payments for paid products, verify who paid, keep payment records or charge taxes, and it does not track which users already paid. The store's payment policy adds three rules for any extension that charges:
- If users must pay for basic functionality, say so in the store description.
- Make clear that you, not Google, are the seller.
- Post your terms of sale, including your refund policy.
A free install with a paid Pro unlock fits all three. Your listing says what is free and what is Pro, and Pocketsflow's checkout and receipt show the seller and the refund terms.
Decide what goes behind Pro
The free version has to be useful on its own, or the store reviews will say so. Put the features that save power users real time behind Pro: bulk actions, sync across browsers, exports, more saved items, or advanced settings. Keep the upgrade prompt where the limit is reached, not on every page load. The Pocketsflow product page can list exactly what Pro adds, so the buyer knows before paying, and you can change the price at any time to test what converts. You can also give early users a discount code; codes work on every Pocketsflow plan.
Pocketsflow vs ExtensionPay
ExtensionPay is a payments library made for extensions. Its facts are from its own site, read November 18, 2026.
| Selling an extension | Pocketsflow | ExtensionPay |
|---|---|---|
| Fee per sale | 4.7% + $0.30, all in | 5%, on your own Stripe account |
| Stripe account needed | No | Yes |
| Sales tax and VAT | Collected and paid for you | Your job; Stripe Tax can calculate it |
| Where you can sell from | 160+ countries | Wherever Stripe works |
| How Pro unlocks | License key with activation limit | Its own library in the extension |
What each sale costs
Extensions sell at small prices, so the fixed part of each fee matters. The chart shows the fee as a share of one US card payment. ExtensionPay's 5% is added to Stripe's own 2.9% + 30¢ on the Stripe account it pays into.
| Point | Pocketsflow | ExtensionPay + Stripe |
|---|---|---|
| $3 | 14.7% | 18% |
| $5 | 10.8% | 14% |
| $10 | 7.7% | 10.9% |
| $20 | 6.2% | 9.4% |
Source: Pocketsflow pricing (www.pocketsflow.com/pricing), 4.7% + $0.30; extensionpay.com, 5% transaction fee, read November 18, 2026; stripe.com/pricing, 2.9% + 30¢ per domestic card, read November 16, 2026. One US card payment.
On a $5 Pro unlock, Pocketsflow takes $0.54 (10.8%) and ExtensionPay with Stripe $0.70 (14%). On $20, it is $1.24 against $1.88. If you turn on Stripe Tax with ExtensionPay, Stripe's tax fee comes on top, and filing the returns is still yours.
How to sell your extension with Pocketsflow
- Create the Pro product. In Pocketsflow, create a one-time product such as "Pro, lifetime", open License keys, switch on Generate a license key for each sale, and set an activation limit, for example 3 browsers.
- Link to the checkout. Point the Upgrade button in your popup or options page at the product's checkout link. After paying, the buyer gets the key in the receipt email and in My purchases, with a copy button.
- Activate. In your options page, add a field for the key. Generate an install ID once and save it in
chrome.storage, then callPOST /licenses/activatewith the product ID, the key and that install ID. No API key goes in the request. - Validate. When the extension starts, call
POST /licenses/validateand unlock Pro only whenvalidis true. Cache the answer so a short network outage doesn't lock out a paying user.
Every call goes to https://api.pocketsflow.com, so add it to your extension's host_permissions. When an order is refunded or disputed, its key stops validating on its own, and Pro turns off at the next check. A buyer who gets a new computer can free an activation from the old one, or you can reset the key's activations for them.
Monthly plans instead of a lifetime license
License keys on Pocketsflow are for one-time products. For a monthly Pro plan, sell a subscription and grant access from your own server: the subscription webhooks tell you when a subscriber starts, renews or cancels, and the API tells you any subscriber's status. That needs a small backend with user accounts, so most solo extension makers start with a lifetime license and add a plan later. The setup with webhooks and the SDK is in how to add payments to an AI app.
When ExtensionPay is the better choice
ExtensionPay suits a developer who already has a Stripe account, is happy to handle sales tax with Stripe Tax or on their own, and wants a library that handles the paid state for them without a license field. Pocketsflow suits an extension sold worldwide from day one, by a developer who wants tax handled and no Stripe account to set up. For more on keys in desktop apps and plugins, read how to add license keys to your software, or see Pocketsflow for apps and plugins.