stripe-best-practices

Map business requirements to current Stripe v2 API endpoints for payment flows.

2|Updated Mar 29, 2026
One-click install
npx skills add https://github.com/NagyVikt/codex-plugins --skill stripe-best-practices-nagyvikt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: stripe-best-practices
Source: https://github.com/NagyVikt/codex-plugins/tree/main/plugins/build-web-apps/skills/stripe-best-practices
Command: npx skills add https://github.com/NagyVikt/codex-plugins --skill stripe-best-practices-nagyvikt

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill eliminates the complexity and risk associated with choosing the wrong Stripe API, ensuring developers implement modern, compliant, and scalable payment architectures.

Core Features & Use Cases

  • Integration Routing: Provides clear decision paths for choosing between Checkout Sessions, PaymentIntents, and Connect APIs based on business requirements.
  • Best Practice Enforcement: Prevents the use of deprecated APIs like Charges or Sources, guiding users toward modern alternatives like the Payment Element and Setup Intents.
  • Use Case: When building a new marketplace, use this skill to correctly configure Connect accounts using the v2 API and controller properties instead of legacy account types.

Quick Start

Use the stripe-best-practices skill to determine the correct API implementation for a new subscription-based SaaS platform.

Frequently Asked Questions about stripe-best-practices

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

FAQPage Schema
How do I choose between Stripe Checkout Sessions and PaymentIntents for my billing flow?

Stripe integration routing selects between Checkout Sessions, PaymentIntents, and Connect APIs by mapping your specific business requirements to the most secure and scalable payment flow design.

What is the best way to set up Stripe recurring subscriptions and one-time charges?

Design Stripe payment flows by standardizing integration patterns for one-time charges and recurring subscriptions, enforcing modern API endpoints to ensure PCI compliance and platform stability.

Why should I use Stripe Payment Elements and Setup Intents instead of deprecated APIs?

Using deprecated Stripe Charges or Sources APIs risks compliance; enforcing best practices guides you toward modern alternatives like the Payment Element and Setup Intents for secure, scalable architectures.

How do I configure Stripe Connect for a multi-party marketplace platform?

Configure Stripe Connect accounts for multi-party marketplaces by using the modern v2 API and controller-based account management properties instead of legacy account types to ensure long-term stability.

Does this approach support building a subscription-based SaaS platform with Stripe?

Yes, standardizing Stripe integration patterns supports new subscription-based SaaS platforms by determining the correct API implementation, ensuring modern, compliant, and scalable payment architectures.