stripe-integration

Implement Stripe payment flows with Payment Intents, subscriptions, and webhook handling.

3|1|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/tomtoto757/ecomm-ai-team --skill stripe-integration-tomtoto757
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: stripe-integration
Source: https://github.com/tomtoto757/ecomm-ai-team/tree/main/skills/checkout-payments-tax/finsilabs/payments-checkout/stripe-integration
Command: npx skills add https://github.com/tomtoto757/ecomm-ai-team --skill stripe-integration-tomtoto757

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires stripe, @stripe/stripe-js, @stripe/react-stripe-js.

What problem does it solve? Adding payment processing to an ecommerce store involves PCI compliance, European SCA requirements, webhook reliability, and platform-specific configuration. This Skill provides step-by-step guidance for integrating Stripe across Shopify, WooCommerce, BigCommerce, and custom headless storefronts without common implementation mistakes. ## Core Features & Use Cases - Platform Setup Guides: Configure Stripe on Shopify (via Shopify Payments), WooCommerce (official plugin), and BigCommerce with the correct API keys, payment methods, and webhook registration. - Custom Checkout Code: Production-ready examples for Stripe Checkout hosted sessions and Payment Intents with Stripe Elements, including SCA-compliant 3D Secure handling via automatic_payment_methods. - Webhook Fulfillment: Signature-verified webhook handlers with idempotency checks for payment_intent.succeeded, payment failures, refunds, and disputes. - Use Case: A headless storefront needs to accept card payments from European customers. Use this Skill to create a Payment Intent with order metadata, render a Stripe Elements form, and fulfill orders through a verified webhook endpoint instead of relying on browser redirects. ## Quick Start Use the stripe-integration skill to add a Payment Intents checkout flow with webhook-based order fulfillment to my Express backend.

Frequently Asked Questions about stripe-integration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I integrate Stripe payments into a custom website?▼

Create a Payment Intent server-side with stripe.paymentIntents.create() using automatic_payment_methods enabled, return the client_secret, and confirm payment client-side with Stripe Elements and stripe.confirmPayment(). Use Stripe Checkout hosted pages for the fastest integration without building a payment form.

How to set up Stripe on WooCommerce?▼

Install the free WooCommerce Stripe Payment Gateway plugin, enter your publishable and secret keys from the Stripe Dashboard, and enable express checkout methods like Apple Pay and Google Pay. The plugin automatically registers the required webhook endpoint with Stripe.

Does Stripe handle SCA and 3D Secure for European customers?▼

Yes, setting automatic_payment_methods: { enabled: true } on Payment Intents automatically triggers 3D Secure challenges when the customer's bank requires them. No additional configuration is needed for SCA compliance.

Why does Stripe webhook signature verification fail?▼

Verification fails when the request body is parsed as JSON before verification. Pass the raw unparsed body buffer to stripe.webhooks.constructEvent() along with the stripe-signature header and your webhook secret, and configure your framework to skip JSON parsing on the webhook route.

Should I use Payment Intents or the Charges API?▼

Always use Payment Intents for new integrations. The legacy Charges API does not support SCA and is not recommended; Payment Intents handle authentication, multiple payment methods, and asynchronous confirmation flows.

Why is my Stripe payment succeeded but the order not confirmed?▼

Webhooks are the authoritative fulfillment signal, not the client-side redirect, since customers can close the browser before redirecting. Check your webhook handler logs in Stripe Dashboard under Developers, Webhooks, and ensure handlers are idempotent against duplicate event delivery.