stripe-best-practices

Guide Stripe integrations toward Checkout Sessions and current APIs.

33.3k|3.8k|Updated Nov 20, 2025
One-click install
npx skills add https://github.com/anthropics/claude-plugins-official --skill stripe-best-practices
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: stripe-best-practices
Source: https://github.com/anthropics/claude-plugins-official/tree/main/external_plugins/stripe/skills/stripe-best-practices
Command: npx skills add https://github.com/anthropics/claude-plugins-official --skill stripe-best-practices

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured approach to implementing Stripe integrations by following official best practices, ensuring you avoid deprecated APIs, minimize risk, and accelerate secure payments.

Core Features & Use Cases

  • API best practices: Use the latest API version by default and choose the recommended API surface (Checkout Sessions for on-session payments, PaymentIntents for off-session scenarios, and SetupIntents to save payment methods).
  • Migration guidance: Avoid the Charges API and migrate to Checkout Sessions or PaymentIntents when appropriate; use the migration path for PAN data if needed.
  • Platform design: For Stripe Connect and SaaS billing use cases, prefer Checkout with Billing APIs and On-behalf-of patterns for platform platforms.
  • Security & compliance: Turn on dynamic payment methods where possible and rely on Stripe's PCI-compliant flows.

Quick Start

Use the stripe-best-practices skill to design a Stripe integration using Checkout Sessions by default, enable dynamic payment methods, avoid deprecated endpoints, and migrate any Charges usage to Checkout or PaymentIntents.

Frequently Asked Questions about stripe-best-practices

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

FAQPage Schema
What's the best way to set up a Stripe payment integration?

Stripe payment integrations should default to Checkout Sessions for on-session payments, PaymentIntents for off-session scenarios, and SetupIntents for saving payment methods. Enable dynamic payment methods and use the latest API version to minimize security risk and avoid deprecated endpoints.

Should I use the Charges API or migrate to Checkout Sessions?

Migrate away from the Charges API to Checkout Sessions or PaymentIntents. Checkout Sessions is recommended for most payment flows, while PaymentIntents better suits custom checkout states and off-session payments. Migration ensures compliance with current best practices.

How do I handle payment method storage securely with Stripe?

Use SetupIntents to save payment methods instead of deprecated approaches. Enable dynamic payment methods to let Stripe select the optimal payment type per region. This approach relies on Stripe's PCI-compliant flows, reducing your compliance burden.

What should I know before going live with a Stripe integration?

Before live deployment, verify you're using Checkout Sessions or PaymentIntents, enable dynamic payment methods, disable the Charges API, and confirm your integration follows PCI compliance guidelines. The stripe-best-practices guidance covers readiness checks for production.

How do I build a Stripe Connect platform or SaaS billing system?

For Stripe Connect and SaaS platforms, prefer Checkout with Billing APIs and On-behalf-of patterns. These approaches streamline subscription management and ensure compliance across your platform architecture.