stripe-best-practices

Guide Stripe API choices, Connect setup, and security patterns.

1|Updated Feb 6, 2026
One-click install
npx skills add https://github.com/gepetojj/umo --skill stripe-best-practices-gepetojj
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: stripe-best-practices
Source: https://github.com/gepetojj/umo/tree/main/.agents/skills/stripe-best-practices
Command: npx skills add https://github.com/gepetojj/umo --skill stripe-best-practices-gepetojj

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Stripe integration decisions can be complex and error-prone; this Skill provides structured guidance on API choices, Connect setup, billing strategies, treasury usage, and security considerations to streamline integration planning and reduce risk.

Core Features & Use Cases

  • API surface guidance for Checkout Sessions vs PaymentIntents, Accounts v2, and billing flows.
  • Migration guidance for deprecated Stripe APIs and recommended modern patterns.
  • Security best practices covering API keys, restricted keys, webhooks, and OAuth for secure integrations.
  • Use Case: Architect and implement Stripe-powered apps for marketplaces, subscriptions, and treasury-enabled flows.

Quick Start

Describe the optimal Stripe integration approach for a new project, including API surface, Connect configuration, and security posture.

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 choose between Stripe Checkout Sessions and PaymentIntents?

Stripe integration API surface selection depends on your control requirements. Checkout Sessions provide pre-built, Stripe-hosted payment flows, while PaymentIntents allow developers to build custom payment experiences and manage complex transaction workflows directly within their application.

How do I configure Stripe Connect Accounts v2 for a marketplace platform?

Configuring Stripe Connect Accounts v2 involves structuring your marketplace integration to route payments between buyers, sellers, and the platform. This requires selecting the correct account type and routing logic to handle multi-party transactions and ensure accurate fund distribution.

What security patterns should I follow for Stripe API key management and webhooks?

Stripe security best practices mandate using restricted API keys for specific permissions, implementing secure key storage, and verifying webhook signatures. These patterns prevent unauthorized access and ensure your application only processes authentic Stripe events.

How do I migrate deprecated Stripe APIs to modern integration patterns?

Migrating deprecated Stripe APIs requires identifying legacy endpoints and transitioning to supported modern patterns like Checkout Sessions or PaymentIntents. Structured migration guidance helps developers phase out outdated integrations while maintaining operational continuity and reducing misconfigurations.

Does this Stripe integration guidance cover billing and subscription flows?

Yes, this guidance covers Stripe billing and subscription flows, including API surface selection for recurring payments. It helps developers architect subscription-based applications by specifying requirements for integrating billing cycles, invoicing, and treasury-enabled flows.