Versioning 

Each major release, such as Acacia, includes changes that aren’t backward-compatible with previous releases. Upgrading to a new major release can require updates to existing code. Each monthly release includes only backward-compatible changes, and uses the same name as the last major release. You can safely upgrade to a new monthly release without breaking any existing code. The current version is 2025-09-30.clover. For information on all API versions, view our API changelog.

• Starting from stripe-node v12, the requests you send using stripe-node align with the API version that was current when your version of stripe-node was released. This ensures that your TypeScript types are compatible with the API version you use.
• On stripe-node v11 or lower, requests made with stripe-node use your Stripe account’s default API version (controlled in Workbench).

You can override the API version in your code in all versions.

To override the API version, provide the apiVersion option when initializing the library, or set it per-request. This might cause inaccurate Typescript types.

Webhook events also use your account’s API version by default, unless you set an API version during endpoint creation.

You can upgrade your API version in Workbench. As a precaution, use API versioning to test a new API version before committing to an upgrade.