A JavaScript library to add payments and subscriptions to browser extensions without needing a backend server.
ExtPay.js is a JavaScript library that enables browser extension developers to add payment processing and subscription management to their extensions without needing to build a backend server. It integrates with ExtensionPay.com to handle user authentication, Stripe payments, and subscription lifecycle, simplifying monetization for extension creators. The library provides methods to check user payment status, open payment pages, and manage trials, all within the extension's context.
Browser extension developers who want to monetize their extensions through one-time payments or subscriptions without the overhead of setting up and maintaining a payment backend. It's ideal for solo developers or small teams looking for a quick and easy way to start earning revenue from their extensions.
Developers choose ExtPay.js because it eliminates the need for server-side infrastructure, drastically reducing development time and complexity. Its seamless integration with Stripe, support for free trials, and cross-browser compatibility make it a turnkey solution for monetizing extensions, allowing creators to focus on building features rather than payment systems.
The JavaScript library for ExtensionPay.com — payments for your browser extensions, no server needed.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Eliminates backend development by routing payments through ExtensionPay.com, as emphasized in the 'No Server Required' key feature, allowing developers to skip server setup entirely.
User testimonial cites setup in under an hour, and the README's simple code examples—like initializing with ExtPay('id') and calling startBackground()—enable quick implementation.
Handles recurring payments, free trials, and user status automatically with methods like getPlans() and event listeners such as onPaid, detailed in sections 6-9 of the README.
Uses Mozilla's webextension-polyfill to work across modern browsers and supports both Manifest V2 and V3, as noted in the README's introduction and configuration sections.
Relies entirely on ExtensionPay.com's servers; service downtime or discontinuation could break payment functionality, with no self-hosting option mentioned.
Payment and trial pages are hosted externally with fixed designs—screenshots in the README show predefined layouts—offering minimal branding control beyond optional text arguments.
Requires careful manifest.json tweaks, such as content scripts for event listeners and handling service worker quirks in Manifest V3, which the README warns can lead to undefined variables in callbacks.