Releases: Adyen/adyen-magento2
Adyen Payment 6.6.3
Known issues
Issues have been reported related to use of CsrfAwareActionInterface in Magento 2.2.x, therefore this version is not ready for use in <2.3.
Fixes:
#862 [PW-3332] Update plugin composer to support php library version 7
Fixed issue:
#861 6.6.2 Error in redirect class after 3DS authorisation
Adyen Payment 6.6.1
Description
#830 [PW-3095] Set reservedOrderId to null before placing an order
In case a customer tries to pay with a non Adyen payment method which reserves the order id then our payment methods will use that reserved order id until we have a successful payment which resets it. It causes issues since we can get multiple refused or offer closed notifications which closes the order before we finally make an authoirze one.
To solve this we added an interceptor and every payment-information request we would set the quote reservedOrderId to null. Therefore we wouldn’t bump unnecessary the orderIds and if it’s null it would not do anything. Also with this approach we can make sure every request of ours has a new order id as merchant reference even if any other service sets the reserved order id before it gets to us.
#850 [PW-3220] Revert the config to exclude adyen js from minification
We had to remove the fix from the config.xml to exclude the adyen checkout component js file from minification. The reason is that the <minify_exclude> is supported by magento version 2.3 and above and not from the older versions. We are planning to make a generic fix for this which will covers all the versions.
For now merchants who are using 2.3 and above can use the adyen-magento2 version release 6.6.0
#833 Check additionalData key in result before using
#836 [PW-3140] Google Pay Integration issue
Tested scenarios
Fixed issue:
Fixes #801 [PW-3140] Google Pay Integration issue
Fixes #805 [PW-3140] Google Pay Integration Bug
Fixes #810 [PW-3140] Google Pay Integration Issue 6.5.0
Fixes #825 [PW-3138] 3DSecure authorisation fails
Adyen Payment 6.6.0
Features
#795 #822 SEPA Direct Debit tokenization
#809 Separate checks for IP and HMAC for notifications received
#812 3DS2/3DS1 fallback
#816 Add the minify exclude element in config
Fixes
#808 Validate checkout agreements before placing order with Google Pay
#813 Remove dependency for Magento setup exception
#814 Fix for Vault with 3DS2 Credit Cards
#821 3DS storeview URL fix for redirect
Adyen Payment 6.5.0
Features
#781 Origin Keys cache now tagged as config
#784 Separate configurations for HMAC and IP webhook check
#786 New configuration for frontend origin domain (PWA) and #806 getOrigin() calls with new storeId param
#788 Guest checkout tokenization and #803 typo
Fixes
#789 Checkout service created with Adyen helper
#792 Country code fetch for admin Pay By Mail
#793 Fix Swish payment methods when running it with the Swish app
#799 Redirect data builder for CC authorize requests (SameSite cookie fix)
Fixed issues
SameSite cookie security settings broke the Magento session when the user was redirected from the issuer page after 3DS1 authentication. The plugin now receives the response via GET instead, the session is kept and the success page is shown on successful auth, error message on failure.
Adyen Payment 6.4.0
Feature:
#775 [PW-2390] Add action component on success page if presentToShopper and Action result is provided.
Adyen Payment 6.3.0
Adyen Payment 6.2.1
Fixes:
#740 Filter out children from invoice item collection
#750 Removed duplicate getData() declaration for Google Pay
#753 Refactor BeforeShipmentObserver
#754 Fix for getCheckoutOriginKeys() output
#755 [PW-2437] Fix issue with capture on shipment
Update vvvgiftcard image
Update mobilepay image
Fixed issues:
#733 Duplicate declaration of the getData function in adyen-google-pay-method.js
Adyen Payment 6.2.0
Features
#736 [PW-2385] Improvements for accepting notifications
Please see our docs page to learn how to configure HMAC key validation for notifications Setting up notifications and Security
Fixes:
#711 [PW-2357] Remove ResultPos.php
#712 [PW-2423] Improve authentication when accepting notifications
#713 [PW-2387] IP validation implementation
#716 [PW-2385] Add HMAC validation for notifications
Fixed issues:
- Fixed an issue where an unauthenticated user could cancel an ongoing point of sale transaction.
- Fixed an issue where an unauthenticated user could perform side-channel attacks to obtain notification credentials and affect the transaction notification flow.
- Fixed an issue where an unauthenticated user could perform a brute forcing attack to obtain notification credentials and affect the transaction notification flow.
Thanks to Denis Andzakovic from Pulse Security for reporting these issues under the Adyen responsible disclosure policy. We are happy to announce these issues are now fixed up.
Adyen Payment 6.1.2
Adyen Payment 6.1.1
Description
#715 Adjusting last name variable for boleto payments
#718 [PW-2383] Fix vault storing for updated expiration date
#719 [PW-2286]: Avoiding order cancellation in Result controller
#721 [PW-2236] Remove idempotency from alternative payment methods
#723 [PW-1972]: Extending AddressAdapter for extra street lines
#728 Fix boleto URL in customer order and admin
#725 [PW-2422] Add validation of the billing/shipping address in the payment forms
#732 [PW-2332] Delay OFFER_CLOSED notifications processing by 10 minutes
Fixed issue:
#596 [PW-1972] Housenumber/addition not visible in Adyen for paypal and credit cards orders
#678 [PW-2383] Unique constraint violation with duplicate vault token
#714 Boleto lastname sent incorrectly
#717 [iDeal] First notification is unsuccessful but a second notification 2 minutes later send a success response => order canceled but payment is in success
#727 Boleto PDF link is empty in customer account order details