Agent skill · software engineering · borghei
stripe-integration-expert
Implement Stripe integrations for SaaS billing: subscriptions, checkout, proration, usage- based billing, idempotent webhooks, customer portal, dunning, and SCA. Use when building billing, handling webhooks, or testing with Stripe CLI.
Why this skill is useful
Adds executable scripts and patterns for Stripe integration that are not commonly found in public documentation.
What it needs
Requires stripe-cli installed locally. Requires stripe account access. About 3k tokens when loaded. Last updated 2026-07-21. 462 stars on the source repository.
What this skill does
Stripe Integration Expert The agent builds production-grade Stripe integrations for SaaS billing: subscription lifecycle management with trials and proration, idempotent webhook handlers, usage-based metered billing, Checkout sessions, Customer Portal, dunning recovery, and SCA/3D Secure compliance. Provides patterns for Next.js, Express, and Django with emphasis on real-world edge cases. Core Capabilities Checkout & client setup — pinned-version Stripe client, centralized plan config, Checkout sessions with trials, tax collection, and promo codes Subscription lifecycle — a state machine covering trialing → active → pastdue → canceled, plus upgrades/downgrades with proration previews and reactivation Idempotent webhooks — signature verification, event dedup, re-fetch-from-API handlers, and retry-safe processing Usage-based billing & gating — metered usage records, feature gating by plan, and grace-period access logic Dunning & SCA — payment-failure email sequences and PSD2 / 3D Secure authentication flows Local testing — Stripe CLI webhook forwarding, event triggers, and test card matrix When to Use Building SaaS subscription billing from scratch on Next.js, Express, or Django Adding plan upgrades/downgrades with correct proration behavior Hardening or debugging a webhook endpoint for idempotency and retry safety Implementing metered/usage-based billing or feature gating by plan Adding dunning recovery or European SCA/3D Secure compliance Clarify First Before building the integration, confirm these inputs. If any is unknown or vague, ASK — do not assume: [ ] Framework — Next.js / Express / Django (the handler and client patterns differ per stack) [ ] Billing model — flat subscription / metered usage-based / trials + proration (shapes the subscription state machine and code) [ ] Scope — which piece: Checkout, idempotent webhooks, dunning, or SCA/3D Secure (selects the reference and code generated) Stop rule: ask only the 2-3 that most change the output. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills borghei/stripe-integration-expert