v5.1.0

Extension Module

Important Breaking Changes ⚠️

• Remove getOriginKeys action (#469). Note: getOriginKeysRequest and getOriginKeysResponse could be removed from the custom type.

Improvements

• Add applicationInfo to all requests to Adyen (#467)
• Prevent creation payment with different amountPlanned and amount in the makePaymentRequest (#462)

Notification module

Improvements

• Improve error logging for HMAC validation (#465)

v5.0.0

Extension Module

Important Breaking Changes ⚠️

commercetools-adyen-integration supports the concept of Adyen Web Components. Components are available for cards, wallets, and most local payment methods. For a list of all payment methods with an available component, refer to supported payment methods.

This release is NOT compatible with previous releases. In case you are currently using the old versions of the extension module, the following changes have to be done in order to work with the new release version.

Migration Guide

• Custom types are changed, please follow the How to run guide for more details.
  • Create new payment custom type. This can be automatically created by the extension module if no payment type with such key exists.
  • Update existing payment-interface-interaction custom type.
• Checkout and the frontend have to be changed, now the extension module requires web-components integration to support lots of payments that support web components. Please follow the new integration guide to adapt your checkout process into the new extension module.

Note: Merchant server no longer creates transactions. Instead, the merchant server creates/updates custom fields as described in the integration guide

Notification Module

• Notification module now supports the HMAC signature verification and it's enabled by default. Please enable HMAC signatures in your Adyen Customer Area. Then add generated secret HMAC key into ADYEN_SECRET_HMAC_KEY environment variable. If required HMAC verification can be deactivated through the environment variable. Please follow the Integration Guide for more details.

v4.0.2

Fix

• return empty actions when paymentHandler short-circuits #301

The response from an API Extension hosted in an AWS Lambda must contain a valid array for the actions property - i.e. undefined is not allowed.
(This is an addition to the previous PR: #297)

v4.0.1

Fix:

• AWS Lambda function fix for extension: Null check around paymentResult.data, which can be null if paymentHandler short circuits when not an Adyen payment. #297

Feat:

• use official node alpine image and update from node 8 to node 12.18.0 (LTS) #209
• JSON resources files were renamed regarding their content (Updated payment-interface-interaction-types.json content it's now not an array but a JSON object.) #285

v4.0.0

Breaking change:

Drop support for nodejs version 8, now the library uses nodejs 12. #190

v3.0.1

#97 delete obsolete additional data from payment response which is stored in interface Interactions.fields.

v3.0.0

Changes:

• #85 expect from front end/user to supply Authorization transaction instead of Charge (⚠️ breaking change)

Migration Guide:

The front end/user should now supply transactions with type Authorization instead of Charge. Please check the Integration guide for more details.

For credit card: https://github.com/commercetools/commercetools-adyen-integration/blob/master/extension/docs/CreditCardIntegration.md

For paypal: https://github.com/commercetools/commercetools-adyen-integration/blob/master/extension/docs/PaypalIntegration.md

v2.1.2

Remove obsolete data from interface interactions (#84)

v2.1.1

New features

• Update dependencies for notification and extension modules (#77)

v2.1.0

New features

• Add AWS lambda support (#69, #68)
• User can enable/disable automatic CTP resource creation (#73)