stripe-best-practices

Guide Stripe integrations with CheckoutSessions, webhooks, and PCI compliance.

Updated Aug 6, 2025
One-click install
npx skills add https://github.com/fabiano001/claude-config --skill stripe-best-practices-fabiano001
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: stripe-best-practices
Source: https://github.com/fabiano001/claude-config/tree/main/plugins/marketplaces/claude-plugins-official/external_plugins/stripe/skills/stripe-best-practices
Command: npx skills add https://github.com/fabiano001/claude-config --skill stripe-best-practices-fabiano001

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides engineers with best-practice guidance for implementing Stripe integrations, helping avoid common pitfalls and ensuring secure, scalable payment experiences.

Core Features & Use Cases

  • Prioritize CheckoutSessions for on-session payments and use PaymentIntents or SetupIntents for off-session or complex flows.
  • Avoid deprecated endpoints like the Charges API and ensure PCI compliance and secure handling of payment data.
  • Cover webhooks, subscriptions, Connect platforms, and cross-cutting concerns such as go-live readiness and API versioning.

Quick Start

Follow Stripe's integration options and implement CheckoutSessions-first flows with safe defaults.

Frequently Asked Questions about stripe-best-practices

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

FAQPage Schema
What is the best way to implement Stripe checkout flows and payment integrations?

Stripe integration best practices recommend prioritizing CheckoutSessions for on-session payments and using PaymentIntents or SetupIntents for off-session flows to ensure secure, scalable payment experiences.

How do I handle Stripe webhooks and subscriptions safely?

To handle Stripe webhooks and subscriptions safely, follow established best practices that specify required API surfaces, avoid deprecated endpoints, and recommend secure patterns for managing recurring billing and event processing.

Does this guidance cover building Stripe Connect platforms?

Yes, this guidance applies established best practices to Stripe Connect platforms, ensuring safe and scalable integrations for marketplace payment workflows and multi-party routing.

Why should I avoid the deprecated Stripe Charges API in my payments integration?

You should avoid the deprecated Stripe Charges API to ensure PCI compliance and secure handling of payment data, relying on current required API surfaces and secure integration patterns instead.

What do I need to know about Stripe API versioning and go-live readiness?

For Stripe API versioning and go-live readiness, you must follow cross-cutting best practices specifying required API surfaces and safety constraints to ensure your production integration is fully prepared.