Track 1 and 2 Block Diagram Magnetic strips are logically divided into tracks or records that is used for storing the data required during financial transaction.
Tracks are placed in a sequential order where Track 1 is followed by Track 2 and 3.
The reading of data also follows the same order. Track 1 and 2 are mostly used for storing crucial data. Track 3 is used for storing optional data. Depending on the banks choice, they can either store financial details either on Track 1 or Track 2. Both these tracks follow specific format for storing the data. Let us give a quick look at the block diagram of both these tracks to understand the format in which the data is stored and read on these tracks:
TRACK 1 BLOCK:
SS: start sentinel(%)
FC: format code
PAN: primary account number
FS: field seperator (^)
CN: card holder's name(up to 26 characters long)
ED: expiray date (in the form YYMM)
SC: service code
DD: discretionary date(may include the card verification(CVV) value/code, or the PIN verification value, and the PIN verification key indicator)
ES: end sentinel(?)
LRC: longitudinal redundancy check
TRACK 2 BLOCK:
SS: start sentinel(
PAN: primary account number
FS: field seperator(=)
ED: expiray date (in the for YYMM)
SC: service code
DD: discretionary data
ES: end sentinel(?)
LRC: longitudinal redundancy check
Both Track 1 and 2 store information in blocks where each block represents specific value, each having a particular storage limit and separated by delimiters. Let us take the example of track 1 data dump once again and analyze it based on the fields mentioned above.
Track 1: G8096654104697113^DAVID/JACOBS ^08061012735900521000000?
Consider no values for SS and FC, The first seventeen characters represent the Bank Account number (G8096654104697113) followed by the field separator (^) and Account holder’s name (DAVID/JACOBS). The next four characters represent expiry duration of the card in YYMM format (0806). The next few digits follows are
the Service code (1012735900) and Identification number (521). The next few digits are the filers for the remaining bytes. Similarly we can also read the Track 2 data. The point to note here is that Track 1 data is sufficient information when dealing with card dumps. It contains enough information to be converted into Track 2
dump as well. There are online tools available as well to do the conversion with ease. Trackgenerator.net is one such online service.
Tracks are placed in a sequential order where Track 1 is followed by Track 2 and 3.
The reading of data also follows the same order. Track 1 and 2 are mostly used for storing crucial data. Track 3 is used for storing optional data. Depending on the banks choice, they can either store financial details either on Track 1 or Track 2. Both these tracks follow specific format for storing the data. Let us give a quick look at the block diagram of both these tracks to understand the format in which the data is stored and read on these tracks:
TRACK 1 BLOCK:
SS: start sentinel(%)
FC: format code
PAN: primary account number
FS: field seperator (^)
CN: card holder's name(up to 26 characters long)
ED: expiray date (in the form YYMM)
SC: service code
DD: discretionary date(may include the card verification(CVV) value/code, or the PIN verification value, and the PIN verification key indicator)
ES: end sentinel(?)
LRC: longitudinal redundancy check
TRACK 2 BLOCK:
SS: start sentinel(
PAN: primary account number
FS: field seperator(=)
ED: expiray date (in the for YYMM)
SC: service code
DD: discretionary data
ES: end sentinel(?)
LRC: longitudinal redundancy check
Both Track 1 and 2 store information in blocks where each block represents specific value, each having a particular storage limit and separated by delimiters. Let us take the example of track 1 data dump once again and analyze it based on the fields mentioned above.
Track 1: G8096654104697113^DAVID/JACOBS ^08061012735900521000000?
Consider no values for SS and FC, The first seventeen characters represent the Bank Account number (G8096654104697113) followed by the field separator (^) and Account holder’s name (DAVID/JACOBS). The next four characters represent expiry duration of the card in YYMM format (0806). The next few digits follows are
the Service code (1012735900) and Identification number (521). The next few digits are the filers for the remaining bytes. Similarly we can also read the Track 2 data. The point to note here is that Track 1 data is sufficient information when dealing with card dumps. It contains enough information to be converted into Track 2
dump as well. There are online tools available as well to do the conversion with ease. Trackgenerator.net is one such online service.
