Versioning 

About the API
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.

Because stripe-java is strongly typed, requests that you send using it are fixed to the API version that was the latest at the time your version of stripe-java was released. To use a newer or older API version, upgrade or downgrade your version of stripe-java. Use the stripe-java changelog to find which versions include the API version you need.

Webhook events use the API version that’s set during your webhook’s endpoint creation. Otherwise, they use your Stripe account’s default API version (controlled in Workbench). Create a webhook endpoint with an API version equal to the version that’s pinned by your version of stripe-java, which you can determine through the Stripe.API_VERSION property.

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.

Stripe.apiKey = "sk_test_BQokikJ...2HlWgH4olfQ2sk_test_BQokikJOvBiI2HlWgH4olfQ2";
// Since Java is strongly typed,
// the version is fixed in the library.