Fast Data Masker (FDM) HashCard1 Masking Function

book

Article ID: 144358

calendar_today

Updated On:

Products

CA Test Data Manager (Data Finder / Grid Tools)

Issue/Introduction

We have an issue masking credit card number.

I need to mask credit card numbers. The length of the card numbers is always 16.

For my requirement, I need to keep the first 7 digit so I the credit cart type (VISA, MC, etc) are kept.

I would like to know if there is a masking function that let's me retain the first "x" digits, where "x" is a number and it need to recalculate the check digit.

The masking function would produces unique values as long as the original values are also unique.

Is there any masking function that would work with my requirement? 

 

It needs to work on ZOS, Oracle, SQL SERVER, DB2, etc.


FORMATENCRYPT doesn't recalculate the check digit.  I need a valid card number.

 Have you other suggestion who

 - generate valid card number 
 - keep the first 7 digit
 - produces unique values as long as the original values are also unique

Environment

Release : 4.8

Component : CA Test Data Manager

Resolution

This is a new masking added to Fast Data Masker, which is available in the FastDataMasker-4.8.157.0 patch, and will be included in the upcoming GA release of 4.9.

The usage for the HashCard1 masking function is described below.
 

 
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.