Extension Payment

Community

quangpl

extension-payment

Integrate payment gateways into Chrome extensions. Stripe, Paddle, Lemon Squeezy, Polar, PayPal, and more. Licensing, subscriptions, freemium. Use when: payment, monetize, subscribe, billing, premium.

Overview

Publisher	quangpl
Repository	`browser-extension-skills`
Skill name	`extension-payment`
Stars	65
Forks	10
Bundled files	4
License	MIT
Links	Skill source Repository

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
4 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by quangpl on GitHub. Read the source before you install it.

Installation

Install the Extension Payment AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/quangpl/browser-extension-skills/tree/main/skills/extension-payment
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/quangpl/browser-extension-skills.git /tmp/browser-extension-skills
mkdir -p .claude/skills
cp -r /tmp/browser-extension-skills/skills/extension-payment .claude/skills/extension-payment

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Extension Payment in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Extension Payment on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Extension Payment is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Extension Payment Integration

🚀 Upgrade to Premium Get the Premium version at https://app.extensionbooster.net/dashboard/services/extension-ai-kit

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
MoR	Paddle	SaaS subscriptions, global tax	https://developer.paddle.com
MoR	Lemon Squeezy	Indie/solo devs, simple setup	https://docs.lemonsqueezy.com
MoR	Polar	Open source monetization	https://docs.polar.sh
MoR	Creem	Extension-focused MoR	https://docs.creem.io
MoR	Dodo Payments	Simple digital products	https://docs.dodopayments.com
MoR	FastSpring	Enterprise digital commerce	https://developer.fastspring.com
MoR	Gumroad	Creators, digital products	https://help.gumroad.com
Gateway	Stripe	Full control, most flexible	https://docs.stripe.com
Gateway	PayPal	Wide user base, easy checkout	https://developer.paypal.com/docs
Gateway	Razorpay	India-focused payments	https://razorpay.com/docs
Gateway	Square	POS + online	https://developer.squareup.com/docs
Gateway	Adyen	Enterprise, multi-currency	https://docs.adyen.com
Gateway	Braintree	PayPal-owned, cards + PayPal	https://developer.paypal.com/braintree/docs
Gateway	Authorize.Net	US legacy, reliable	https://developer.authorize.net

llms.txt for AI-assisted docs (use docs-seeker skill):

Stripe: https://docs.stripe.com/llms.txt
Polar: https://docs.polar.sh/llms-full.txt

Step 3: Fetch provider docs

Use docs-seeker skill to fetch the provider's latest API docs. For Stripe/Polar, use llms.txt endpoints.

Step 4: Implement the integration

See references/integration-architecture.md for the full pattern.

Key architecture (extensions cannot run backend code):


Extension (popup/options) → Your Backend API → Payment Provider
         ↕                        ↕
   chrome.storage          License/subscription DB

Step 5: Show user the post-integration workflow

After integration, show the user this flow:


User clicks "Upgrade" in extension
  → Opens payment page (provider-hosted or custom)
  → Completes payment
  → Webhook hits your backend
  → Backend validates + stores license
  → Extension checks license via API
  → Premium features unlocked

References

references/integration-architecture.md — Backend setup, license validation, webhook handling
references/mor-vs-gateway.md — MoR vs Gateway decision guide, tax/compliance
references/extension-licensing-patterns.md — License key, account-based, feature flags
references/provider-quickstarts.md — Quick setup for top 5 providers

Related Skills

extension-publish — Store submission and listing
extension-analyze — Security audit (API key exposure check)
extension-dev — Feature development workflow

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Extension Payment AI skill do?

Why use Extension Payment on TypingMind?

Because you install it once and use it with any model. Extension Payment is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Extension Payment in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/quangpl/browser-extension-skills/tree/main/skills/extension-payment. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Extension Payment?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Extension Payment?

As many as you like. As long as a model supports skills, you can use Extension Payment with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Extension Payment AI skill free?

Yes. It is published on GitHub by quangpl under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Market Research

affaan-m

CommunityPopular

Conduct market research, competitive analysis, investor due diligence, and industry intelligence with source attribution and decision-oriented summaries. Use when the user wants market sizing,…

X Api

X/Twitter API integration for posting tweets, threads, reading timelines, search, and analytics. Covers OAuth auth patterns, rate limits, and platform-native content posting. Use when the user wants…

Postgres Patterns

Patrones de base de datos PostgreSQL para optimización de consultas, diseño de esquemas, indexación y seguridad. Basado en las buenas prácticas de Supabase.

Android Clean Architecture

affaan-m

CommunityPopular

Android と Kotlin Multiplatform プロジェクトのクリーンアーキテクチャパターン — モジュール構造、依存関係ルール、UseCase、Repository、データ層パターン。

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Extension Payment Integration

Workflow (Execute This)

Step 1: Ask user for payment requirements

Step 2: Provider selection guide

Step 3: Fetch provider docs

Step 4: Implement the integration

Step 5: Show user the post-integration workflow

References

Related Skills

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now