extension-payment
Extension Payment Integration
Integrate payment/subscription into a Chrome extension. Ask user for provider, then fetch docs and implement.
Workflow (Execute This)
Step 1: Ask user for payment requirements
Ask the user to confirm:
- Payment model: One-time purchase / Subscription / Freemium / Credits-based
- Provider category: Payment Gateway or Merchant of Record (MoR)?
- Preferred provider (or let us recommend)
- Required info: API keys, product/price IDs, webhook URL
Recommend MoR for solo/indie developers — handles tax, compliance, billing portal. No need to register as a business in every country.
Step 2: Provider selection guide
| Category | Provider | Best For | Docs |
More from quangpl/browser-extension-skills
extension-ui
Build polished Chrome extension UIs (popup/sidepanel/options). Analyze existing UI, suggest improvements, set up design systems, enforce a11y and UX best practices.
25extension-analyze
Audit Chrome extensions for security issues, best practice violations, performance problems, and CWS compliance. Scans manifest, code, CSP, message handlers, storage, and dependencies.
24extension-create
Auto-scaffold Chrome extensions with WXT or Plasmo. Ask user for name/features, scaffold, configure entrypoints. Use when: create extension, scaffold, new extension.
23extension-manifest
Generate and validate manifest.json with optimal permissions for Chrome MV3 extensions. Analyzes code to determine minimum permissions. Use when: manifest, permissions, manifest.json.
22extension-dev
Detect Chrome extension framework/stack, find proper docs, implement features, and debug across service worker, content script, and popup contexts.
21extension-assets
Generate and manage all Chrome extension assets: icons (16–128px), CWS listing images, promotional tiles, and public/ folder setup. Supports ImageMagick, Gemini API, and manual prompt templates.
20