stripe-best-practices
FeaturedGuides 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, integrating Stripe, processing payments, setting up subscriptions, creating connected accounts, or implementing secure key handling.
Install
Quality Score: 94/100
Skill Content
Details
- Author
- fcakyon
- Repository
- fcakyon/claude-codex-settings
- Created
- 1 years ago
- Last Updated
- today
- Language
- Python
- License
- Apache-2.0
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
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), and migrating from deprecated Stripe APIs. Use when building, modifying, or reviewing any Stripe integration — including accepting payments, building marketplaces, integrating Stripe, processing payments, setting up subscriptions, or creating connected accounts.
stripe-best-practices
Best practices for building Stripe integrations. Covers payment processing, checkout flows, subscriptions, webhooks, Connect platforms, and Stripe API usage.
integration
Use this FIRST for ANY Stripe integration to pick the right approach before writing code. Router that classifies the ask (accept a one-time payment, subscriptions/recurring/invoicing, in-person/POS, marketplace/platform payouts, fraud/identity/bank-linking) and routes to the correct sibling skill and integration surface (Payment Links, Checkout, Elements, mobile/Terminal SDKs). Triggers — "Stripe", "accept a payment", "PaymentIntent", "checkout", "subscription/recurring/plan/trial/metered billing", "invoice", "marketplace/platform/Connect/split funds/payout", "Terminal/card reader/POS/Tap to Pay", "webhook/Stripe-Signature", "test cards/Stripe CLI", "publishable/secret/restricted key", "idempotency key". API version pinned 2026-06-24.dahlia.