stripe-best-practices

Estrelas4.748

Forks636

Atualizado21 de abril de 2026 às 18:07

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), and migrating from deprecated Stripe APIs. Use when building, modifying, or reviewing any Stripe integration — including accepting payments, building marketplaces, integrating Stripe, processing payments, setting up subscriptions, or creating connected accounts.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Fonte

openai

openai/plugins

Abrir repositório GitHub Ver repositórios do creator

Download

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores de softwareInformática e Matemática·SOC 15-1252

Explorador de arquivos

6 arquivos

SKILL.md

readonly

Mais deste repositório

mesmo repositório

figma-design-to-code

openai/plugins

Use this skill when implementing a Figma design as code (design → code) — the read-FROM-Figma direction. Triggers: 'implement this Figma design', 'build this screen from Figma', 'turn this Figma into code', 'code this up from Figma', 'design to code', or a figma.com design URL provided alongside a codebase. Encodes the workflow for reading a node out of Figma with get_design_context and adapting its reference output to the target project — reusing existing components, tokens, and conventions, and honoring Code Connect mappings, component docs, design annotations, and design tokens by priority. Complements figma-code-connect (component mapping) and figma-generate-design / figma-use (the reverse, code → design direction).

2026-07-094.7k

attack-path-analysis

openai/plugins

Use when Codex is already in the attack-path-analysis phase of a security scan or the user explicitly asks to trace a security finding from source to sink and calibrate severity. Do not use as the primary trigger for full PR, commit, branch, patch, or repository scans.

2026-07-094.7k

deep-security-scan

openai/plugins

Use when the user asks for a deep, exhaustive, multi-pass, or variance-reducing repository-wide or scoped-path Codex Security scan. Run repeated independent discovery passes over one resolved scope with worker-specific threat models, semantically merge candidates, synthesize one canonical validation threat model, then run validation, attack-path analysis, canonical JSON completion, and generated reporting once. Do not use for PRs, commits, branch diffs, or working-tree diffs.

2026-07-094.7k

finding-discovery

openai/plugins

Use when Codex is already in the finding-discovery phase of a security scan or the user explicitly asks to discover candidate security findings in a repository or code change. Do not use as the primary trigger for full PR, commit, branch, patch, or repository scans.

2026-07-094.7k

fix-finding

openai/plugins

Use when the user explicitly asks to fix and verify a validated or plausible security finding. Do not use as the primary trigger for full PR, commit, branch, patch, or repository scans.

2026-07-094.7k

propose-security-hardening

openai/plugins

Develop evidence-backed structural and architectural security hardening proposals from vulnerability disclosures, supplied findings, incident or assessment documents, source code, or a completed Codex Security scan. Use when a user asks for systemic improvements, alternatives beyond per-finding patches, before-and-after security architecture views, engineering tradeoff analysis, or an implementation-ready plan for a selected hardening option. Also use automatically after a Codex Security scan with reportable findings when the top-level scan workflow requests final-report hardening guidance.

2026-07-094.7k

name

stripe-best-practices

description

Latest Stripe API version: 2026-02-25.clover. Always use the latest API version and SDK unless the user specifies otherwise.

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
Subscriptions or recurring billing	Billing APIs + Checkout Sessions	references/billing.md
Embedded financial accounts / banking	v2 Financial Accounts	references/treasury.md

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

Key documentation

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

Integration Options — Start here when designing any integration.
API Tour — Overview of Stripe's API surface.
Go Live Checklist — Review before launching.