Stripe Integration
Get paid from day one. Payments, subscriptions, billing portal, webhooks, metered billing, Stripe Connect. The complete guide to implementing Stripe correctly, including all the edge cases that will bite you at 3am. This isn't just API calls - it's the full payment system: handling failures, managing subscriptions, dealing with dunning, and keeping revenue flowing. Use when: stripe, payments, subscription, billing, checkout.
- Skill ID
- davila7/claude-code-templates/stripe-integration
- Publisher
- davila7
- Repository
- claude-code-templates
- Installs
- 0
- Files
- 1
- Synced
- Sep 23, 2026
Open any RiverX project, open the Skills panel in the chat, and search for this identifier. The files are fetched from the source repository at install time.
davila7/claude-code-templates/stripe-integrationInstalls these files- SKILL.md
What this skill tells the agent
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
More from davila7
Use this skill in a project
Open any RiverX project, search the Skills panel for davila7/claude-code-templates/stripe-integration, and install it in one click.