ID TECH SecureHead SPI with TMIV User Manual
Page | 33
6.9.
Track Hashed Data
SecureHead reader uses SHA-1 to generate hashed data for both Track1, Track2 and Track3
unencrypted data. It is 20 bytes long for each track. This is provided with two purposes in mind: One
is for the host to ensure data integrity by comparing this field with a SHA-1 hash of the decrypted
Track data, prevent unexpected noise in data transmission. The other purpose is to enable the host to
store a token of card data for future use without keeping the sensitive card holder data. This token
may be used for comparison with the stored hash data to determine if they are from the same card.
6.9.1.
Encryption Output Format Setting
Command:
53 85 01 <Encryption Format>
Encryption Format:
‘0’: No longer supported
‘1’: Enhanced Encryption Format
6.9.2.
Encryption Option Setting (for enhanced encryption format only)
Command:
53 84 01 <Encryption Option>
Encryption Option: (default 08h)
bit 0:
1: Track1 force encrypt
bit 1
1: Track2 force encrypt
bit 2
1: Track3 force encrypt
bit 3
1: Track3 force encrypt when card type is 0
Note:
1.
When force encrypt is set, this track will always be encrypted, regardless of card type.
No clear/mask text will be sent.
2.
If and only if in enhanced encryption format, each track is encrypted separately.
Encrypted data length will round up to 8 or 16 bytes.
3.
When force encrypt is not set, the data will be encrypted in original encryption format,
that is, only Track1 and Track2 of type 0 cards (ABA bank cards) will be encrypted.
6.9.3.
Hash Option Setting:
Command:
53 5C 01 <Hash Option>
Hash Option: (‘0’ –
‘7’
)
bit0
1: track1 hash will be sent if data is encrypted
bit1
1: track2 hash will be sent if data is encrypted
bit2
1: track3 hash will be sent if data is encrypted