4.7.1. Samsung Pay Encoding/Decoding
Special track decoding considerations apply to Samsung Pay interactions. Samsung Pay/MST
(LoopPay) sends out a magnetic signal to a magnetic head. So MCUs may receive identical magnetic
signals on all tracks. However, Samsung Pay devices send out Track1 and Track2 data consecutively,
making it possible to disambiguate the tracks.
If the reading device receives identical MSR data for multiple tracks, MSR processing will ignore
Track2 and Track3 data if the card data is ISO 7-bit encoded, treating it as Track1 data . If the data are
5-bit encoded, it is received as Track2 data only.
If MSR receives single track data corresponding to ABA, IATA, or ISO 4909, but not in the expected
track, the data will be ignored to avoid capturing track data as an incorrect type. The processor will
not move data from one track to another.
4.8. Review Settings
Command: <STX><R><1Fh><ETX><CheckSum>
This command does not have any <FuncData>. It activates the review settings command.
SecureHead sends back an <ACK> and <Response>.
<Response> format:
The current setting data block is a collection of many function-setting blocks <FuncSETBLOCK> as
follows:
<STX><FuncSETBLOCK1>...<FuncSETBLOCKn><ETX><CheckSum>
Each function-setting block <FuncSETBLOCK> has the following format:
<FuncID><Len><FuncData>
Where:
<FuncID> is one byte identifying the setting(s) for the function.
•
<Len> is a one-byte length count for the following function-setting block <FuncData>
•
<FuncData> is the current setting for this function. It has the same format as in the sending
•
command for this function.
<FuncSETBLOCK> are in the order of their Function ID<FuncID>
•
4.9. Review Firmware Version
Command: <STX><R><22h><ETX><CheckSum>
This command gets the device firmware version.
ID TECH SecureHead SPI with TMIV User Manual
Page | 18
Need help?
Do you have a question about the SecureHead SPI and is the answer not in the manual?