Stripe Integration
- 392 installs
- 30.1k repo stars
- Updated August 4, 2026
- davila7/claude-code-templates
stripe-integration is a Claude Code skill that implements Stripe checkout, subscriptions, webhooks, and billing portal flows for developers building monetized SaaS or ecommerce backends that accept cards and manage plans
About
stripe-integration is a payments engineering skill from davila7/claude-code-templates, sourced from vibeship-spawner-skills under Apache 2.0, that guides complete Stripe payment system implementation beyond bare API calls. It covers Checkout sessions, subscription lifecycle management, customer billing portal, webhook verification and idempotency, metered billing, Stripe Connect, and dunning for failed payments. The skill emphasizes edge cases that break revenue at scale: declined cards, webhook delivery failures, subscription state transitions, and 3am billing incidents. Developers reach for stripe-integration when adding payments, subscriptions, billing, or checkout to a SaaS or ecommerce backend and need production-grade error handling rather than tutorial-level charge creation. Output includes webhook endpoints, checkout flows, subscription schemas, and billing portal integration code. It assumes Stripe as the payment processor and does not cover alternative processors or tax compliance outside Stripe's built-in tools.
- Structures checkout and subscription setup
- Covers webhook verification and event handling
- Aligns pricing models with Stripe objects
- Reduces payment integration boilerplate mistakes
- Targets SaaS and ecommerce monetization paths
Stripe Integration by the numbers
- 392 all-time installs (skills.sh)
- Ranked #1,100 of 4,347 Backend & APIs skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/davila7/claude-code-templates --skill stripe-integrationAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 392 |
|---|---|
| repo stars | ★ 30.1k |
| Last updated | August 4, 2026 |
| Repository | davila7/claude-code-templates ↗ |
How do you implement Stripe subscriptions and webhooks correctly?
Implement Stripe checkout, subscriptions, webhooks, and customer billing flows when building monetized SaaS or ecommerce backends that must accept cards and manage plans.
Who is it for?
Backend developers building monetized SaaS or ecommerce apps who need production-grade Stripe checkout, subscriptions, and webhook handling.
Skip if: Projects using non-Stripe payment processors or teams needing only read-only Stripe dashboard analytics without payment integration code.
When should I use this skill?
User mentions stripe, payments, subscriptions, billing, checkout, webhooks, metered billing, or Stripe Connect during backend implementation.
What you get
Stripe Checkout flows, webhook handlers, subscription management code, billing portal routes, and payment failure handling patterns.
- checkout integration
- webhook handlers
- subscription billing code
By the numbers
- Covers 6 Stripe integration areas: Checkout, subscriptions, billing portal, webhooks, metered billing, and Connect
Files
Stripe Integration
You are a payments engineer who has processed billions in transactions. You've seen every edge case - declined cards, webhook failures, subscription nightmares, currency issues, refund fraud. You know that payments code must be bulletproof because errors cost real money. You're paranoid about race conditions, idempotency, and webhook verification.
Capabilities
- stripe-payments
- subscription-management
- billing-portal
- stripe-webhooks
- checkout-sessions
- payment-intents
- stripe-connect
- metered-billing
- dunning-management
- payment-failure-handling
Requirements
- supabase-backend
Patterns
Idempotency Key Everything
Use idempotency keys on all payment operations to prevent duplicate charges
Webhook State Machine
Handle webhooks as state transitions, not triggers
Test Mode Throughout Development
Use Stripe test mode with real test cards for all development
Anti-Patterns
❌ Trust the API Response
❌ Webhook Without Signature Verification
❌ Subscription Status Checks Without Refresh
⚠️ Sharp Edges
| Issue | Severity | Solution |
|---|---|---|
| Not verifying webhook signatures | critical | # Always verify signatures: |
| JSON middleware parsing body before webhook can verify | critical | # Next.js App Router: |
| Not using idempotency keys for payment operations | high | # Always use idempotency keys: |
| Trusting API responses instead of webhooks for payment statu | critical | # Webhook-first architecture: |
| Not passing metadata through checkout session | high | # Always include metadata: |
| Local subscription state drifting from Stripe state | high | # Handle ALL subscription webhooks: |
| Not handling failed payments and dunning | high | # Handle invoice.payment_failed: |
| Different code paths or behavior between test and live mode | high | # Separate all keys: |
Related Skills
Works well with: nextjs-supabase-auth, supabase-backend, webhook-patterns, security
Related skills
Lark Openapi ExplorerInstantly explore, test, and generate calls against the full Lark (Feishu) OpenAPI surface without leaving their agent workflow.493k
Lark EventConsume real-time events from Lark/Feishu as structured NDJSON streams inside AI agent workflows.387k16kLark Openapi ExplorerWhen an existing Lark/Feishu skill or CLI command cannot fulfill a specific requirement and they need to discover and invoke the exact native OpenAPI endpoint.386k16k
Just ScrapeQuickly search, crawl, extract structured JSON, or monitor web pages without writing custom scraping code.245k41Lark AppsQuery the current visibility and permission scope of a Lark (Feishu) app without writing HTTP client code.235k16k
Design An InterfaceGenerate multiple radically different interface or API designs in parallel before committing to one.188k198kHow it compares
Pick stripe-integration over generic API wrapper skills when you need subscription lifecycle, webhook idempotency, and dunning patterns for production billing.
FAQ
What Stripe features does stripe-integration cover?
stripe-integration covers Checkout sessions, subscriptions, customer billing portal, webhooks, metered billing, and Stripe Connect. The skill addresses edge cases like declined cards, webhook failures, and dunning rather than only basic charge API calls.
Does stripe-integration handle webhook security?
stripe-integration includes webhook verification, idempotency, and failure recovery patterns. Production payment systems require verified webhook signatures and retry-safe handlers to avoid lost revenue from missed events.
When should developers use stripe-integration?
stripe-integration should be used when building monetized SaaS or ecommerce backends that need card payments, subscription plans, or billing portal access. Triggers include stripe, payments, subscription, billing, and checkout keywords.