Copyright © 2010-2014, International Technologies & Systems Corp. All rights reserved.
Page 45 of 74
SecureMag User Manual
Field 8 (Clear/mask data sent status) and field 9 (Encrypted/Hash data sent
status) will only be sent out in enhanced encryption format.
Field 8: Clear/masked data sent status byte:
Bit 0: 1 —track 1 clear/mask data present
Bit 1: 1— track 2 clear/mask data present
Bit 2: 1— track 3 clear/mask data present
Bit 3: 0— reserved for future use
Bit 4: 0— reserved for future use
Bit 5: 0— reserved for future use
Note 4: Encrypted/Hash data sent status
Field 9: Encrypted data sent status
Bit 0: 1— track 1 encrypted data present
Bit 1: 1— track 2 encrypted data present
Bit 2: 1— track 3 encrypted data present
Bit 3: 1— track 1 hash data present
Bit 4: 1— track 2 hash data present
Bit 5: 1— track 3 hash data present
Bit 6: 1—session ID present
Bit 7: 1—KSN present
10.6
Additional Description
Except for USBKB and PS2 interfaces, track formatting (preamble, prefix,
separator, etc.) is not supported in a reader set to send encrypted track data. The
track data is always sent in the same format that is with no special formatting so
that the program doing the decoding can know where is data field is located. For
USBKB and PS2 interfaces, preamble and postamble will be available in the
encrypted track data
T1, T2 or T3 Data Length: Each byte value indicates how many bytes of decoded
card data are in the track data field. This value will be zero if there was no data on
the track or if there was an error decoding the track.
The hashed data may optionally be omitted, and also track 3 may be hashed and
included.
Track 1 and Track 2 unencrypted Length