Loading...
Loading...
Found 60 Skills
Payments library: idempotency-key patterns, a webhook reliability checklist, Stripe, Adyen, and PayPal quirks, a refund and chargeback decision tree, currency handling, PCI scope reduction, the PaymentIntent state machine, and code for idempotent creation, webhook processing, 3DS2 exemptions, and dunning. Use when building or debugging payment flows.
Checkout.com integration. Manage data, records, and automate workflows. Use when the user wants to interact with Checkout.com data.
Enfuce integration. Manage data, records, and automate workflows. Use when the user wants to interact with Enfuce data.
Add Stripe payments to a web app — Checkout Sessions, Payment Intents, subscriptions, webhooks, customer portal, and pricing pages. Covers the decision of which Stripe API to use, produces working integration code, and handles webhook verification. No MCP server needed — uses Stripe npm package directly. Triggers: 'add payments', 'stripe', 'checkout', 'subscription', 'payment form', 'pricing page', 'billing', 'accept payments', 'stripe webhook', 'customer portal'.
Expert-level banking systems, core banking, regulations, and banking technology
Manage account balance, payments, invoices, webhooks, and view audit logs and detail records. This skill provides Ruby SDK examples.
WePay integration. Manage data, records, and automate workflows. Use when the user wants to interact with WePay data.
Manage account balance, payments, invoices, webhooks, and view audit logs and detail records. This skill provides JavaScript SDK examples.
View Stripe revenue metrics — MRR, total charges, balance, refunds, and payouts. Use when the user asks about revenue, income, MRR, charges, refunds, or financial overview.
Implement Stripe payment processing for robust, PCI-compliant payment flows including checkout, subscriptions, and webhooks. Use when integrating Stripe payments, building subscription systems, or implementing secure checkout flows.
Complete Stripe payments integration with subscriptions, webhooks, and customer portal. Use when adding billing to a SaaS application with subscription tiers, usage-based pricing, or one-time payments.
Integrate Commet billing and payments into any application. Use when working with @commet/node, @commet/next, @commet/better-auth, the Commet CLI, or building billing features like subscriptions, usage tracking, seat management, checkout, customer portal, webhooks, feature gating, or payment flows. Triggers on imports from "@commet/node", "@commet/next", "@commet/better-auth", commet SDK usage, billing integration tasks, or mentions of Commet.