
Upgrade Stripe
by stripe08d371a9fbe0No licenseListed Oct 8, 2026Updated Oct 8, 2026
Guide for upgrading Stripe API versions, webhook endpoints, server-side SDKs, Stripe.js, and mobile SDKs
- 08d371a9fbe0Currentcommit 08d371aPublished Oct 8, 2026
1 modifiedCompare on GitHub
- 97b2164821c3commit 97b2164Published Oct 8, 2026
Source and attribution
Source:stripe/aiinskills/upgrade-stripeat commit08d371a
License: No license
Content belongs to its original authors. SourceWeft indexes it from a public repository.
More from stripe/ai

Stripe Best Practices
stripe
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.

Metronome
stripe
Guides Metronome usage-based billing integration decisions — event ingestion (single and batch, idempotency, billable metrics), contract design (rate cards, overrides, dimensional pricing, products), invoicing lifecycle (grace periods, finalization, Stripe sync), credit and commit management (prepaid, postpaid, thresholds, auto-recharge), and Stripe integration (arrears invoicing, tax providers, line item limits). Use when building, modifying, or reviewing any Metronome integration — including ingesting usage events, creating contracts or rate cards, managing credits and commits, configuring invoicing, or syncing invoices with Stripe Billing.

Connect Required Verification Information
stripe
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.

Connect Recommend
stripe
Recommends a Stripe Connect configuration and charge pattern from a business description or codebase scan.
More in Software Development

Playground
anthropics
Builds self-contained interactive HTML playgrounds with controls, live preview, and copyable prompt output.

M5 Onboard
anthropics
Provisions M5Stack ESP32 boards by detecting them on USB, flashing UIFlow 2.0 firmware, and installing a MicroPython app bundle.

Cardputer Buddy
anthropics
Guides iterating on a Cardputer-Adv MicroPython app bundle: adding apps, pushing files over USB-serial, tailing logs, and running REPL commands.

Testing Strategy
anthropics
Designs test strategies and test plans, covering test types, coverage targets, and example test cases.

Tech Debt
anthropics
Identifies, categorizes, and prioritizes technical debt, producing a scored backlog and phased remediation plan.

System Design
anthropics
Guides system and architecture design through requirements, high-level design, deep dives, scaling, and trade-off analysis.