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

v10.0.2

Bug fix

• Extension module: submit payment details: add a check if a transaction already exists before creating a new transaction (#1019)

v10.0.1

Bug fix

• When there are no changes for API extensions, ensure API extensions won't update API extensions. (#1017)

v10.0.0

Breaking change ⚠️

• Adyen extension module is now using conditional extension trigger. You need to set the condition field in API extension using Change triggers action or you can also run setup-resources command that will do the updates for you. (#1014)

v9.13.0

Extension module

Feature

• adyen-integration can automatically generate unique idempotency key for manual capture requests and refund requests. Have a look at refund and manual capture documentation. (#930)

v9.12.0

Extension module

Feature

• Users can add custom reference field for manual capture. For more details, please refer to manual capture documentation (#1011, #1012)

v9.11.0

Features

• Users can add idempotency key field to allow retry for captures and refunds. For more info about this feature see the documentation for Capture and Retry (#1000)
• Users can disable stored payments. For more info about this feature see the documentation.(#1004)

v9.10.0

Feature

• Add custom transaction field field for refund reference (#997)