stripe-best-practices

Guide Stripe API surface and architecture decisions for integrations.

Updated Feb 17, 2026
One-click install
npx skills add https://github.com/Fabianrzs/car-wash --skill stripe-best-practices-fabianrzs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: stripe-best-practices
Source: https://github.com/Fabianrzs/car-wash/tree/main/.agents/skills/stripe-best-practices
Command: npx skills add https://github.com/Fabianrzs/car-wash --skill stripe-best-practices-fabianrzs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

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.

Core Features & Use Cases

  • API routing guidance for choosing the correct Stripe surface (Checkout Sessions, PaymentIntents, SetupIntents, Accounts v2)
  • Connect platform setup and accounts v2 configuration
  • Billing and subscriptions design patterns
  • Treasury/Financial Accounts guidance for platforms
  • Guidance on integration surfaces (Checkout, Payment Element) and migrating from deprecated APIs
  • Practical decision framework for building, reviewing, or extending Stripe integrations

Quick Start

Review the integration routing table to select the recommended Stripe API path for your use case.

Frequently Asked Questions about stripe-best-practices

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

FAQPage Schema
When should I use Stripe Checkout Sessions instead of PaymentIntents?

Use Stripe Checkout Sessions for pre-built, hosted payment flows, and PaymentIntents when you need a custom, client-side integration surface. This routing guidance helps you select the correct API path for your specific billing and payment architecture requirements.

How do I set up Stripe Connect accounts for a marketplace?

Configure Stripe Connect accounts using the Accounts v2 API surface and controller properties. This setup provides the necessary architecture for multi-tenant marketplaces to process payments and manage treasury workflows for connected accounts.

What is the best way to migrate from deprecated Stripe APIs?

Migrate from deprecated Stripe APIs by following the integration routing framework to select current API surfaces like Checkout Sessions, PaymentIntents, or Accounts v2. This ensures your payment and subscription workflows avoid deprecated functionality.

Can I use this Stripe integration guidance for subscription billing patterns?

Yes, this guidance applies to designing and modifying subscription and billing patterns. It provides a practical decision framework for selecting the correct API surfaces to handle recurring payments and setup intents within your integration.

Does this guidance cover setting up Stripe Treasury financial accounts?

Yes, this guidance includes Treasury and Financial Accounts setup for platforms. It helps you navigate the architecture required to manage funds and treasury workflows across multi-tenant or marketplace scenarios using Stripe.