Back to Skills

stripe-best-practices

Guides Stripe integration decisions — API selection (Checkout Sessions vs PaymentIntents), Connect platform setup (Accounts v2, controller properties), billing/subscriptions, Treasury financial accounts, integration surfaces (Checkout, Payment Element), migrating from deprecated Stripe APIs, and security best practices (API key management, restricted keys, webhooks, OAuth). Use when building, modifying, or reviewing any Stripe integration — including accepting payments, building marketplaces, in

1,504stars257forksUpdated 4/25/2026

Security Assessment

Safe(100/100)
Security Score100/100

About stripe-best-practices

The `stripe-best-practices` skill provides comprehensive guidance for integrating Stripe payment solutions effectively and securely. It helps developers and technical teams make informed decisions regarding API selection, platform setup, subscription management, financial account handling, and security practices. By consolidating best practices for both new integrations and legacy migrations, this skill reduces the risk of implementation errors, ensures compliance with Stripe's evolving APIs, and streamlines the overall integration process.

This skill covers a wide range of capabilities including selecting between Checkout Sessions and PaymentIntents for one-time or recurring payments, configuring Connect platforms with Accounts v2, managing billing and subscription workflows, and handling embedded financial accounts through Treasury APIs. It also provides guidance on implementing secure integration surfaces such as Payment Elements, setting up webhooks, managing API keys, using restricted access keys (RAKs), and following OAuth and two-factor authentication best practices. Each integration type includes references to detailed documentation to ensure developers follow Stripe's recommended patterns.

`stripe-best-practices` is particularly useful for developers building marketplaces, subscription services, or platforms that require connected accounts and recurring billing. It is also valuable for teams reviewing existing integrations for security or compliance improvements. Target users include software engineers, technical leads, and consultants working with payment processing or financial services who need a clear, structured approach to integrating Stripe APIs while maintaining best-in-class security and operational practices.

FAQ

Which Stripe API should I use for a one-time payment?

For one-time payments, the recommended API is Checkout Sessions. Consult the payments reference documentation for implementation details.

Can this skill guide me on Connect platform setup?

Yes, it provides guidance on setting up Connect platforms using Accounts v2 and relevant controller properties.

Is this skill compatible with the latest Stripe API version?

The skill is aligned with Stripe API version 2026-03-25.dahlia. Always use the latest API version unless a specific version is required.

Does this skill cover subscription management?

Yes, it includes best practices for subscriptions and recurring billing using Stripe Billing APIs along with Checkout Sessions.

Are there security considerations included in this skill?

Absolutely. It covers API key management, restricted keys, webhooks, OAuth, and two-factor authentication to help maintain secure integrations.

All Files

6 files
references/security.md7.7 KB
View
references/billing.md1.3 KB
View
references/connect.md3.0 KB
View
references/treasury.md0.8 KB
View
references/payments.md4.4 KB
View
SKILL.md2.6 KB
View

Install stripe-best-practices

Download and extract the skill files to your .claude/skills/ directory.

Quick Setup:

  1. Copy the skill folder to .claude/skills/
  2. Claude will automatically detect and use the skill

Repository

stripe/ai