The Online Payments solution of CCV is constantly evolving and improving to provide users with the best possible experience. It is designed to streamline the payment process, making it convenient and efficient for both customers and businesses. In October 2022, a new version was released which brings important additions to our suite of payment tools, and we are excited to offer it to our users. We believe that this new release will be a valuable addition to the Online Payments solution of CCV.
More information about CCV Online Payments can be found here: https://www.ccv.eu/en/solutions/payment-services/ccv-online-payments/
Rebranding to new CCV style
CCV is rebranding. More information about this can be found here: https://www.ccv.eu/en/about-us/our-story/rebranding/
All visual elements of the Online Payments software were updated to reflect this new CCV style (logo, font, colors). Some examples of this new style can be found in the images below.
Default 3DS2 version to 2.2.0
3DS2 has two versions active: 2.1.0 and 2.2.0. Using version 2.2.0 optimizes the authentication rate of transactions. Therefore, unless there is an explicit reason to use 2.1.0, 2.2.0 should be always used. With this release, if the 3DS2 version is not configured, it is now defaulted to the latest version 2.2.0.
Important bugfixes
A number of bugfixes were resolved with this release. The following are worth to mention:
- When using a test API key with the 3DS1 setting on “Proceed if unknown”, the authentication fails when 3DS2 is falled back to 3DS1. This was fixed.
- When a vault transaction is initiated, the transaction type “Store in Vault” is not shown in the MyCCV transaction overview. This was now added.
- If at any time the VPOS is temporary unavailable, it is possible that the communication with an external software application is interrupted. If this happens during the payout procedure, this might cause an incomplete payout to the merchant. This can mean that part of the payout is delayed until the next day. A retry mechanism was added to prevent this from happening.
- In rare cases, the 3DS server incorrectly responds an error message “invalid card range”, causing a VISA transaction to fail. This was resolved.