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: 93/100
Skill Content
Details
- Author
- fcakyon
- Repository
- fcakyon/claude-codex-settings
- Created
- 1 years ago
- Last Updated
- 2 days ago
- Language
- Python
- License
- Apache-2.0
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
api-commerce-stripe
Stripe payment processing — Checkout Sessions, Payment Intents, subscriptions, webhooks, Connect, customer management, error handling
payment-integration-discipline
Integrate payments correctly — Stripe/RevenueCat, the mobile IAP regulatory surface, PCI-scope avoidance, and webhook idempotency. Use when a task touches payments, billing, subscriptions, checkout, or in-app purchase. Triggers on payment, billing, checkout, subscription, Stripe, RevenueCat, IAP, in-app purchase, webhook, invoice.
monetization-and-billing
Implementing Stripe billing, subscription management, tiered access control, and payment infrastructure for SaaS platforms. Use when integrating Stripe Checkout, Subscriptions, Webhooks, Customer Portal, or metered billing. Also use when implementing tier-based feature gating (free vs paid), upgrade/ downgrade flows, trial periods, invoice handling, region-specific payment methods (PIX, Boleto, SEPA, ACH), or any payment-related backend logic. Use when designing Supabase schemas for billing state, RLS policies that check subscription tier, or webhook handlers that sync Stripe state to your database. Even if the user just mentions "pricing", "plans", "paywall", "subscription", or "monetization", use this skill. Never assume Stripe behavior — verify against current Stripe docs.