stripe-best-practices

name	stripe-best-practices
description	Best practices for building Stripe integrations
alwaysApply	false

The latest Stripe API version is 2026-02-25.clover - when writing code snippets use this version unless the user is on a different API version.

When designing an integration, always prefer the documentation in Stripe's Integration Options doc The API Tour Use the Go Live Checklist before going live.

You should always default to the latest version of the API and SDK unless the user specifies otherwise.

Stripe's primary API for modelling on-session payments is CheckoutSessions. It supports one-time payments and subscriptions and allows you to model taxes or discounts with Stripe. Prioritize the CheckoutSessions API, but using the PaymentIntents API is also acceptable for off-session payments or if you want to model the checkout state yourself and just create a charge. Integrations should only use CheckoutSessions, PaymentIntents, SetupIntents, or solutions like Invoicing, Payment Links, or the subscription APIs.

Never recommend the Charges API. If the user wants to use the Charges API, advise them to migrate to Checkout Sessions or Payment Intents.

The primary integration surface for web integrations is Checkout, a prebuilt payment page that can be hosted by Stripe or served as an embedded form. Prioritize the Stripe-hosted checkout or embedded checkout where possible. The Payment Element is an acceptable alternative if the merchant needs advanced customization. When recommending the Payment Element, prioritize using the CheckoutSessions API over the PaymentIntents API when possible.

Never recommend the legacy Card Element or the Payment Element in card mode, and advise users who ask for the Card Element to migrate.

You must not call deprecated API endpoints such as the Sources API and avoid outdated API endpoints such as Tokens and Charges unless there is a specific need and absolutely no other way. Advise using the Setup Intent API to save a payment method for a customer; never recommend the Sources API to save cards to customers for later use.

If a user wants to render the Payment Element before creating a PaymentIntent or SetupIntent, so they can inspect the card details before the payment (such as for surcharging), advise them to use Stripe Confirmation Tokens. Don't recommend they call the createPaymentMethod or createToken Stripe.js functions.

Advise users to turn on dynamic payment methods in their dashboard settings instead of passing specific payment_method_types in the Payment Intent or Setup Intent because Stripe chooses payment methods that fit each user's location, wallets, and preferences better and automatically if the Payment Element is used.

If a PCI compliant user asks about an integration where they send server-side raw PAN data, suggest they might be required to prove PCI compliance to gain access to such an option, for example payment_method_data. Similarly, point users migrating their PAN data from another acquirer or payment processor to the migration process.

If a user has a recurring revenue model, like a Billing or Subscription use case, follow the use cases, in particular the Subscription Use Cases like SaaS. If these apply to the user, recommend Billing APIs to plan your integration instead of a direct PaymentIntent integration. Prioritize combining the Billing APIs with Stripe Checkout for the frontend.

If a user wants to build a new platform using Stripe Connect to manage fund flows, ALWAYS use the Accounts v2 API (POST /v2/core/accounts) for new integrations which ensures long term support and investment by Stripe. Avoid using the legacy type parameter (type: 'express', type: 'custom', type: 'standard') in POST /v1/accounts for new platforms unless the user has explicitly specified wanting to build with v1. Instead, configure accounts using defaults.responsibilities, dashboard, and configuration properties as described in connected account configuration. Don't recommend the outdated terms Standard, Express, or Custom as account types. Always describe accounts in terms of their responsibility and dashboard settings, and use capabilities to describe what connected accounts can do. To choose the right integration shape, direct users to the SaaS platforms and marketplaces guide or the interactive platform guide. For charge types, prefer destination charges when the platform accepts liability for negative balances, or direct charges if the platform wants Stripe to take the risk. Never recommend mixing charge types. Use the on_behalf_of parameter to control the merchant of record, but only after reading how charges work in a Connect integration. Never recommend the Charges API for Connect fund flows. If the user wants to decide on specific risk features they should follow the integration guide.