Mobile SDKs lifecycle policy
Last updated: August 12, 2026
Checkout.com's lifecycle support policy covers the versioning and deprecation strategy, development support tiers, and adoption timelines for the following Android and iOS SDKs:
Each SDK platform sets its own version numbers and release cadence.
We divide development support for an SDK version into three tiers:
- Full support – The version is under active development. Updates include new features, bug fixes, and security patches.
- Advisory – The version is no longer under active development, so we do not release updates or patches for it. Security advisories prompt you to upgrade to a version with full support.
- End-of-life (EOL) – The version is no longer supported. We do not release updates, patches, or security advisories, and no further support is available.
We version and release each platform's SDK components together as a bundle, following standard semantic versioning: Major.Minor.Patch.
- Major – Introduces API changes that are not compatible with previous versions.
- Minor – Introduces new functionality that is backward compatible with previous versions.
- Patch – Introduces backward-compatible bug fixes.
Adoption timelines and Advisory tier durations vary by version type:
| Version type | Expected adoption timeline | Advisory tier duration |
|---|---|---|
Major | 9 months | Until we release the next major version. |
Minor | 3 months | Until we release the next minor or major version. |
Patch | 1 month | Until we release the next patch, minor, or major version. |
We only apply security patches to the version under full support.
A critical security vulnerability may arise before you can migrate to a new major version. In that case, we may apply security patches to versions in the Advisory tier.
We only change minimum platform requirements in major SDK version releases:
- iOS – The minimum deployment target changes. For example, we may drop support for iOS 15.
- Android – The
minSdkorcompileSdkchanges. For example, we may raise theminSdkfrom 24 to 26.
This gives you a 9-month window to adapt to platform requirement changes.
A card scheme or platform mandate may require an SDK update. If this happens, we assess whether the change calls for a major or minor version release.
We notify you 3 months in advance of any SDK version update driven by an external mandate.
With every major version release, we provide a migration guide that covers:
- All breaking changes, with code examples
- Deprecated API removals
- New minimum platform requirements
- Step-by-step migration instructions
We notify you 2 months in advance of any breaking change in a new SDK version. This does not apply to urgent security, card scheme, or legal compliance changes.
We deprecate APIs in two stages:
- We deprecate the API in a minor release, but it keeps working as normal. You'll receive compiler warnings when you use it, so you can plan your migration during the minor version support window. We mark it as deprecated with migration hints, using each platform's native mechanism:
- Android (Kotlin and Java) –
@Deprecatedwith theReplaceWithannotation. - iOS (Swift) –
@available(*, deprecated, renamed:)or@available(*, deprecated, message:).
- Android (Kotlin and Java) –
- We remove the API in the next major release. Using it then causes a compiler error.
We publish release notes for every version in GitHub Releases.