|September 2020 Release|
|July 2020 Release|
|March 2020 Release|
|Jan 2020 Release|
TEST: 9 September 2020 | PROD: 23 September 2020
Our platform allows to resubmit declined transactions due to missing 3-D Secure authentication.
Check out here how you can offer this Soft Decline feature to your customers.
Starting from 25 August 2020, Google will be releasing a new version of Google Chrome (v.85), impacting the way referrers are handled on Chrome.
To prevent data privacy leaks that may be accessible from other parts of the full URL such as the path and query string, only the main domain name (e.g https://www.your-webshop.com) is sent in the ‘Referer header’ of cross-origin requests.
To ensure business continuity of your web shop for customers using Chrome (v.85), as from 25 August we are pro-actively adapting the way our gateway is authenticating referrers to only validate the transaction request against to domain name (e.g https://www.your-webshop.com) instead of the complete page url (e.g https://www.your-webshop.com/shopping/cart.php) that you may have configured.
All new future integrations should not perform any data and origin check via referrer and only privilege the SHA. Find more information in our dedicated FAQ.
TEST: 1 July 2020 | PROD: 23 July 2020
Payment method Carte Bancaire (CB) becomes a true Payment Method following the implementation of the European Regulation 2015/751.
TEST: 11 March 2020 | PROD: 20 May 2020
The modalities of using parameter ALIASOPERATION have changed.
Before that, sending ALIASOPERATION=BYPSP could be used to prevent creating a new Alias if a card and / or Alias sent with a new transaction is already stored in our system. Due to PSD2-related regulations, this is no longer possible. As a consequence, the aforementioned scenario will result in the creation of multiple Aliases for the same card / customer.
Please check our Alias Manager documentation chapter 4.2 to get a detailled overview on the different scenarios and their outcome.
In our January release we introduced a new safety function: Any user that has not logged on to our platform for more than 60 days will be put into status "inactive".
To further enhance this security feature, we have extended it to users that have never logged on. A user that has been created at any point in the past and has never logged on will also be deactivated after 60 days.
Please check our original release note via Support > Platform Releases > Release 04.136 for detailed information and how to reactivate inactive users.
TEST: 16 January 2020 | PROD: 29 January 2020
To enhance your customer's experience during the payment process, we implemented improvements on our Responsive payment page template.
- All payment methods on the payment method selection screen can now be selected by clicking on the respective icons
- The generic credit card icon in the card number field has been removed