Subscribe and Retain Features
Security - Update Key Management and Cryptographic Algorithm
In this release, a new feature has been added that updates Vindicia’s key management and cryptographic algorithms. This change empowers our decryption servers with a secure and efficient method of generating new credit card certificates via an API call to AWS KMS (Key Management System). Certificates are used to decrypt the encrypted Credit Cards. To achieve this, we are implementing the following changes to our credit card certificate generation process:- Adding the ability to generate a new data key from AWS KMS on demand via a secure API call.
- Improving the way we transport the data key generated from AWS KMS to distribute and use the same in the Decryption Server pool.
- Changing to the way we encrypt/decrypt data using an asymmetric key.
- Added the ability to revoke & rotate the KMS key via the KMS console.
Hosted PCI Integration - Detokenization Support
This feature allows the encrypted HPCI records file to be uploaded via API. The new file upload API is designed to accept encrypted HPCI records file. The API provides a success or failure response, indicating whether the file has been successfully uploaded or not. All submitted records are sent to Retain. Additionally, a response file is uploaded on SFTP that shows if the record was successfully submitted to Retain. VIN-20422Retain Portal - Transaction Upload with Embedded Flat File Software
From this release, submitting your failed transactions to Vindicia Retain can be performed from the Retain Merchant Portal as a file upload. The Transaction upload uses Flat File software to provide a simple and automatic interface allowing accelerated data onboarding by submitting a single file with all the Transactions. The advanced file upload technology will validate and also auto-correct the provided details , when possible, in that way shortening the time from decision to actual usage and Transaction recovery. In the Retain Portal, users use the Upload > Upload Transaction menu,to access the upload functionality. . As is always true in Retain, credit cards and tokens can be accepted. The upload process is a secure encrypted environment and therefore full credit card account numbers can be provided, with no encryption. Once the file is uploaded and validated in the upload flow, it can either be downloaded or submitted. Data gathering and preparation details are provided as part of the interface and in the documentation on the Knowledge Center. For more details, see the Retain Portal User Guide - Transaction Upload chapter. (VIN-19478, VIN-19510)Retain API REST Services
In previous releases, we added the new Retain REST APIs in the Staging environment. For more details, see the Retain OpenAPIs. The following Retain APIs are available:Report Features
Improvements to the Subscribe and Reports 2.0 (Catalina) Integration
The following changes were made to the Subscribe and Reports 2.0 (Catalina) integration:- The Reports 2.0 Server can now publish a message when:
- A schedule report is started
- A report is generated
- Subscribe Listens to the new messages, and updates the events in the database.
- Reports are no longer downloaded to Subscribe repository. Reports are now saved in Reports 2.0 only.
Internal Fixes
The following issues were solved in this release:Known Issues
The following known issues currently exist with the new Retain functionality:- Retain Transactions can’t be searched or viewed in the Retain Merchant Portal or through the new Retain REST API as the Event broker has been disabled. Fixes for scalability (SYS-26496) and UTF-8 character encoding (VIN-22810/VIN-22203) are planned.
- Users must enter an Expiration Date value in files with tokens, even though it is not a required field in the template. The issue will be fixed. (MICRO-342)
- Users must enter credit card details, even though it is not required for non-tokenized Transactions. The issue will be fixed. (VIN-22843)
- Credit card ingestion issue in Retain API. The issue will be fixed. (MICRO-334)
- End-to-end latency issues for Transaction submission via API. The issue will be fixed. Meanwhile, the feature is usable. (VIN-22770)