stripe-best-practices
por ifoster01
TransportationResumen
Best practices for building Stripe payment integrations.
Descripción
Qué hace esta skill
A knowledge skill that encodes Stripe's recommended integration patterns, deprecated API warnings, and decision rules for payments, subscriptions, and Connect platforms. It guides agents toward current Stripe APIs and away from legacy ones like Charges API, Card Element, and Sources API.
Encoding these rules in a skill prevents agents from defaulting to outdated Stripe APIs that Stripe itself recommends against, which can cause compliance issues and integration debt.
Cuándo usarla
- Choosing between CheckoutSessions and PaymentIntents for a new checkout flow
- Setting up recurring billing for a SaaS product
- Migrating an existing integration off the deprecated Charges API
- Building a marketplace with Connect and selecting the right charge type
- Saving a customer payment method without an immediate charge
Flujo de trabajo de ejemplo
User asks: I want to add subscription billing to my SaaS app
- 1
Identifies recurring revenue use case and applies Billing APIs preference
- 2
Recommends Stripe Billing APIs combined with Checkout frontend
- 3
Advises against raw PaymentIntents for subscription management
- 4
Suggests Stripe-hosted Checkout as the default frontend unless more control is needed
- 5
References stripe:billing/design-integration for integration planning
A recommended integration approach using Stripe Billing APIs and Checkout, with links to relevant Stripe docs
Requisitos
- Stripe account
- Stripe API keys
Instalación
clawhub install ifoster01/stripe-best-practicesEjecuta el comando de la CLI o pega el prompt en Claude Code, Cursor, Codex o el agente de programación que uses.