Getting paid, plainly

How to Monetize a Chrome Extension Now That Google's Payments Are Gone: Accounts, Trials, Credits and the Ad Rules

There is no buy button in the Chrome Web Store anymore. Google retired it years ago, which surprises the founder who budgeted for a store cut and delights the one who reads the fine print. Getting paid for an extension now happens on your own website, under your own rules, with a few of Google's still attached.

November 17, 2026 · 10 min read

acmepricewatch.com · extension billing report
Free install, account on the web app, paid plan
Where a fictional extension's installs stop short of paying
Installed from the store1,000
Connected an account520(52%)
Started a paid trial210(40%)
Kept a monthly plan120(57%)

Half never connect an account: put the sign-in button where the extension first appears

Illustrative: a sample billing funnel for a fictional price-check extension

The short answer

Chrome Web Store payments are deprecated, so a paid extension now bills through the developer's own website: the user creates an account and pays there, and the extension checks that account through the developer's server. Google's policies require you to say in the listing if basic features cost money and to identify yourself, not Google, as the seller. Ads and affiliate links carry separate, stricter rules.

On this page
  1. Google's checkout counter closed in five stages
  2. What replaced it: a free install and an account on your server
  3. GatorCrawl's price list, quoted from its own site
  4. Trials, credits, seats or one flat monthly fee
  5. Two disclosures Google requires before anyone pays
  6. Ads and affiliate links: a narrow lane with a drop on each side
  7. When the extension should not carry a price of its own

Google's checkout counter closed in five stages

Google's own payments notice is gone from its live address, which now returns a 404 page. According to an Internet Archive copy of the notice, captured on February 26, 2026 and last updated by Google on September 20, 2020, "The Chrome Web Store payments system is now deprecated and will be shut down over the coming months." The same copy tells developers who used it that they would "need to migrate" to another way to get paid. It names no replacement processor.

Milestones as listed in Google's payments deprecation notice, according to the Internet Archive copy of February 26, 2026
DateWhat the notice saidWhat it meant
March 27, 2020"Publishing of paid items temporarily disabled."No new paid listings went up
September 21, 2020"You can no longer create new paid extensions or in-app items."The store stopped being a place to sell
December 1, 2020"Free trials are disabled."Trials moved to the developer's own billing
Feb 1, 2021Existing items and in-app purchases "can no longer charge money" through the storeEvery paid extension needed its own checkout
At some future timeThe licensing API will stop reporting license statusOld license checks are a liability, not a plan

If an older extension still asks Google whether a user has paid, treat that code as borrowed time. The notice gives no date for the licensing change, and we will not guess one. A rebuild of the billing check is usually a small job; our maintenance page covers how we quote it.

What replaced it: a free install and an account on your server

The pattern almost every paid extension uses now is simple to describe. The extension installs free. The user signs in to an account on your website. Your server knows the plan, the trial and the balance, and the extension asks your server before it does paid work. Google's Manifest V3 requirements list "Syncing user account data with a remote server" among the remote calls an extension may make, so the account check is squarely inside the rules.

  1. 1

    Install from the store, free

    The listing explains what the extension does and, if basic features cost money, says so up front.

  2. 2

    Connect the account

    A button opens your site's sign-in or sign-up page, which hands the extension a token tied to that account.

  3. 3

    Pay on your own site

    Checkout, trials, plan changes and invoices all happen in your web app, through your own payment processor.

  4. 4

    Check before paid work

    Each paid action calls your server, which confirms the plan or deducts credits and returns the data.

  5. 5

    Show the balance

    The extension displays what is left, so nobody is surprised by a stopped feature.

The money logic lives on the server for a second reason. Chrome's getting started guide says all extension logic must ship inside the package, and Google disallows obfuscating that code. Prices, limits and secrets belong on the server, where no user can edit them. Connecting the extension to your existing web app or payment system goes live the same day through our API integration work; if you need the web app itself, see web app development.

Glowing cyan and blue blocks stacked like rising coins along a thin data grid on a deep blue and violet field, soft light, no text or numbers
Paid extensions now keep the meter on the developer's own server, not in the store.

GatorCrawl's price list, quoted from its own site

Our GatorCrawl Keywords extension follows the pattern exactly. Its site says the extension is "Free to install from the Chrome Web Store. Lookups use your plan's credits," and defines the unit: "One credit is one keyword with data." The extension carries no price of its own. It is "Included with every plan," and every plan lists "Chrome extension on Google" among its features. Prices below are as of November 2026.

GatorCrawl Keywords monthly plans as stated on keywords.gatorcrawlseo.com, as of November 2026
PlanMonthly priceKeyword creditsSeats
Starter$19/mo20,000 a month1
Pro$49/mo55,000 a month3
Agency$129/mo145,000 a month10
Trial$5 for 7 days, charged today, non-refundable5,000 for the 7 daysThen the chosen plan

The site describes the trial in full: "Every plan starts with a 7-day trial for $5 (charged today, non-refundable): 5,000 keyword credits for 7 days, then your plan. Cancel any time." Annual billing is labeled "2 months free." The store listing, read November 16, 2026, shows "Offers in-app purchases," which reflects the plans sold on the site. We publish no user count or revenue for it, because none is public and we will not invent one.

One small decision protects customers' credits. The service worker keeps results for an hour in session storage, so reloading the same Google page does not spend credits again. The options page shows the connected account and the credits left. Those two details do more for trust than any pricing page copy. Our build write-up shows where they live in the code, and the SaaS companion page applies the same pattern to other apps.

Trials, credits, seats or one flat monthly fee

No pricing model is right for every extension, and no source we trust ranks them by revenue. Here is how we think about the choice, as practice rather than research.

Credits

Fits extensions whose every action costs you money, such as data lookups or AI calls. Customers pay for use; you need a visible balance and a cache so they never pay twice for the same result.

Seats

Fits team tools where value grows with headcount. Pairs well with a company account and an administrator who adds people.

Flat monthly fee

Fits extensions with low running costs and steady use. Easiest to explain, hardest to keep fair when one customer uses fifty times more than another.

Paid trial

A small charge, like GatorCrawl's $5 for seven days as of November 2026, filters out casual sign-ups and confirms the card works. It also asks more of the listing, which has to earn that first payment.

Free extension, paid app

The extension is a door into a product people already pay for. Charge for the app; let the extension raise its value.

Mixing models is common: GatorCrawl combines plans, credits and seats. What matters more than the model is that the extension shows the customer where they stand before they hit a limit. An AI assistant extension almost always needs credits or a usage cap, because every summary costs a model call.

Two disclosures Google requires before anyone pays

Google's accepting payment policy is short and specific. If users must pay "to obtain basic functionality," you must make that clear in the description they see when deciding whether to install. And "You must clearly identify that you, not Google, are the seller of the products or services." The publishing guide adds that the dashboard's Distribution tab is where you declare whether the extension is a paid item.

Some founders plan to fund a free extension with ads or affiliate commissions. Google permits both under conditions, and enforces them. The rules below come from Google's ads policy, its affiliate ads policy and the affiliate policy update published March 11, 2025, all read in November 2026.

  • Ads must be shown in context or say which product they come with, and must be easy to remove through settings or by uninstalling.
  • Ads placed on other websites are allowed only when the behavior is "clearly disclosed to the user" and does not interfere with that site's own ads or features.
  • Google's ads policy says that "Currently, AdSense may not be used to serve ads in Products, per AdSense policies."
  • An extension whose primary purpose is serving ads violates the single purpose rule, and so does one that shows reviews but "also injects ads into web pages."
  • Any affiliate program must be described prominently on the listing, in the interface and before installation, and each affiliate code or link needs a related user action first.
  • Since enforcement began June 10th 2025, extensions may not inject affiliate links when no real discount, cashback or relevant offer is provided; Google's FAQ says a coupon extension must not inject one "if no valid coupon or discount is available."

Google's troubleshooting page has a code for this, Grey Titanium, for affiliate ads violations. Our view, as practice: for a business extension, ads and affiliate links cost more trust than they earn. If the extension serves your customers or your staff, charge for the product or fold it into one you already sell. The ecommerce extensions page covers store-owner tools, where affiliate questions come up most.

When the extension should not carry a price of its own

Here is the advice that loses us nothing to give. If you already sell a web app, the extension usually should not have its own price. It should make the app more useful and more often used, the way GatorCrawl's extension is included with every plan. If the idea only works when thousands of strangers pay a few dollars each, and you have no audience yet, the extension is a bet on distribution, not on code, and no developer can promise the installs. Our list of extension ideas for business leans toward jobs that pay for themselves in saved time.

When the numbers do work, we build the extension, the account connection and the billing check together, from $1,500, depending on complexity, with a fixed written estimate before work starts. The listing goes up under your own developer account, so the product and its customers stay yours. We promise no revenue, installs or approval. The build service page explains the offer, the section overview shows what we make, and a fractional CTO can help weigh the business case first. DataCram is a San Antonio studio building for the web since 1999 (about); call (210) 346-0848.

Questions owners ask about custom browser extensions

Not through Google's payment system. According to Google's deprecation notice, read through an Internet Archive copy, new paid extensions stopped in September 2020 and existing items could no longer charge through the store from February 1, 2021. Paid extensions now take payment on the developer's own website and check the user's account from the extension.

Google's Chrome Web Store ads policy says AdSense may not currently be used to serve ads in products, per AdSense policies, as of November 2026. Other ads must be shown in context or name the product they come with, and be easy to remove. An extension whose main purpose is serving ads breaks the single purpose rule.

Only under Google's affiliate ads policy. The program must be disclosed prominently on the listing, in the interface and before install, and each affiliate link needs a related user action. Since June 10th 2025, extensions may not inject affiliate links when no real discount, cashback or relevant offer is provided.

Run it on your own site. Google's notice says Chrome Web Store free trials were disabled on December 1, 2020. Your server records the trial start, limits and expiry, and the extension checks that account before paid work. GatorCrawl Keywords, for example, offers a 7-day trial for $5 with 5,000 credits, as of November 2026.

Yes, if basic functionality requires payment. Google's accepting payment policy says you must make that clear in the description users see when deciding whether to install, and you must identify yourself, not Google, as the seller. The developer dashboard's Distribution tab is also where you declare a paid item.

If you already sell a web app, including the extension in every plan is often the simpler choice: one account, one bill, and the extension adds value to what customers already pay for. GatorCrawl Keywords works that way. A separate price makes sense when the extension is the whole product and its running costs justify it.

Keep reading

Free · No obligation

Plan how the extension gets paid

Tell us what the extension does and how you sell today. We reply with the billing approach we would use, what connects to what, and what the build would cost.

Which of these sounds like you? (pick any)

Rather talk now? Call (210) 346-0848.

CallGet a quote