Checkout icon

Upgrade your integration

Keep your integration up-to-date with the latest versions.

Find our latest releases

Adyen aims to offer seamless integration for an easy checkout and payment process to shoppers globally. Because the payments industry is constantly changing, we frequently release new versions and features.

We recommend that you update your integration regularly to benefit from our latest improvements. Our updates provide competitive advantages so that your shoppers have an efficient checkout experience.

We frequently release improvements to our products to keep up with the newest developments in the fast-paced payments industry:

  • Shopper expectations
  • Regulations
  • Best practices

Our way of versioning

Check our release notes to see the latest changes and follow our migration guides to upgrade your integration.

Type of changes Version type Description
Backwards-compatible Minor version The changes in these versions work with earlier versions and do not break existing integrations.
Breaking changes Major version We only introduce changes that do not work with earlier versions in major versions. For example, these could be new features or new ways of structuring data present in earlier versions.

For our Drop-in/Components, we frequently release minor versions and periodically release major versions.
For our Checkout API, we only release major versions.

Drop-in/Components lifecycle

After a new Drop-in/Components version is released, it follows a lifecycle that contains four states.

State Description
Active The latest major version of Drop-in/Components. This is the recommended version to use that benefits from new features, bug fixes, and changes required to comply with new regulations.
Inactive A version that only receives bug fixes and changes required to comply with new regulations.
Deprecated A version that no longer receives any new features, bug fixes, and changes required to comply with new regulations. After a version reaches this state, you have 1 year to upgrade to the latest version of Drop-in/Components.
End-of-Life A version that no longer receives any new features, bug fixes, and changes required to comply with new regulations. When a version reaches end-of-life, you no longer receive support from Adyen and payment processing can be suspended anytime.

Check the lifecycle states of our Web Drop-in/Components versions on GitHub.

The following is a visual example of how different versions receive new states over time:

Benefits of upgrading

You can get the best of Adyen's products when you upgrade your existing integration to a newer version. We recommend the following:

Upgrading from Classic API to Checkout API

We no longer develop the Classic API, which can process only card payments.

We strongly recommend that you upgrade your server-side integration to use the latest version of the Checkout API for the following benefits:

  • A single integration to process all payment methods, including cards, bank-based, and alternative payment methods.
  • A simpler client-side integration with Drop-in/Components that is only available with the Checkout API.
  • Improved 3D Secure 2 authentication for payments. This includes simpler integration and the auto-authorization feature which reduces integration errors and failed payments.
  • An integration that adheres to latest security standards, like JSON Web Encryption (JWE) and JSON Web Signature (JWS), and offers your shoppers a more secure checkout process.
  • A simple, developer-friendly integration experience that handles many of the complexities of processing payments with less code complexity.
  • More specific error responses that makes debugging easier.

Upgrading to the latest version of Checkout API

If you already use Checkout API, we recommend that you upgrade to the latest version of Checkout API if the following applies to you:

  • You use 3D Secure 2 to authenticate payments with Adyen and use v66 or earlier. In v67, we simplified the integration and introduced auto-authorization that reduces integration errors and failed payments.
  • You are are upgrading Drop-in/Components to a version that is no longer compatible with the your current Checkout API version. For example, Web Drop-in/Components v5.0.0 is only compatible with Checkout API v68 or later.

We continuously release new features for Checkout API to improve your online payments integration. Most improvements are backward compatible. When we must introduce a breaking change, we release a new major version.

Upgrading to the latest version of Drop-in/Components

Drop-in/Components follow the semantic versioning standard. Changes are released in a new patch, minor, or major version.

We recommend you upgrade to the latest major version of Drop-in/Components to get the latest features and bug fixes. The breaking changes introduced in our major versions improve performance of the integration and developer experience. Adyen no longer updates earlier major versions.

When you upgrade to the latest major version, you get the following:

  • New payment methods
  • New accessibility features
  • Design improvements
  • Better technical support

Before you upgrade, check the compatibility of the version you want to upgrade to.

Migration guides

We have guides to help you upgrade to the following:

Checkout API

Migration guide From version
Migrate to Checkout API (latest version) Classic API
Migrate to Checkout API v70 v69
Migrate to Checkout API v69 v68

Drop-in/Components

Drop-in/Components version compatibility

Each version of iOS and Android Drop-in/Components is compatible with different versions of other parts of your integration. When you upgrade, you must use versions that are compatible with one another.

For iOS Drop-in/Components, you must make sure your version of Drop-in/Components is compatible with the following:

Description
Checkout API The recommended earliest version of Checkout API.
iOS version The earliest version of iOS that is compatible.

The iOS compatibility table shows these for each version of Drop-in/Components.

For example, if you use Drop-in/Components v5.13.0, you must use Checkout API v71 and iOS v12.

iOS compatibility table

Drop-in/Components Checkout API iOS version
5.5.0 - 5.13.0 v71 12
5.4.0 - 5.4.1 v70 12
5.2.0 - 5.3.0 v70 11, if you use Xcode 14 or earlier.
12, if you use Xcode 15 or later.
5.0.0 - 5.1.0 v69 11, if you use Xcode 14 or earlier.
12, if you use Xcode 15 or later.
4.12.0 - 4.14.0 v71 12
4.11.1 - 4.11.2 v70 12
4.10.4 - 4.11.0 v70 11, if you use Xcode 14 or earlier.
12, if you use Xcode 15 or later.
4.10.2 - 4.10.3 v69 11, if you use Xcode 14 or earlier.
12, if you use Xcode 15 or later.
4.0.0 - 4.10.1 v67 11, if you use Xcode 14 or earlier.
12, if you use Xcode 15 or later.

For Android Drop-in/Components, you must make sure your version of Drop-in/Components is compatible with the following:

Description
Checkout API The recommended earliest version of Checkout API.
Minimum API level The minimum API level.
In your manifest file as the minSdkVersion or in your build configuration as minSdk.
Target API level The target API level.
In your manifest file as the targetSdkVersion or in your build configuration as targetSdk.

The Android compatibility table shows these for each version of Drop-in/Components.

For example, if you use Drop-in/Components v5.7.0, you must use Checkout API v71, minimum API level 21, and target API level 34.

Android compatibility table

Drop-in/Components Checkout API Minimum API level Target API level
5.1.0 - 5.7.0 v71 21 34
5.0.0 - 5.0.1 v70 21 34
4.13.0 - 4.13.6 v70 21 33
4.11.0 - 4.12.1 v70 21 32
4.10.0 v69 21 32
4.9.0 - 4.9.1 v69 21 31
4.0.0 - 4.8.0 v67 21 30
3.8.0 - 3.8.3 v52 16 28

See also