Stripe payments
Stripe's skills for payment integrations: Checkout or PaymentIntents, webhooks, Billing, Connect platforms and verification, and the Stripe docs.
Category: Backend. By playbookrun. Reviewed by PlaybookRun before publishing. Installs in Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI and more.
Tags: stripe, payments, billing, subscriptions, connect
Skills
- stripe-best-practices (stripe-best-practices): Guides Stripe integration decisions across development and test environment planning (separate sandboxes vs the shared test mode sandbox), API selection (Checkout Sessions vs PaymentIntents), Connect platform setup (Accounts v2, controller properties), billing/subscriptions, tax and registrations (Stripe Tax, automatic_tax, product tax codes), Treasury financial accounts, integration options (Checkout, Payment Element), migrating from deprecated Stripe APIs, and security best practices (API key management, API key permissions, webhooks, OAuth). Use when planning, building, modifying, testing, or reviewing any Stripe integration, including choosing a development environment, accepting payments, building marketplaces, integrating Stripe, processing payments, setting up subscriptions, collecting sales tax, VAT, or GST, creating connected accounts, or implementing secure key handling.
- stripe-docs (stripe-docs): Use when the user or agent needs to read, search, or look up Stripe documentation or API reference. Prefer this over curl or WebFetch for any docs.stripe.com content. Use to fetch gated documentation.
- connect-recommend (connect-recommend): Use this skill when the user asks about Stripe Connect configuration, charge patterns, Dashboard access, or how to get started with Connect, is building a marketplace, platform, multi-vendor store, gig platform, or subscription platform, needs to pay out sellers, vendors, or providers, mentions split payments, revenue sharing, multi-party payments, or similar payment distribution concepts, provides a company URL or business description for a recommendation, builds SaaS that routes money between parties (for example, POS, booking, invoicing — not operational SaaS without payment routing), asks about onboarding or KYC for merchants, sellers, and vendors, mentions connected account Dashboard or responsibility configurations, or asks about payment flows, white-label payments, or embedded payments.
- connect-required-verification-information (connect-required-verification-information): Use this skill when the user asks what information a Stripe Connect connected account must provide for verification, onboarding, KYC, or account requirements; when they need to compare requirements between connected-account setups; or when they ask which verification fields, documents, or business details are required for a particular platform country, account country, business type, dashboard, service agreement, or capability.
MCP servers
- Stripe: Stripe's hosted server: search the docs and work with your Stripe account through OAuth. Use a sandbox or test mode while developing.
Install
claude plugin marketplace add Fcakiroglu16/marketplace claude plugin install stripe-payments@playbookrun