No momento, esta página não está disponível em português
Classic-integration icon

Classic Checkout SDK is end-of-life

Find out what classic Checkout SDK end-of-life means for you.

The classic Checkout SDK integrations are being phased out
This means we are:

  • No longer developing the classic Checkout SDK integration.
  • Not accepting new classic Checkout SDK integrations.

You have until March 31, 2024 to migrate.


Due to the upcoming PCI DSS v4.0 requirements and evolving security standards and regulations, we are forced to deprecate the classic Checkout SDK per April 2024.

Besides, there are a number of benefits to migrating from classic Checkout SDK to a newer integration, including:

Our newer integrations, Drop-in and Components, do meet the upcoming PCI DSS v4.0 requirements.


Migration steps

1. Find out where you use the classic Checkout SDK

If you know that you have a classic Checkout SDK integration or received an email from Adyen about live traffic with the classic Checkout SDK, the deprecation applies to you. Contact our Support Team if you need help with identifying your classic Checkout SDK traffic.

To identify your usage of the classic Checkout SDK, search for requests to the following endpoints (which are exclusive to the classic Checkout SDK):

  • /paymentSession
  • /payments/result
  • /setup
  • /verify

2. Choose a new integration

Need help to migrate?

Our Support Team can help you find a system integrator.

The easiest way to replace your classic Checkout SDK integration is to migrate to a more adaptable and flexible Drop-in.

Alternatively, try our interactive guide to get a recommendation for your new integration based on your business needs.

If you currently use the classic Checkout SDK for Android, we strongly advise you to reserve time for migration in Q4 of 2023. This is because starting in that quarter, our Android Drop-in and Component integrations will begin to support the /sessions request, which they currently don't.

3. Migrate to your new integration

When migrating to your new integration, you do not need to change your:

  • Account structure
  • Payment method setup
  • System messages setup
  • Payout settings
  • Reporting and reconciliation setup
  • Risk profile

To migrate, build an integration to replace the classic Checkout SDK:


Drop-in is a pre-built checkout. It is quicker to integrate, but allows for less control over your payments UI.


Components are pre-built payment forms for individual payment methods. You can use these to build a checkout. They allow for more flexibility in how you present payment methods in your checkout, but take more time to integrate - you will need to add and configure each payment method individually.


Use our APIs and build your own payment form if you want full control over the look and feel of your checkout page.

4. Submit PCI DSS validation documentation

The complexity of the documentation you need to submit depends on the new integration you choose.

You must submit the PCI DSS validation documentation before going live with your new integration. Contact our Support Team to get the prefilled PCI DSS documentation you need to sign.

If you move your classic Checkout SDK traffic to another Adyen integration for which you are already providing annual validation documentation, then you most likely don't need to submit additional validation documentation.

See also