stripe-best-practices

Guides Stripe API selection and integration decisions across payments, Connect, billing, and Treasury.

Updated Jul 31, 2026
One-click install
npx skills add https://github.com/AarnavBaddam/skills --skill stripe-best-practices-aarnavbaddam
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: stripe-best-practices
Source: https://github.com/AarnavBaddam/skills/tree/main/stripe-best-practices
Command: npx skills add https://github.com/AarnavBaddam/skills --skill stripe-best-practices-aarnavbaddam

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Choosing the wrong Stripe API leads to deprecated integrations, compliance issues, and costly rewrites. This Skill routes every Stripe integration question to the current recommended API and flags deprecated patterns before they reach production. ## Core Features & Use Cases - API Routing: Maps integration goals (one-time payments, subscriptions, marketplaces, embedded banking) to the correct Stripe API such as Checkout Sessions, PaymentIntents, Accounts v2, or v2 Financial Accounts. - Deprecation Guardrails: Identifies legacy patterns like the Charges API, Sources API, Card Element, and v1 Connect account types, then points to migration paths. - Use Case: When building a marketplace, the Skill directs you to Connect Accounts v2 with controller properties instead of legacy account types, and recommends destination charges with PaymentIntents. ## Quick Start Ask how to accept subscription payments with Stripe and get routed to the Billing APIs with Checkout Sessions.

Frequently Asked Questions about stripe-best-practices

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

FAQPage Schema
Should I use Checkout Sessions or PaymentIntents for Stripe payments?

Use Checkout Sessions for on-session payments since it handles taxes, discounts, shipping, and subscriptions automatically. Use PaymentIntents for off-session payments or when you need to model checkout state independently and just create a charge.

How do I set up Stripe Connect for a marketplace?

Use the Accounts v2 API (POST /v2/core/accounts) with controller properties for losses, fees, dashboard access, and requirement collection. Avoid legacy account types like Standard, Express, or Custom, and pick one charge type such as destination charges.

Is the Stripe Charges API deprecated?

The Charges API should never be used for new integrations. Migrate to Checkout Sessions or PaymentIntents, which are Stripe's actively supported paths for creating charges.

How do I save a customer's card for later with Stripe?

Use the Setup Intents API to save a payment method for future use. Do not use the deprecated Sources API or Tokens API for attaching cards to customers.

Which Stripe API should I use for subscriptions?

Use the Billing APIs combined with Checkout Sessions in subscription mode, which handles trials, proration, renewals, and dunning automatically. Avoid building manual renewal loops with raw PaymentIntents and use Prices instead of the deprecated plan object.

Can I use v1 Treasury financial accounts for a new integration?

No, new integrations must use the v2 Financial Accounts API (POST /v2/core/vault/financial_accounts). Existing v1 Treasury integrations continue to work but should not be extended.