Changelog
November 2024 Release (04.163) |
|
TEST: 14 October 2024 | PROD: 30 October 2024 |
There is no content for this release.
April 2024 Release (04.161) |
|
TEST: 9 April 2024 | PROD: 23 April 2024 |
There is no content for this release.
January 2024 Release (04.160) |
|
TEST: 24 January 2024 | PROD: 7 February 2024 |
There is no content for this release.
November 2023 Release (04.159) |
|
TEST: 25 October 2023 | PROD: 7 November 2023 |
Integration
There is no content for this release.
September 2023 Release (04.158) |
|
TEST: 12 September 2023 | PROD: 26 September 2023 |
Integration
There is no content for this release.
July 2023 Release (04.157) |
|
TEST: 28 June 2023 | PROD: 12 July 2023 |
Integration
We have updated the Visa/Mastercard reattempt management mechanism, taking the different time periods that apply to the schemes into account.
Make sure to comply to this rule as explained here.
May 2023 Release (04.156) |
|
TEST: 25 April 2023 | PROD: 9 May 2023 |
Integration
We have implemented the Visa/Mastercard reattempt management mechanism, reducing the number of retries for declined transactions.
Make sure to comply to this rule as explained here.
March 2023 Release (04.155) |
|
TEST: 15 March 2023 | PROD: 29 March 2023 |
There is no content for this release.
January 2023 Release (04.154) |
|
TEST: 25 January 2023 | PROD: 8 February 2023 |
There is no content for this release.
November 2022 Release (04.153) |
|
TEST: 12 October 2022 | PROD: 26 October 2022 |
There is no content for this release.
September 2022 Release (04.152) |
|
TEST: 24 August 2022 | PROD: 7 September 2022 |
Interface
We have added parameters to the dynamic file structure of our Reporting tool. This can help you to follow-up on your transactions for granted 3-D Secure exemptions (ThreeDsExemption) and the SCA scenario (ThreeDsChallengeIndicator) for each of your transactions.
July 2022 Release (04.151) |
|
TEST: 22 June 2022 | PROD: 6 July 2022 |
There is no content for this release.
May 2022 Release (04.150) |
|
TEST: 4 May 2022 | PROD: 18 May 2022 |
There is no content for this release.
March 2022 Release (04.149) |
|
TEST: 16 March 2022 | PROD: 30 March 2022 |
There is no content for this release.
January 2022 Release (04.148) |
|
TEST: 18 January 2022 | PROD: 01 February 2022 |
Integration
We have updated our documentation with detailed information how to treat 3-D Secure v2 transactions effectively in specific scenarios:
- Understand and handle fallback to 3-D Secure v1
- Handle exclusions/exemptions and frictionless/challenge flow for 3-D Secure v2 transactions
- Added an infobox about the new Back Office field "3DS Liability" in our 3-D Secure status guide
API
We enhanced the use of customer IP address, so you are now able to send IP addresses in version 6.
November 2021 Release (04.147) |
|
TEST: 20 October 2021 | PROD: 3 November 2021 |
Integration
Added a new chapter in our 3-D Secure status guide, informing you about the gradual decommission of 3-D Secure v1.
September 2021 Release (04.146) |
|
TEST: 1 September 2021 | PROD: 15 September 2021 |
There is no content for this release.
July 2021 Release (04.145) |
|
TEST: 14 July 2021 | PROD: 28 July 2021 |
Integration
A new version of our Parameter Cookbook is online.
Integration
A new version of our Alias Manager (Tokenization) guide is online.
March 2021 Release (04.143) |
|
TEST: 17 March 2021 | PROD: 31 March 2021 |
API
With the continuous improvement of the version 2 of 3-D Secure, we are proud to offer you more parameters for secure transactions, such as:
- Enhanced: Mpi.threeDSRequestorChallengeIndicator
- New: Mpi.merchantFraudRate
- New: Mpi.secureCorporatePayment
- New: BROWSERJAVASCRIPTENABLED (available for DirectLink Visa transactions. MasterCard and Amex coming soon). Check out the dedicated chapter how it works)
January 2021 Release (04.142) |
|
TEST: 20 January 2021 | PROD: 2 February 2021 |
API
3DSv2 feedback parameter CH_AUTHENTICATION_INFO is now available. Check out our e-Commerce and DirectLink guides to learn more.
September 2020 Release (04.140) |
|
TEST: 9 September 2020 | PROD: 23 September 2020 |
Integration
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.
Integration
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.
July 2020 Release (04.139) |
|
TEST: 1 July 2020 | PROD: 23 July 2020 |
Payment methods
Payment method Carte Bancaire (CB) becomes a true Payment Method following the implementation of the European Regulation 2015/751.
Check out what you have to do for your eCommerce or DirectLink integration to comply to this rule.
March 2020 Release (04. 137) |
|
TEST: 11 March 2020 | PROD: 20 May 2020 |
Integration
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.
Interface
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.
January 2020 Release (04. 136) |
|
TEST: 16 January 2020 | PROD: 29 January 2020 |
Integration
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