search cancel

The new implemented HASHCARD1 function in 4.9

book

Article ID: 200459

calendar_today

Updated On:

Products

CA Test Data Manager (Data Finder / Grid Tools)

Issue/Introduction

Can you share more details on the new HASHCARD1 masking function implemented in version 4.9

Environment

Release : 4.9

Component : CA Test Data Manager

Resolution

 

The new Hashcard1 dialog has the following fields: 

Card Start Position: Position where the credit card number starts into a String. Default value is 1.
Ex.: ABC1234567890123456 => Let’s suppose that Card Start Position is 4.
Card End Position: Position where the credit card number ends into a String. Default value is 16. 
Ex.: 1234567890123456ABC => Let’s suppose that Card End Position is 17.
Mask Start Position: Position into a credit card number, where FDM will start masking. Default value is 1.
Ex.: 1234567890123456 => Let’s suppose that Mask Start Position is 4.
Mask End Position: Position into a credit card number, where FDM will start masking. Default value is 16. 
Ex.: 1234567890123456 => Let’s suppose that Mask End Position is 14.
Master Key: Custom user key that will be mixed with internal key set as we have in FORMATENCRYPT1. Follow the same rules that we have in the FORMATENCRYPT1.
 
Custom End Digits: Full sentence of digits that will not be masked in the end of credit card number. The check digit will not be updated.
Ex.: 1234567890123000 => Let’s suppose that Custom End Digits is 00.
 
PS.:
In case of credit card number haven't a valid size, the number will be encrypted and it will remain invalid and same size number.
In case found null0 or 0000000000000000, the field value will not be changed.
 
 
For more information , please refer the documentation links

Attachments