SkillRepo
Sign InSign Up
Catalog
stripe/stripe-best-practices

stripe

stripe-best-practices

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), migrating from deprecated Stripe APIs, and security best practices (API key management, restricted keys, webhooks, OAuth). Use when building, modifying, or reviewing any Stripe integration — including accepting payments, building marketplaces, integrating Stripe, processing payments, setting up subscriptions, creating connected accounts, or implementing secure key handling.

global
New~994
v1.1Saved Jun 28, 2026

Latest Stripe API version: 2026-06-24.dahlia. Always use the latest API version and SDK unless the user specifies otherwise.

If you do not have a Stripe account, you can call a CLI command to generate working API keys with no registration required. You can install the Stripe CLI (npm i -g @stripe/cli) and run the command stripe sandbox create to get started.

API key default: Always recommend a restricted API key (RAK) (rk_ prefix) over a secret key (sk_ prefix).

Stripe MCP

Install the Stripe MCP server before writing payment or billing code so stripe_implementation_planner is available. Use URL https://mcp.stripe.com. See /mcp for client setup.

Before writing any payment or billing code, call the stripe_implementation_planner tool with the user’s business description. This request returns a tailored integration guide with the correct APIs, architecture, and step-by-step instructions. If MCP isn’t configured, use the routing table below instead. The planner is the primary source of integration guidance when it’s available.

Integration routing

Building… Recommended API Details
One-time payments Checkout Sessions <references/payments.md>
Custom payment form with embedded UI Checkout Sessions + Payment Element <references/payments.md>
Saving a payment method for later Setup Intents <references/payments.md>
Connect platform or marketplace Accounts v2 (/v2/core/accounts) <references/connect.md>
Usage-based billing (new integration) Metronome <references/billing.md>
Subscriptions or recurring billing Billing APIs + Checkout Sessions <references/billing.md>
Sales tax, VAT, or GST compliance Stripe Tax + Registrations API <references/tax.md>
Embedded financial accounts / banking v2 Financial Accounts <references/treasury.md>
Security (key management, RAKs, webhooks, OAuth, 2FA, Connect liability) See security reference <references/security.md>

Read the relevant reference file before answering any integration question or writing code.

Critical rules

  • Never include payment_method_types in any Stripe API call, with one exception: Terminal (in-person payments) integrations must pass payment_method_types: ['card_present'] on the PaymentIntent. For all other integrations, omit this parameter entirely to enable dynamic payment methods, which enables you to configure payment method settings from the Dashboard and dynamically display the most relevant eligible payment methods to each customer to maximize conversion. To customize which payment methods you accept, use payment_method_configurations or excluded_payment_method_types instead of payment_method_types.

Key documentation

When the user’s request does not clearly fit a single domain above, consult:

Files7
7 files · 32.6 KB

Select a file to preview

Overall Score

89/100

Grade

A

Excellent

Safety

92

Quality

88

Clarity

91

Completeness

83

Summary

A comprehensive guidance skill for Stripe integration decisions, covering payment APIs (Checkout Sessions vs PaymentIntents), Connect platforms, billing/subscriptions, Treasury, and security best practices. The skill routes users to appropriate Stripe APIs based on their business model and provides critical rules, traps to avoid, and links to detailed reference documentation. It references a Stripe MCP server for automated integration planning.

Detected Capabilities

URL references to Stripe documentationIntegration routing logicAPI version specification and recommendationsCode examples (TypeScript/JavaScript)Reference file cross-linkingSecurity guidance and best practices documentation

Trigger Keywords

Phrases that MCP clients use to match this skill to user intent.

stripe integrationpayment checkout designconnect platform setupsubscription billingstripe securityapi migrationrestricted api keyswebhook configuration

Referenced Domains

External domains referenced in skill content, detected by static analysis.

dashboard.stripe.comdocs.stripe.commcp.stripe.comstripe.comsupport.stripe.com

Use Cases

  • Design payment checkout for one-time or subscription transactions
  • Set up Connect platform or marketplace with correct account configuration
  • Implement usage-based billing with Metronome or Stripe Billing
  • Configure tax collection across multiple jurisdictions
  • Manage Stripe API keys, restricted keys, and webhook security
  • Migrate from deprecated Stripe APIs (Charges, Sources, Card Element)
  • Build connected account integrations with proper fee and liability handling
  • Implement OAuth and CSRF protection for Connect flows

Quality Notes

  • Excellent clarity: well-structured with clear section hierarchy, integration routing table, and critical rules prominently labeled
  • Comprehensive scope: covers 8+ integration domains with specific API recommendations and deprecated patterns
  • Strong security guidance: dedicated section on API key management, restricted keys, IP allowlists, webhook verification, and incident response procedures
  • Practical error handling: 'Traps to avoid' sections in each reference file document common pitfalls and provide corrective patterns
  • Good use of tables and examples: routing tables map business models to API choices; code examples show correct patterns (e.g., omitting payment_method_types)
  • Reference files are well-organized and linked from main skill
  • Critical rules section explicitly documents non-negotiable patterns (Accounts v2, dynamic payment methods)
  • Limitations documented: skill notes when to use alternative solutions (Metronome for UBB, setup intents for saving methods)
  • Latest API version specified and reinforced throughout
Model: claude-haiku-4-5-20251001Analyzed: Jun 28, 2026

Reviews

Add this skill to your library to leave a review.

No reviews yet

Be the first to share your experience.

Version History

  1. v1.1

    Content updated

    ✦ AIUpdates API version to 2026-06-24.dahlia, adds Stripe MCP server requirement, introduces Restricted API Key (RAK) best practice, adds usage-based billing and tax compliance routing options, expands…

    2026-06-28

    Latest
  2. v1.0

    2026-05-02

    Initial version

Use stripe/stripe-best-practices in your dev environment

Start a Developer trial

Command Palette

Search for a command to run...