Stripe Checkout and Webhook Integration
Build Stripe checkout and subscriptions with verified webhooks, server-side pricing, retry safety, and payment-state reconciliation.
Before & after
Same prompt, same agent — the only difference is the skill.
Adding Stripe to an app is definitely doable in a week, but it depends on how complex your use case is. If you just need a simple checkout, that's pretty straightforward. If you need recurring billing, subscriptions, or custom workflows, that's more involved. What's your tech stack? Do you have a backend or is this a static site? Do you need one-time purchases or subscriptions? Once I know more details, I can point you in the right direction or help you sketch out the implementation.
STRIPE INTEGRATION ROADMAP (7 days) DAY 1: Setup → Create Stripe account and grab API keys → Install Stripe client library for your stack (Node/Express assumed) → Create environment file with publishable + secret keys DAY 2–3: Backend Wiring → Create /api/create-checkout-session endpoint (handles cart-to-Stripe conversion) → Create /api/webhook receiver (handles charge.paid, invoice.paid events) → Store session IDs and sync webhook events to your database DAY 4–5: Frontend Checkout → Install Stripe.js and the Stripe React library → Add a Checkout button that calls your session endpoint → Redirect to Stripe-hosted checkout on success → Handle return_url redirect with success/cancel pages DAY 6: Testing → Use Stripe test cards (4242 4242 4242 4242) → Verify webhook events fire on test charges → Check that your database syncs correctly DAY 7: Deploy → Move API keys to your production environment → Test one real charge with a small amount → Monitor webhook logs for 24 hours CRITICAL: Enable webhook event signing (verify the signature header) to prevent forged events.
About this skill
Checkout says success, but the account never upgrades. Or a webhook retry grants the same purchase twice. This skill builds the Stripe payment flow and the application state handling that make those outcomes predictable, from server-side checkout creation through verified events and recovery.
What it does
- Chooses hosted Checkout or Payment Element based on the actual payment and interface requirements.
- Builds authenticated server endpoints that derive prices and customer ownership from trusted application data.
- Maps one-time purchases and subscription events to explicit payment, billing, and access states.
- Handles signed webhooks, duplicate delivery, delayed payments, and interrupted processing.
- Prevents duplicate customers, checkout attempts, and fulfillment through database constraints and stable operation keys.
- Produces targeted test cases and a reconciliation path for payments that disagree with the application database.
What you get
Implementation code or a focused patch for your stack, plus the event-to-state mapping and tests needed to assess it. Reviews identify the failing transition, explain its consequences, and provide a concrete correction.
Best for
Developers adding their first Stripe checkout or subscription flow, and teams fixing unreliable payment webhooks or accounts that disagree with Stripe.
SKILL.md preview
---
name: stripe-checkout-and-webhook-integration
description: >-
Implement Stripe checkout, subscriptions, and database synchronization using server-authoritative pricing, signed webhooks, durable deduplication, and reconciliation. Use when the user says "add Stripe checkout", "set up subscriptions", "wire up Stripe webhooks", "my webhooks aren't working", "I'm getting duplicate events or orders", "my checkout succeeds but access never unlocks", "customers are getting charged twice", "my database disagrees with Stripe", or "review this Stripe integration".
---
# Stripe Checkout and Webhook Integration
… (sign up to view the full skill)More development skills
View all Development skills →Production Go: Concurrency, Services & Profiling
Production Go code with leak-free goroutines, context-correct services, wrapped errors, and pprof-driven performance fixes.
Backend Feature Build Plan
Builds one backend feature through gates: confirmed requirements, one-screen design, small tested slices, and a deploy/rollback handoff.
Consistent, Safe Application Logging
Adds structured, correlated logs with useful severity, safe fields, bounded volume, and targeted verification.
Reliable WebSocket Messaging and Scaling
Build WebSocket and Socket.IO systems with authorized rooms, reconnect recovery, bounded queues, and multi-node presence.