Cette page n'est pas encore disponible dans cette langue. Nous faisons tout notre possible pour proposer notre documentation dans davantage de langues et nous vous fournirons la version traduite dès qu'elle sera disponible.
Mobile SDK versioning and support policy
Learn about the Mobile SDK versioning and support policy.
This page describes Stripe’s mobile SDK versioning policy, compatibility with Stripe API versions, and how to update to newer SDK versions.
Stripe’s iOS SDK follows semantic versioning (semver). This means that version numbers are structured as MAJOR.MINOR.PATCH, where:
MAJOR version increments indicate incompatible API changes
MINOR version increments add functionality in a backwards-compatible manner
PATCH version increments include backwards-compatible bug fixes
We recommend staying up to date with the latest SDK versions to take advantage of new features, improvements, and bug fixes.
Migration guides and changelog
Migration guides - Detailed guides for upgrading between major versions
Changelog: Complete history of changes across all versions
Support policy
New features and bug fixes are released on the latest major version of the SDK. If you’re on an older major version, we recommend upgrading to the latest major version to take advantage of these features and bug fixes. Older major versions of the SDK continue to be available for use, but won’t receive any additional updates.
Compatibility with Stripe API versions on your backend
Unless specifically noted in an SDK API, the mobile SDKs is compatible with any Stripe API version you use on your backend.