v11.4.1

New features

• Fixed #1145 by adding support for AWS API Gateway payloadFormatVersion 1.0.

v11.4.0

Bug fix

• Fix webhook handling when initial payment/session request has no response
• Fix reported bug that integration assumes that prices are always with included tax
• Update defaults for payment method names

v11.3.0

New features

• Upgraded Adyen checkout API to version 71. The extension and notification modules are now compatible with WebComponents version 5.53.2
• Usage of legacyApiBaseUrl configuration parameter is removed. The extension module is not using legacy API routes anymore.
• Project dependencies are updated

v11.2.0

New features

• Support for advanced checkout flow is introduced. Advanced flow allows upgrading Adyen web components on the storefront by keeping the existing checkout logic.
• Project dependencies are updated and the node version is bumped to >=18
• Deprecated API endpoints usage for capture, refund, and cancel is replaced with active ones

v11.1.1

Bug Fix

After we added new feature in integration to support Commercetools Connect, we found that the integration cannot be built in Connect due to missing adyen configuration in environment variable in Connect platform and vulnerable dependencies used.

For this reason, we added following patches in this version :

1. Changed the npm command npm run test to execute unit test only for Commercetools Connect. Meanwhile the normal CI/CD pipeline executes npm run test-ci to perform unit test, integration test and e2e test
2. Move c8 libraries to devDependencies in package.json

v11.1.0

New feature

• Support Commercetools Connect

For application developers aiming to create integrated e-commerce solutions, and clients seeking to expand the functionality of their Composable Commerce Project, commercetools Connect offers a streamlined approach for creating and deploying integrations.
https://docs.commercetools.com/connect/

v11.0.0

Breaking change ⚠️

• Adyen extension module is now supporting Adyen Web Component v5. In the new version, we allow users to input createSessionRequest custom field in Commercetools payment payload to create payment session for newly-introduced Adyen endpoint /sessions.
  Documentation for session endpoint
  Documentation for new checkout flow for Adyen Web Component v5

• Since new checkout flow has been introduced, this integration is no longer supporting existing payment custom fields makePaymentRequest and submitAdditionalPaymentDetailsRequest. For details, please refer to our latest integration guide.

• We would base on web component v5 for upcoming changes. For users who are using web component v4 and need bug fix(es) or enhancement(s), we would suggest to adapt Adyen web component v5 in your merchant webpage.

v10.1.2

Improvement

User reported that refund requests fail from time to time. We found that we are unable to handle the non-JSON response from Adyen API call, which has hidden the root cause of the problem #1052

Now we have provided a fix for this issue. The non-JSON response from any Adyen API call would be handled, and the corresponding error stack would be saved as response field in InterfaceInteraction, so that we can understand more about the failed API call and help to investigate the root cause.

v10.1.1

Bug Fix

• After we introduced custom field for refund reference in v9.10.0, it leads to unmatched payment in notification because the the reference obtained in notification is not matched with payment key. To fix it, we now use either pspReference or merchantReference as payment key, and lookup the corresponding payment with them (or originalReference if it exists) in notification module.

For more information, please refer to our architectural decision record

v10.1.0

New feature

• Add a script to ensure a webhook and HMAC key for the notification module. If you have not set up webhooks for your notification module yet, you can use the script to set it up for you. For detailed information see the Integration Guide for the notification module