skills.rest
FarooqProProgrammer
FarooqProProgrammerCOMMUNITY
Explore all skills by this author →
GitHub

stripe-best-practices

Guides Stripe integration decisions across payments, Connect, billing, tax, Treasury, and security.

Updated Sep 8, 2026
Search Tags:#subscriptions#payments#stripe#webhooks#connect#checkout sessions#stripe tax
One-click install
npx skills add https://github.com/FarooqProProgrammer/the-magician --skill stripe-best-practices-farooqproprogrammer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: stripe-best-practices
Source: https://github.com/FarooqProProgrammer/the-magician/tree/main/agent/skills/stripe-best-practices
Command: npx skills add https://github.com/FarooqProProgrammer/the-magician --skill stripe-best-practices-farooqproprogrammer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Stripe integrations fail in predictable ways: deprecated APIs get recommended, automatic_tax silently collects nothing without a registration, payment_method_types get hardcoded and hurt conversion, and webhooks get skipped. This Skill routes every Stripe question to current best practices and v2 APIs so integrations are built correctly the first time. ## Core Features & Use Cases - Integration Routing: Maps your use case (one-time payments, subscriptions, marketplaces, tax, embedded finance) to the correct modern Stripe API, such as Checkout Sessions, Accounts v2, or Metronome. - Domain References: Provides in-depth guidance for payments, Connect platforms, billing/subscriptions, Stripe Tax, Treasury financial accounts, and security (restricted keys, webhooks, OAuth, CSP). - Deprecated API Guardrails: Blocks legacy patterns like the Charges API, Sources API, v1 Connect account types, and global API key configuration, with migration paths to current APIs. - Use Case: When building a marketplace, the Skill directs you to Accounts v2 with destination charges, express dashboards, correct capability checks, and webhook-based fulfillment instead of deprecated v1 patterns. ## Quick Start Ask how to accept payments, set up subscriptions, create connected accounts, or collect sales tax with Stripe, and the Skill will recommend the correct current API and configuration.

Frequently Asked Questions about stripe-best-practices

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

FAQPage Schema
How do I accept one-time payments with Stripe?▼

Use the Checkout Sessions API for one-time payments, which handles discounts, shipping, and adaptive pricing automatically. Omit payment_method_types entirely so Stripe dynamically shows the most relevant payment methods for each customer.

Should I use Checkout Sessions or PaymentIntents for Stripe payments?▼

Use Checkout Sessions for on-session payments and subscriptions, and PaymentIntents for off-session payments or when you need to model checkout state independently. Never use the deprecated Charges API for new integrations.

Why is Stripe Tax collecting zero tax on my transactions?▼

Zero tax usually means automatic_tax is enabled without an active registration in the customer's jurisdiction, or the product has a Nontaxable tax code. Check taxability_reason on the line item and confirm registrations with the Tax Registrations API.

How do I create connected accounts for a Stripe marketplace?▼

Use the Accounts v2 API (POST /v2/core/accounts) with configuration.recipient requesting stripe_transfers capability, never the deprecated type: 'express' or 'custom' v1 patterns. Marketplaces default to dashboard: 'express' with destination charges.

Are webhooks required for Stripe subscription integrations?▼

Yes, webhooks are required for subscriptions because renewals, failed payments, and cancellations happen asynchronously after checkout. Handle customer.subscription.*, invoice.paid, and invoice.payment_failed events rather than relying on the success page.

Should I use a secret key or restricted API key for Stripe?▼

Always prefer a restricted API key (rk_ prefix) with only the permissions each service needs, following least privilege. Store keys in a secrets vault like AWS Secrets Manager or Azure Key Vault, never in source code.

Related Skills

Explore More Software Engineering Skills→
selrai-companyselrai-company

stripe-connector

Manage Stripe payments, invoices, subscriptions, and customers via CLI or API.

Official
Intermediate
dasara-varundasara-varun

Validation and Testing

Validates Cashfree Payments integrations using sandbox credentials, webhook verification, and go-live checklists.

Community
Intermediate
anicca-labsanicca-labs

stripe

Configure Stripe PaymentSheet flows and inspect payment events via MCP.

Official
Intermediate
herdiansahherdiansah
23

billing-automation

Automate subscription billing, invoicing, proration, and dunning management.

Community
Advanced