stripe-best-practices

Guide Stripe payment and subscription integrations toward supported APIs and checkout flows.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents costly Stripe integration mistakes by steering you toward modern, supported APIs and recommended flows for payments, saving payment methods, and checkout experiences.

Core Features & Use Cases

  • API and architecture guidance: Recommends CheckoutSessions for most on-session payment flows, with PaymentIntents/SetupIntents for off-session or custom state needs, and guidance for when to use Billing/subscriptions.
  • Safer integration practices: Avoids deprecated endpoints (including Charges/Sources/Tokens) and discourages legacy UI components that require migration.
  • Frontend checkout recommendations: Prioritizes Stripe-hosted/embedded Checkout and the Payment Element (when applicable) while covering edge cases like surcharging and when to use Confirmation Tokens.
  • Connect platform considerations: Guides Connect integration type selection and discourages mixing charge types while emphasizing current controller properties.

Quick Start

Ask your AI assistant to review your proposed Stripe payment or subscription integration plan and rewrite it to follow the Stripe best-practice guidelines in this skill (including which APIs to use, which deprecated options to avoid, and what checkout approach to recommend).

Frequently Asked Questions about stripe-best-practices

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

FAQPage Schema
What is the best way to build a Stripe checkout integration?

For off-session payments or saving payment methods without immediate charges, use SetupIntents to securely collect payment details for future use. Use PaymentIntents only when you need custom state management beyond standard Checkout flows.

Which deprecated Stripe APIs should I avoid when building a payment flow?

When building a payment flow, avoid deprecated Stripe APIs including the legacy Charges, Sources, and Tokens endpoints. You should also migrate away from legacy UI components and use modern supported APIs like PaymentIntents instead.

How do I set up Stripe Connect for a platform with multiple sellers?

To set up Stripe Connect, select the appropriate integration type for your platform and use current controller properties. Avoid mixing different charge types within your application to maintain a clean and safe architecture.

When do I need Confirmation Tokens or surcharging in Stripe?

You need Confirmation Tokens in Stripe for specific edge cases within custom checkout flows, while surcharging applies when you must add extra fees to transactions. Use these alongside the Payment Element when applicable.