v7.1.3

Fixes

• Remove redundant applicationInfo field for /payment/details Adyen API call (#660)

v7.1.2

Fixes:

• Modify the error handling to avoid returning stacktrace when user accesses extension module URL through browser (#630)

Enhancement:

• Upgrade to nodejs 14 as min supported version (#645)

v7.1.1

Fixes:

• A bug fix is added for the metadata.commercetoolsProjectKey check when it's undefined (#602)

Enhancements:

• The notification module will return "accepted" by default, otherwise, notification delivery can not be retried by Adyen as it most probably would fail again. The notification module will return the 500 status code only when the issue is recoverable with a retry. (#629)

v7.1.0

Extension module

New features

• The extension module now supports authentication mechanism (#584). It aims at protecting extension endpoints from being accessed by unauthorized 3rd-parties. Once it is enabled, authorized customer has to provide credentials stored in ADYEN_INTEGRATION_CONFIG. For authentication settings in configuration, please refer to How To Run. To embed the given credentials into request header, please refer to this document to create ExtensionDraft.

Improvements

• Use in package.json unique project names for notification and extension modules (#573)
• Improve/review integration guide documentation of extension module (#570)

v7.0.0

Extension module

Important Breaking Changes ⚠️

The extension module now supports multitenancy setup and this change is no longer compatible with previous versions.

Migration guide

• The configuration for Extension module has changed. Now it requires one environment variable ADYEN_INTEGRATION_CONFIG with JSON as its value. Remove all existing environment variables and add an environment variable ADYEN_INTEGRATION_CONFIG. For more information, see the How to run guide
• 2 new attributes are added to the commercetools custom type ctp-adyen-integration-web-components-payment-type. These attributes are commercetoolsProjectKey and adyenMerchantAccount. Please compare your current custom type and the new custom type and create these attributes.
• In order for commercetools-adyen-integration to know which project it should communicate with, this new custom fields must be provided. The payment object must contain the following 2 custom fields:
  • Provide merchant account as a custom field called adyenMerchantAccount on create payment.
  • Provide commercetools project key as a custom field called commercetoolsProjectKey on create payment.

  In case any of those fields are not provided, payment creation will be rejected.

Notification module

Important Breaking Changes ⚠️

The notification module now supports multitenancy setup and this change is no longer compatible with previous versions.

Migration guide

• The configuration for Notification module has changed. Now it requires one environment variable ADYEN_INTEGRATION_CONFIG with JSON as its value. Remove all existing environment variables and add an environment variable ADYEN_INTEGRATION_CONFIG. For more information, see the How to run guide.

Both modules

New features

• Support for multitenancy - one instance of Extension or Notification module can serve multiple commercetools projects and multiple adyen merchant accounts
• New deployment scripts for AWS Lambda and Google Functions

Improvements

• Add caching for commercetools API tokens so that they could be reused for every requests.

v6.0.0

Feature

• Add support for partial refund (#475)

Extension Module

Important Breaking Changes ⚠️

• CancelOrRefund option is removed. It is now replaced by two options: Cancel option and Refund option.

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