Google killed Chrome Web Store payments in 2021 leaving extension developers with no built-in billing infrastructure
In February 2021 Google permanently deprecated Chrome Web Store payments, forcing every extension developer to build or integrate their own billing stack from scratch. An HN thread on the deprecation (270 pts, 169 comments) shows developer anger and confusion. Developers who want to charge for their extensions now must integrate Stripe or Paddle, build entitlement checks, handle tax compliance, and manage license key distribution, all without a single line of help from the platform. This billing vacuum is a primary driver of two outcomes: extensions staying free and eventually selling to acqui-buyers (the only monetization path), or small devs abandoning the platform. Ask HN 'Easiest way to charge money for a Chrome extension?' (10 pts) confirms the ongoing confusion. ExtensionPay and BrowserBill emerged to fill the gap but serve only a fraction of devs.
A browser extension that gives developers a drop-in subscription and one-time payment layer built specifically for Chrome and Edge extensions
439 ▲Score Breakdown
Social Proof 1 sources
Existing Solutions 2 competitors
Third-party payment API built specifically for Chrome extensions. Handles subscriptions and one-time payments without a server.
Recurring subscription and one-time payment platform for browser extension developers.
Gap Assessment
ExtensionPay and BrowserBill handle subscriptions but require developer integration and are not Google-native. No one-click solution comparable to the old Chrome Web Store payments exists. Stripe and Paddle work but add significant billing complexity for solo devs. Market is fragmented.