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), 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.

Jump to install

Repository: openai/plugins
Last source activity: April 21, 2026 at 18:07
Detected SKILL.md language: English
Stars: 7,086
Forks: 916

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/openai/plugins --skill stripe-best-practices

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

File Explorer

6 files

SKILL.md

Source instructions · Read-only preview

name: stripe-best-practices
description: 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.

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](references/payments.md) | | Custom payment form with embedded UI | Checkout Sessions + Payment Element | [references/payments.md](references/payments.md) | | Saving a payment method for later | Setup Intents | [references/payments.md](references/payments.md) | | Connect platform or marketplace | Accounts v2 (`/v2/core/accounts`) | [references/connect.md](references/connect.md) | | Subscriptions or recurring billing | Billing APIs + Checkout Sessions | [references/billing.md](references/billing.md) | | Embedded financial accounts / banking | v2 Financial Accounts | [references/treasury.md](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](https://docs.stripe.com/payments/payment-methods/integration-options.md) — Start here when designing any integration. - [API Tour](https://docs.stripe.com/payments-api/tour.md) — Overview of Stripe's API surface. - [Go Live Checklist](https://docs.stripe.com/get-started/checklist/go-live.md) — Review before launching.

View on GitHub

Back to search Back to installation

assess-patch-risk

Assess an immutable patch artifact's program impact, regression risk, and auto-merge eligibility. Use for generated patch files, provider pull-request diffs, or commit ranges when reviewers need evidence about affected runtime paths, contracts, tests, and recoverability. This skill is read-only and does not generate, edit, apply, push, or merge the patch.

2026-09-11

attack-path-analysis

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-09-11

deep-security-scan

Use when the user asks for a deep, exhaustive, multi-pass, or variance-reducing repository-wide or scoped-path Codex Security scan. Run repeated complete independent Standard scans with the Codex Security deep-scan tool, which aggregates their validated findings and prepares the canonical artifacts; then complete the same scan once. Do not use for PRs, commits, branch diffs, or working-tree diffs.

2026-09-11

View all from this repository

stripe-best-practices

Source facts

Install options

Review the source files

More from this repository

More from this repository