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

Migrate to a new version

Follow these instructions to migrate your Adobe Commerce plugin to a new major version

On this page, we describe the changes that you need to make in your existing integration when migrating to v8 or v9 of the Adobe Commerce plugin.

V9 introduces a new configuration page that makes it easier to configure your plugin. See the release notes for an overview of all changes.

Step 1: Upgrade the plugin

Follow the instructions to upgrade the plugin to v9.

Step 2: Upgrade PHP

Adobe Commerce v2.4.4 requires PHP 8.1 or later to be installed on your server. Refer to the PHP documentation to see the changes for this PHP version.

If you are running a PHP version earlier than 8.1, install the required version.

Step 3: Check dependencies

V9 of the plugin uses Checkout API version 70 and Components version 5.51.1. If you have customized the plugin, upgrading could cause issues in the implementation of your custom code. Check if your integration is compatible with the new versions of Checkout API and Components, and apply changes if needed.

Step 4: Change your webhook server configuration

If you set up your integration manually, you have to change your webhook server configuration to ensure you continue to receive webhooks from us.

  1. Log in to your Customer Area.
  2. Select Developers > Webhooks.
  3. Next to the webhook you added when you set up webhooks, select > Edit webhook.
  4. Under General > Server configuration, select the edit icon .
  5. Change the ending of the URL from /process/json to /webhook. For example, from https://THE_URL_OF_YOUR_STORE/adyen/process/json to https://THE_URL_OF_YOUR_STORE/adyen/webhook.
  6. Select Apply.
  7. Select Save changes.

IP address validations for webhooks

The plugin has IP address checks in place to validate that the webhooks you receive are from Adyen. Previously, it was possible to choose if you wanted to enable this check. This option is removed in v9, and the checks run by default.

For test environments, the checks are disabled to let you test webhook processing.

Step 5: Verify changes in payment methods

Changes to payment methods and how they are displayed

  • All payment methods are now registered independently on the Adobe Commerce platform. Previously, the plugin grouped payment methods into cards and alternative payment methods. With the separation of payment methods to their own files, payment methods are sorted based on the order in your Customer Area.
  • You can now enable all payment methods that you have enabled in your Customer Area by selecting a single button in Adobe Commerce.

    After upgrading your plugin, make sure that you have enabled the payment methods.

  • By default, the payment methods shown to shoppers during checkout are based on their billing address country. You can override this with the ISO Country Code setting.
  • If you applied customizations to the way payment methods are handled in your plugin, upgrading may cause issues in the implementation of your custom code. Check if your custom code is compatible with the new payment method set up.
  • For headless integrations:
    1. You now have to send the individual payment method names in your requests when placing orders.
    2. You no longer need to include shippingAddress object in your request to the /paymentMethods endpoint when getting available payment methods.

Step 6: Verify changes to the gift card flow

Gift card payments have a new native flow.

Previously, shoppers were redirected to an Adyen-hosted payment page. In v9, gift card payments use the Checkout API /orders endpoint and shoppers can complete partial gift card payments in one native flow.

If you previously set up gift card payments in your integration, using the new flow requires additional configuration on our end. Contact our Support Team.

Step 7: Verify changes to tokenization

The plugin uses the Adobe Commerce Vault for tokenization. Previously, you could choose between storing token references in Adyen or Adobe Commerce.

If you use tokenization, you have to reconfigure the payment methods for which you want to enable tokenization, and specify a recurring processing model. Follow the instructions to set up the Vault in Adobe Commerce.

If you previously used Adyen tokenization, the tokens are migrated to the Adobe Commerce Vault automatically. To verify the migration, you can manually check if your token references are stored correctly.