stripe-integration▌
davila7/claude-code-templates · updated Apr 9, 2026
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.
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
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.8★★★★★55 reviews- ★★★★★Dhruvi Jain· Dec 28, 2024
stripe-integration is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Isabella Gill· Dec 20, 2024
I recommend stripe-integration for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Evelyn Gupta· Dec 20, 2024
We added stripe-integration from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Benjamin Wang· Dec 16, 2024
stripe-integration has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Diya Li· Dec 16, 2024
stripe-integration reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Ira Reddy· Dec 4, 2024
stripe-integration fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Rahul Santra· Nov 27, 2024
Keeps context tight: stripe-integration is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Henry Jain· Nov 23, 2024
stripe-integration is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Oshnikdeep· Nov 19, 2024
stripe-integration fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Carlos Mehta· Nov 11, 2024
Useful defaults in stripe-integration — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
showing 1-10 of 55