Releases: Adyen/adyen-commercetools
Releases · Adyen/adyen-commercetools
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
ormerchantReference
as payment key, and lookup the corresponding payment with them (ororiginalReference
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
v10.0.1
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
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
v9.10.0
v9.9.2
Improvement
- Add support of Azure deployment for both Extension and Notification modules (#993) - for detailed information check the documentation.