stripe-integration

Stripe payment processing in Next.js requires installing Stripe libraries, configuring environment variables with your API keys, and implementing webhook routes with raw-body verification for secure event handling. This Skill provides templates for checkout sessions, customer handling, and subscription lifecycle management across your client-server architecture.

Secure webhook processing requires signature validation using Stripe's signing secret, raw-body access for verification, and idempotent handling to prevent duplicate event processing. This Skill covers webhook route setup, signature validation patterns, and safe event processing for subscription and payment events.

Subscription management with Stripe involves creating checkout sessions with price IDs, validating prices server-side, handling subscription lifecycle events through webhooks, and maintaining customer records. This Skill provides patterns for end-to-end subscription flows including setup, updates, and cancellation events.

Yes. Next.js API routes work with Stripe webhooks when you configure raw-body middleware, validate signatures against Stripe's signing secret, and implement idempotent event handling. This Skill includes webhook route templates designed for Next.js server-side patterns.

Critical security requirements include environment variable configuration for API keys, raw-body webhook verification to prevent tampering, signature validation, safe price ID validation, and Stripe API versioning consistency. This Skill enforces these patterns to prevent common integration vulnerabilities.

Raw-body access is essential because Stripe signature validation requires the exact request body bytes received from Stripe's servers. If the body is parsed or modified before verification, the signature check fails and webhooks become unverifiable. This Skill ensures raw-body handling is configured correctly.