Stripe payment platform integration: manage payments, subscriptions, invoices, and customers via Stripe API.
Automate Chaser tasks via Rube MCP (Composio).
Automate Elorus tasks via Rube MCP (Composio).
Automate Fidel API tasks via Rube MCP (Composio).
Automate Skyfire tasks via Rube MCP (Composio).
Use Miru MCP safely from AI agents with Pro-gate awareness, namespaced tools, and write-safe defaults (`dry_run`, `idempotency_key`).
Request and receive payments by generating a payment link you can send out and monitor for status.
Integrate payments with SePay (VietQR), Polar, Stripe, Paddle (MoR subscriptions), Creem.io (licensing).
Drafts overdue-invoice reminder emails from the ledger (MYOB, NetSuite, QuickBooks, Xero, or Zoho Books) plus PayPal, Stripe, and…
Add Polar billing to a TypeScript/JavaScript app using the @polar-sh/sdk package — Checkout, Customer Portal, and Webhooks endpoints in…
Generate professional PDF invoices from JSON data with company/client details and line items.
Integrate PayPal payment processing with support for express checkout, subscriptions, and refund management.
Interactive onboarding wizard to set up Polar payment integration from scratch — authentication, product creation, and framework-specific…
Build automated billing systems for recurring payments, invoicing, subscription lifecycle, and dunning management.
Stripe, RevenueCat, subscription billing, webhooks, PCI compliance, and tax
This skill should be used when working on Polar billing system, Stripe integration, subscription lifecycle, checkout flows, or benefit…
Automate Zoho Invoice tasks via Rube MCP (Composio): invoices, estimates, expenses, clients, and payment tracking.
Payments & Billing agent skills on mcprush, filed under one heading so the shelf can be read in one pass. The kinds are workflow, expertise, output format, voice & style and guardrail, and the one a skill belongs to, where its author declared it, is the fastest way to guess what it will do to your prompt.
What to look at before installing one is what it costs in context and what it takes away: a guardrail that refuses an action and a voice that rewrites a sentence are both skills, and only one of them will stop the agent doing something. Every skill here says what it costs in context, which kind it is where its author declared one, what it needs beside it to work and the licence it is published under, next to the publisher it came from and whether that publisher has been verified. The filters on the left narrow it further and the sort at the top decides what comes first.
A skill is not connected to anything: there is no endpoint to authorise and nothing routed through the gateway. Installing one drops a folder of instructions into the client’s own skill folder, and uninstalling it is deleting that folder. The exact line for each client is on the skill’s own page, because it differs by client rather than by skill.