stripe▌

Comprehensive guide for upgrading Stripe API versions across all SDK types and platforms. \n \n Covers server-side SDKs (dynamically-typed languages like Python, Node.js, Ruby allow per-request or global version overrides; strongly-typed languages like Java, Go, .NET require SDK updates instead) \n Stripe.js uses an evergreen model with biannual major releases (Acacia, Basil, Clover) that automatically pair with corresponding API versions; v3 continues to be supported indefinitely \n Mobile SDKs

Authoritative guidance for implementing Stripe payment integrations across all use cases. \n \n Prioritizes Checkout Sessions API for on-session payments and subscriptions; recommends Stripe-hosted or embedded Checkout as the primary web integration surface \n Covers payment flows, subscription models, webhooks, Connect platforms, and fund management with explicit guidance on modern APIs versus deprecated endpoints \n Includes pre-launch checklist requirements, PCI compliance considerations, and

Decision guide for Stripe API selection, Connect setup, billing, and integration patterns. \n \n Routes integration decisions across six domains: one-time payments (Checkout Sessions), custom payment forms (Payment Element), saved payment methods (Setup Intents), marketplaces (Accounts v2), subscriptions (Billing APIs), and embedded financial accounts (Treasury) \n Provides reference documentation for each integration type, including API version guidance (latest: 2026-02-25.clover) and pre-launc

You are a payments engineer who has processed billions in transactions. You've seen every edge case - declined cards, webhook failures, subscription nightmares, currency issues, refund fraud. You know that payments code must be bulletproof because errors cost real money. You're paranoid about race conditions, idempotency, and webhook verification.

Drive a sponsor through a SponsorCal booking page — enumerate ad-slot inventory and pricing, pick an available issue date, hand off to Stripe Connect Checkout, then submit assets (headline, body, URL, logo) at the tokenized post-payment URL and track booking status through approval and revisions. Read-only on payment + final asset submission unless caller has explicitly authorized them.

Mint a one-time-use payment credential (virtual card PAN or Shared Payment Token) from a user's Link wallet so an agent can complete a purchase on their behalf. User approves each spend request from the Link mobile app; real card details never reach the agent.

Stripe payment processing with checkout sessions, subscriptions, webhooks, and customer management. \n \n Supports three checkout approaches: Stripe-hosted checkout (lowest maintenance), custom UI with Payment Element, and Payment Intents for bespoke control \n Handles subscriptions, one-time payments, refunds, and disputes with built-in webhook event handling for payment success, failure, and subscription lifecycle changes \n Includes customer management, payment method storage, and customer po

Add Stripe payments to a web app. Covers the common patterns — one-time payments, subscriptions, webhooks, customer portal — with working code. No MCP server needed.

Comprehensive skill for automating Stripe payment processing and subscription management.

Stripe payment processing with checkout sessions, subscriptions, webhooks, and customer management. \n \n Supports three payment flows: hosted Checkout Sessions (fastest setup), custom Payment Intents with Stripe.js (full UI control), and Setup Intents for saving payment methods without charging \n Includes subscription management with Products, Prices, and recurring billing, plus customer portal for self-service subscription changes \n Provides webhook handling for critical events (payment succ