PlugWiki

upgrade-stripe Skill for Claude: Upgrade Stripe API and SDK Versions

Stripe's skill for upgrading API versions, webhook endpoints, server SDKs, Stripe.js and mobile SDKs, step by step.

Installs
74.5K
on skills.sh
Stars
2K
on GitHub
Updated
Nov 2026
last repo commit

upgrade-stripe makes Claude work through a Stripe version upgrade in order. It picks a target API version, compares it with every version your code pins, updates the SDKs, tests with the Stripe-Version header and reviews webhook endpoints.

It triggers when you ask to upgrade Stripe versions. If you name no target, it looks up the current version on docs.stripe.com, and falls back to a version bundled in the skill only when it cannot reach the site. It is one SKILL.md and bundles no scripts.

Good for

  • Developers whose Stripe integration pins an old API version
  • Teams planning a move across a major Stripe release
  • Engineers who own Stripe webhook endpoints and event destinations

Install upgrade-stripe

Claude Code

  1. 1

    Copy this prompt.

    Install the upgrade-stripe skill in Claude Code. Run this command:
    
    claude plugin install stripe@claude-plugins-official
    
    Then check that it loaded and tell me how to use it.
  2. 2

    Paste it into Claude Code. It shows the change and asks before running it.

The README recommends the official plugin, which it says includes additional agent tools and updates automatically. The skills CLI route installs skills from docs.stripe.com, does not auto-update, and needs npx skills update -y to refresh. Pick one route, not both. The plugin also adds the hosted Stripe MCP server, lifecycle hooks and skill-usage telemetry (set DISABLE_TELEMETRY or DO_NOT_TRACK to 1 to turn the telemetry off). See the safety section.

From the project README. Source.

What's in the skill

When it loads

Guide for upgrading Stripe API versions, webhook endpoints, server-side SDKs, Stripe.js, and mobile SDKs

Sections in SKILL.md

  1. Choose a target API version
  2. Understanding Stripe API Versioning
  3. Types of Changes
  4. Server-Side SDK Versioning
  5. Dynamically-Typed Languages (Ruby, Python, PHP, Node.js)
  6. Strongly-Typed Languages (Java, Go, .NET)
  7. Best Practice
  8. Stripe.js Versioning
  9. Loading Versioned Stripe.js
  10. API Version Pairing
  11. Migrating from v3
  12. Mobile SDK Versioning
  13. iOS and Android SDKs
  14. React Native SDK
  15. Backend Compatibility
  16. Upgrade Checklist

Key facts

Author
Stripe
License
MIT
Installs on skills.sh
74,482 (Nov 2, 2026)
GitHub stars (whole repo)
2,026 (Nov 2, 2026)
Last commit to the repo
Nov 1, 2026

What it includes

  • Uses your version, or looks up the current one on docs.stripe.com

    Compares the target with every pin: client config, per-request overrides and webhook endpoints. It will not move a pin to an older version or a stable pin to a preview unless you ask.

    Network · Choose a target API version

  • Monthly versions are safe; major releases can break

    Since 2024-09-30.acacia, monthly releases have no breaking changes. A new major release starts twice a year and can need code changes.

    Understand API versioning

  • Set apiVersion in code, or update the SDK

    Ruby, Python, PHP and Node.js can set a version. Java, Go and .NET use a fixed version tied to the SDK release, so you update the SDK instead.

    Write · Server-side SDKs

  • Pairs each Stripe.js release with an API version

    Stripe.js uses named major releases twice a year. The pairing cannot be overridden.

    Write · Stripe.js versioning

  • iOS and Android use semantic versioning

    React Native uses a 0.x.y scheme where minor versions can break.

    Mobile SDK versioning

  • Nine steps from changelog to database column sizes

    Includes updating the SDK package, setting apiVersion, testing, reviewing webhook destinations, Stripe.js, mobile SDKs and storing IDs in columns of 255 characters.

    Runs code · Upgrade checklist

  • Try a new version without changing your default

    Shown with curl and with code. Replace the version in the examples with your target before running.

    Runs code · Test with the Stripe-Version header

  • Reviews each event destination's version

    Thin event payloads are unversioned. Snapshot events follow the destination's API version.

    Webhooks and thin events

  • A 72-hour window to go back in Workbench

    After an upgrade you can roll back to the previous API version in Workbench for 72 hours.

    Rollback note

From the official docs

Permissions

Medium risk

The skill makes Claude edit your Stripe integration, upgrade packages and may run test requests with a secret key. Work on a branch, use test-mode keys and review every change.

What it can do

  • Read your data
  • Create and change things
  • Delete things
  • Read-only mode

Watch out for

  • It edits payment integration code

    It changes API version pins and SDK settings in your Stripe code. Work on a branch and review the diff before you deploy.

  • It may run package upgrades

    The checklist includes commands such as npm update stripe and pip install --upgrade stripe. Approve each command.

  • The recommended plugin route adds a Stripe MCP server and hooks

    The Claude Code plugin the README recommends is more than this skill. Its .mcp.json points to the hosted Stripe MCP server at mcp.stripe.com, and its hooks.json runs Node scripts at session start and after Skill and Agent tool calls. Take only this skill with the skills CLI route if you want less.

  • The plugin sends skill usage names to Stripe

    The plugin README says every skill invocation sends its name to Stripe, unconditionally unless you set DISABLE_TELEMETRY or DO_NOT_TRACK to 1 or true. It also prompts the agent for feedback and says it shows you the draft and asks for approval before sending.

  • Test requests need a Stripe key

    The curl and SDK test examples take a secret key. Use a test-mode key, never a live one, for these checks.

  • It looks up docs on the web

    It reads docs.stripe.com to find the current version. If that fails, it must say the version is unverified.

  • The plugin checks your Stripe CLI at session start

    A session-start hook looks for a newer Stripe CLI version and may suggest installing it. The plugin README says it never installs anything itself.

Technical details
Talks todocs.stripe.com. api.stripe.com (test requests)
Sign-in and keysThe SKILL.md's examples use a placeholder test key (sk_test_xxx) and name no place to store keys.

Questions

How do I install upgrade-stripe?

Use the install box above. The Stripe README recommends the official Stripe plugin for Claude Code, Codex and Cursor, which it says includes additional agent tools and updates automatically. The skills CLI route works too but does not auto-update.

Which API version will Claude upgrade me to?

The one you name. If you name none, the skill looks up the current version on docs.stripe.com. Only when it cannot reach the site does it use its bundled fallback, and it must say the latest version is unverified.

Will it downgrade a version I already pinned?

Not unless you ask. The skill says not to move a pin to an older version or a stable pin to a preview version, and to report a pin that already matches the target as unchanged.

Does it work in the Claude app or Codex?

The README documents plugin installs for Claude Code, Codex, Cursor and Grok Build, and a skills CLI install. The Claude app route is not documented.

Do I need a Stripe API key?

The SKILL.md's test examples use a placeholder test key (sk_test_xxx) for curl and SDK calls. Use a test-mode key for any test call.

Is upgrade-stripe safe?

The skill is plain text, but it makes Claude edit payment code, upgrade packages and may run test requests against Stripe. Work on a branch, use test-mode keys and review every change. The plugin route the README recommends also adds an MCP server, hooks and usage telemetry, covered in the safety section.

Can I undo an API version upgrade?

The SKILL.md says that for 72 hours after upgrading you can roll back to the previous API version in Workbench.

Information

updated Nov 2, 2026

Repository
stripe/ai
Folder
skills/upgrade-stripe

stripe/aiskills.sh

Sources

Docs, issue trackers and discussions this page is built from.

Show all 7
  1. stripe/ai README · github.com
  2. Stripe plugin for Claude Code README · github.com
  3. upgrade-stripe SKILL.md · github.com
  4. upgrade-stripe on skills.sh · skills.sh
  5. stripe/ai · github.com
  6. Stripe plugin .mcp.json · github.com
  7. Stripe plugin hooks.json · github.com

Updated Nov 2, 2026.