IDTECH MiniSmart II Installation manual

80161508-001
MiniSmart II
Secure Smart Card Reader
Command Interface
August 2, 2019
2018 Rev. C
ID TECH
10721 Walker Street, Cypress, CA90630 Voice: [phone] Fax: [phone]

MiniSmart II
1
Copyright © 2018 ID TECH. All rights reserved.
ID TECH
10721 Walker St.
Cypress, CA 90630
[e-mail] Visit: http://www.idtechproducts.com
This document, as well as the software and hardware described in it, is furnished under
license and may be used or copied online in accordance with the terms of such license.
The content of this document is furnished for information use only, is subject to change
without notice, and should not be construed as a commitment by ID TECH. While
every effort has been made to ensure the accuracy of the information provided, ID
TECH assumes no responsibility or liability for any unintentional errors or inaccuracies
that may appear in this document.
Except as permitted by such license, no part of this publication may be reproduced or
transmitted by electronic, mechanical, recording, or otherwise, or translated into any
language form without the express written consent of ID TECH.
ID TECH and ViVOpay are trademarks or registered trademarks of ID TECH.
Warranty Disclaimer: The services and hardware are provided "as is" and "as-available"
and the use of the services and hardware is at its own risk. ID TECH does not make,
and hereby disclaims, any and all other express or implied warranties, including, but not
limited to, warranties of merchantability, fitness for a particular purpose, title, and any
warranties arising from a course of dealing, usage, or trade practice. ID TECH does not
warrant that the services or hardware will be uninterrupted, error-free, or completely
secure.

MiniSmart II
2
Contents
INTRODUCTION ........................................................................................................................................................................ 3
USB-HID INTERFACE ............................................................................................................................................................... 3
COMMAND/RESPONSE FORMAT ......................................................................................................................................... 3
COMMANDS................................................................................................................................................................................ 5
Default RS232 Group ............................................................................................................................................................. 14
Review RS232 Group ............................................................................................................................................................. 14
Smart Card Group (ICC EMV Level Two Task) – Function Command.......................................................................... 16
SETTING TRANSACTION PARAMETERS ......................................................................................................................... 16
Smart Card Group – Set/Get Commands Misc. .................................................................................................................. 29
TR-31 Block data format is: KBH + KBH_OB (Optional Block) + ASCII code Result + ASCII code MAC data. ............. 35
FIRMWARE UPDATING ......................................................................................................................................................... 36
Application/Bootloader FM File Structure .......................................................................................................................... 36
Definitions............................................................................................................................................................................ 37
Block 1 Data......................................................................................................................................................................... 37
Block 2 Data......................................................................................................................................................................... 37
Block 3 Data......................................................................................................................................................................... 38
Block 4 Data......................................................................................................................................................................... 38
DEVICE EXAMPLES................................................................................................................................................................ 39
Example 1............................................................................................................................................................................. 39
Example 2............................................................................................................................................................................. 39
Example 3............................................................................................................................................................................. 39
Entering Bootloader Mode................................................................................................................................................... 39
Bootloader Status - Process ................................................................................................................................................. 40
FM File Data - Process........................................................................................................................................................ 40
BOOTLOADER ERROR CODES............................................................................................................................................ 42
RESPONSE CODES................................................................................................................................................................... 46
Note:..................................................................................................................................................................................... 49
TIMINGS: GENERAL PURPOSE COMMANDS.................................................................................................................. 50

MiniSmart II
3
Introduction
The MiniSmart II is ID TECH’s latest EMV-compliant ICC module. The MiniSmart II,
certified for EMV Level 1 and Level 2, combines a proven EMV kernel with a compact
33mm x 66mm form factor and supports USB, UART, and RS-232 communication,
allowing for smooth integration into a variety of payment environments.
With EMV acceptance now an international payment standard, the MiniSmart II fills a
need for a compact, reliable, EMV-ready device that can serve a wide variety of space-
limited applications.
This document describes the low-level command API for the MiniSmart II, for
integrators who wish to send commands (and receive responses) to/from the device via
serial communications. ID TECH also offers (separately) a high-level-language SDK (the
"Universal SDK") for programmers who wish to target a Windows platform using C# or
Android via Java. The SDK provides a variety of convenience methods and high-level-
langauge wrappers around most of the low-level commands described in this document.
Contact your ID TECH representative to learn more about the SDK, which is free for all
customers. Also, be sure to check the ID TECH public Knowledge Base for additional
documentation, utilities, demos, and software updates:
https://atlassian.idtechproducts.com/confluence/display/KB/MiniSmart+II+-+downloads
USB-HID Interface
VID is 0xACD.
PID is 0x3410.
Reports: 64 bytes
Report type: 0
Report[0] = report length
Report[1-63] = data
If more reports to follow, Report[0]=0xBF, data length = 63.
Command/Response format
MiniSmart II uses a simple command/response protocol based on the following
packaging of messages:
NGA Protocol Format
<STX><CLenL><CLenH><Command_Body/Response_Body><CheckLRC><CheckSum><ETX>
Where:
<STX> = 0x02
<CLenL> = length, low (least significant) byte
<CLenH> = length, high byte

MiniSmart II
4
<LRC> = Overall LRC (Modulus 2 Exclusive OR) of Command/Response Body; XOR
all bytes together (as shown below).
<Checksum> = The overall sum of bytes from Command/Response Body (neglecting
overflow); add all bytes and take the low 8 bits.
<ETX> = 0x03
Example:
To get the firmware version, send
02 03 00 78 46 01 3F BF 03
The command is 78 46 01. The length is 3 bytes (note the little-endian LSB/MSB format,
hence the length is given as 03 00). The LRC is 3F; the checksum is BF. This command
can be sent in a USB-HID Report 0 of length 64, with the first byte of the report set to the
length of the data being sent.
The USB-HID response from the MiniSmart II is:
21 02 1b 00 06 49 44 20 54 45 43 48 20 4d 69 6e 69 53 6d 61 72 74 20 49
49 20 56 32 2e 30 30 21 73 03 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00
00
00
00
The report's first byte (21, in this example) is the length of the actual data.
Calculation of LRC:
public static byte[] getLRC(byte[] data)
{
byte[] lrc = new byte[1];
lrc[0] = data[0];
for (int i = 1; i < data.Length; i++)
lrc[0] ^= data[i];
return lrc;
}
// Checksum is the same as LRC except it uses addition:
// lrc[0] += data[i];
// The return value should be constrained to 8 bits (lrc & 255).

MiniSmart II
5
Commands
The following table lists the commands supported by the device, in alphabetical order (by
command name). Documentation of individual commands begins after the table.
Command Summary Table (Alphabetical by Command Name)
Command
Name
72 46 05 02
Authenticate Transaction
72 46 06
Cancel Transaction
72 46 05 03
Complete Transaction
7F 53 00
Default All
72 53 00
Default ICC Group All Settings
70 53 00
Default RS232 Group
78 46 F5
Device Enter into Load Important Data State
78 46 7A 49 52 46 57 00
00 00 00 00 00 00 00
Enter into Bootloader
78 46 F4
Erase Keys
78 46 C3 49 44 54 45 43
48
Erase Serial Number
72 46 41
Exchange APDU Plaintext
72 52 01 21
Get Ascii Mask Data
70 52 01 41
Get Baud Rate
72 52 01 22
Get BCD Mask Data
78 46 11
Get Bootloader FW Release Version (Internal Command)
72 52 01 04
Get Card Type Option
70 52 01 42
Get Data Bits
78 52 01 50
Get Date and Time
78 46 3E
Get DUKPT Key KSN
72 46 23 01
Get EMV Level One Version Number
72 46 08 01
Get EMV Level Two Version Number
72 52 01 02
Get Encryption Mode for Data encryption Key (ICC
DUKPT Key)
78 46 01
Get Firmware Release Version
72 52 01 05
Get ICC L1 Transaction Timeout
72 46 09 13
Get ICC L2 AID List Check Value
72 46 09 14
Get ICC L2 CA Public Key Check Value
72 46 09 02
Get ICC L2 Configuration Check Value
72 46 09 01
Get ICC L2 Kernel Check Value
72 46 24
Get ICC Reader Status
72 52 01 03
Get ICC Voltage Option(Internal Command)
72 46 86 01
Get Interface Device Serial Number
72 46 23 02
Get Internal EMV Level One Version Number

MiniSmart II
6
72 46 08 02
Get Internal EMV Level Two Version Number
78 31
Get Internal Firmware Version
78 46 30
Get Key Status
72 52 01 01
Get Key Type for Data encryption Key (ICC DUKPT Key)
78 46 20
Get Model Number
70 52 01 43
Get Parity
72 52 01 20
Get Pre/Post Data Len
78 52 01 01
Get Remote Key Injection Timeout
78 46 02
Get Serial Number
78 46 25
Get Status for Key
70 52 01 45
Get Stop Bits
78 46 50
Implement Self-Test function for Non-PCI device
75 46 31
Load App Firmware Check Value (Internal Command)
75 46 33
Load Bootloader Firmware Check Value (Internal
Command)
75 46 17
Load Firmware Key (Internal Command)
78 46 F3
Load Key
78 46 F2
Load LCL-KEK (Internal Command)
75 46 16
Load Manufacture Key (Internal Command)
72 46 4D
Power Off
72 46 6E
Power On (Get ATR)
72 46 01 04
Remove All Application Data
72 46 04 04
Remove All CA Public Key List
72 46 85 04
Remove All Certification Revocation List
72 46 01 02
Remove Application Data
72 46 04 02
Remove CA Public Key
72 46 85 02
Remove Certification Revocation List
72 46 02 02
Remove Terminal Data
72 46 0A 02
Remove Transaction Amount Log
78 46 49
Reset
72 46 03 01
Retrieve AID List
72 46 01 01
Retrieve Application Data
72 46 04 01
Retrieve CA Public Key
72 46 04 05
Retrieve CA Public Key List
72 46 85 01
Retrieve Certification Revocation List
72 46 02 01
Retrieve Terminal Data
72 46 87 01
Retrieve Terminal Identification
72 46 07 01
Retrieve Transaction Result
78 52 00
Review General Group
72 52 00
Review ICC Group All Setting
70 52 00
Review RS232 Group
72 46 01 03
Set Application Data
72 53 01 21 01
Set Ascii Mask Data

MiniSmart II
7
70 53 01 41 01
Set Baud Rate
72 53 01 22 01
Set BCD Mask Data
72 46 04 03
Set CA Public Key
72 53 01 04 01
Set Card Type Option
72 46 85 03
Set Certification Revocation List
78 53 01 50 08
Set Date and Time
72 53 01 02 01
Set Encryption Mode for Data encryption Key (ICC
DUKPT Key)
72 53 01 05 01
Set ICC L1 Transaction Timeout
72 53 01 03 01
Set ICC Voltage Option (Internal Command)
78 53 01 05 01
Set Idle Waiting Time
72 46 86 03
Set Interface Device Serial Number
72 53 01 01 01
Set Key Type for Data encryption Key (ICC DUKPT Key)
72 53 01 20 02
Set Pre/Post PAN Data Len
78 46 03
Set Serial Number (Internal Command)
70 53 01 45 01
Set Stop Bits
72 46 02 03
Set Terminal Data
72 46 87 03
Set Terminal Identification
72 46 05 01
Start Transaction
Get DUKPT Key KSN
Command Body is 78 46 3E <Length of Data> <KeyNameIndex> <Length of Key Slot>
<Key Slot>
Where:
<Length of Data> is 2 bytes, format is Len_L Len_H, is length of <KeyNameIndex>
<Length of Key Slot> <Key Slot>
<KeyNameIndex> is 1 byte, please refer to below table.
<Length of Key Slot> is 2 bytes, format is Len_L Len_H
<Key Slot> is any byte (1 byte or 2 bytes), value always 0.
KeyNameIndex
Key Name
0x14
LCL-KEK
0x02
Data encryption Key
0x0C
RKI-KEK
Response Body:
15 <Error Code> 78 46 3E – Invalid related Key (90 42, or 90 46, or 90 52) or Key STOP
(73 00), Or Do Not Support the Key (90 47), Or
06 78 46 3E <Length of KSN> <KSN>
Where:
<Length of KSN> is 2 bytes, format is Len_L Len_H, value always 0A 00
<KSN> is 10 bytes KSN

MiniSmart II
8
Load Key
Command Body is 78 46 F3 <Length of Data> <Length of Encrypted Key ANS.1
Structure> <Encrypted Key ANS.1 Structure> <Length of LCL-KEK KSN> <LCL-KEK
KSN>
Where:
<Length of Data> is 2 bytes, format is Len_L Len_H, is length of <Length of Encrypted
Key ANS.1 Structure> <Encrypted Key ANS.1 Structure> <Length of LCL-KEK KSN>
<LCL-KEK KSN>
<Length of Encrypted Key ANS.1 Structure> is 2 bytes, format is Len_L Len_H
<Encrypted Key ANS.1 Structure> - please refer to <80000405-001 Key Injection for
Unattended Devices A.docx> document with F3 command (Sets DUKPT Key).
<Length of LCL-KEK KSN> is 2 bytes, format is Len_L Len_H, value always 0A 00
Note: Device supports loading below Key:
KeyNameIndex
Key Name
Definition
Key Slot
Mode
Of Use
Key
Usage
0x02
Data
encryption
Key
Encrypt ICC
0
B or X
B1
0x0C
RKI-KEK
Remote Key
Injection
0
X
B1
Response Body:
15 <Error Code> 78 46 F3 - No LCL-KEK (04 00) or LCL-KEK STOP (73 00) or other,
Or
06 78 46 F3 <Length of KCV ANS.1 Structure> <KCV ANS.1 Structure>
Where:
<Length of KCV ANS.1 Structure> is 2 bytes, format is Len_L Len_H
<KCV ANS.1 Structure> - please refer to <80000405-001 Key Injection for Unattended
Devices A.docx> document with F3 command (Sets DUKPT Key). KCV is Key Check
Value, it is 3 bytes data, algorithm refer to X9.24
Get Firmware Release Version
Command Body is 78 46 01
Response Body is 06 & some bytes ASCII codes
Enter into Bootloader
Command Body is 78 46 7A 49 52 46 57 00 00 00 00 00 00 00 00
Response Body is
06 – Device has the function, or:
15 – Device has not the function.

MiniSmart II
9
Get Serial Number
Command Body is 78 46 02
Response Body is
06 + 10 bytes ASCII code Serial Number, or:
15 62 00 – No Serial Number
Get Model Number
Command Body is 78 46 20
Response Body is 06 + Model Number
Where: Model Number is “MINI2-5X” (USB-HID) or “MINI2-2X” (RS232) or “MINI2-
0X” (UART)
Reset
Command Body is 78 46 49
Response Body is 06
Note:
Device will Reset (Re-Start) after it responds ACK Response Body.
It is the Highest Priority Command in device except Key Loading State.
If Device implement the function, the Real Date/Time will be started from 2015.01.01
00:00:00.
Implement Self-Test function for Non-PCI device
Command Body is 78 46 50
Response Body is
06 – Self-Test function successful
15 75 00 – Self-Test function failed
Implementation notes:
1. App integrity checking. After failure or error, device will check 2 times again.
2. Bootloader integrity checking. After failure or error, device will check 2 times again.
3. Configuration integrity checking. After failure or error, device will check 2 times
again.
4. If Configuration data are large, the checking time increases.
Get Key Status
Command Body is 78 46 30

MiniSmart II
10
Response Body is 06 + PIN DUKPT Status + PIN Master Key Status + PIN Session Key
Status + Data encryption Key Status + Data encryption Key Status + RKI-KEK
Where:
Key
Status
Note
PIN DUKPT Key
0: None.
1: Exist
0xFF: STOP
Does not support this key.
Always 0
PIN Master Key
0: None
1: At least Exist a
Master Key
Does not support this key.
Always 0
PIN Session Key
0: None.
1: Exist
Does not support this key.
Always 0
Data encryption Key / MSR
DUKPT Key
0: None.
1: Exist
0xFF: STOP
Does not support this key.
Always 0
Data encryption Key / ICC
DUKPT Key
0: None.
1: Exist
0xFF: STOP
RKI-KEK
0: None.
1: Exist
0xFF: STOP
Get Status for Key
Command Body is 78 46 25
Response Body:
06 <Block Length> <KeyStatusBlock1> <[KeyStatusBlock2]> …<[KeyStatusBlockN]>,
Or
15 <Error Code>
Where:
<Block Length> is 2 bytes, format is Len_L Len_H, is KeyStatusBlock Number
<KeyStatusBlockX> is 4 bytes, format is <Key Index and Key Name> <keyslot> <keystatus>:
<Key Index and Key Name> is 1 byte. Please refer to following table and <80000426-
001 KeyNameIndex Database - V51.xls>
<key slot> is 2 bytes. Range is 0 – 9999
<key status> is 1 byte.
0 – Not Exist
1 – Exist
0xFF – (Stop. Only Valid for DUKPT Key)
Support <Key Index and Key Name> Table
KeyNameIndex
Key Name
Definition
Key Slot
0x14
LCL-KEK
Encrypt Other Keys
0
0x02
Data encryption Key
Encrypt ICC
0
0x0C
RKI-KEK
Remote Key Injection
0

MiniSmart II
11
Set Remote Key Injection Timeout
Command Body is 78 53 01 01 02 <Timeout_H> <Timeout_L>
Where: <Timeout_H> <Timeout_L> need be 120 seconds ~ 3600 seconds
Response Body is 06
Get Remote Key Injection Timeout
Command Body is 78 52 01 01
Response Body is 06 78 01 01 02 <Timeout_H> <Timeout_L>
Set Date & Time
Command Body is 78 53 01 50 08 <Data/Time Length> <Date Time> <MAC Length>
Where:
<Data/Time Length> is 1 bytes data – Fix is 0x06
<Data Time> is 6 bytes data – Year, Month, Date, Hour, Minute, Second
Item
Value Area (BCD Code)
Year
15~99, 00
Month
01~12
Date
01~31
Hour
00~23
Minute
00~59
Second
00~59
<MAC Length> is 1 byte data – Fix is 0x00
Response Body is 06
Note:
After Power On the device, the Real Time is starting from 2000/01/01 00:00:00, , end to
2100/01/01 00:00:00. User need set the Real Time to implement related transaction.
The command always valid in IDLE State.
If current Date/Time is 2014/08/23 15:24:59, <Date Time> should be 0x14 0x08 0x23 15
24 59 (BCD Code).
Disable Set Date/Time to Before 2012/01/01 00:00:00.
The Default Date/Time is 2015/01/01 00:00:00
Get Date & Time
Command Body is 78 52 01 50
Response Body is 06 78 01 50 06 <Date Time>

MiniSmart II
12
Where: <Data Time> is 6 bytes data – Year, Month, Date, Hour, Minute, Second
Set Idle waiting time
Command Body is 78 53 01 05 01 <Time>
Where: <Time> is 0 or 2 seconds ~ 60 seconds (Default is 2 seconds)
Response Body is 06
Note:
•If Waiting time is 0 and if interface is RS232, Disable device work into Low Power
Consumption status.
•If Waiting time is Not 0, If Idle status is more than <Time>, if interface is RS232, and if Card is
not Seated, device will enter into Low Power Consumption status.
•If device received command in Idle status, the waiting time will be reset.
•If IC card is removed, the waiting time will be reset.
Default General Group (Default All)
Command Body is 78 53 00
Response Body is 06
Below Setting should be reset to default value:
Function Name
Default Value
Note
Remote Key Injection Timeout
120 Seconds
Get Internal Firmware Version
Command Body is 78 31 – Get Internal Version
Response Body is 06 + Version Number
Review General Group
Command Body is 78 52 00
Response Body is 06 78 02 01 02 <Timeout_H> <Timeout_L>50 06<Date Time>
RS232 Group
Note:
Device will use new stop bits after it responds 0x06.
Set Baud Rate
Command Body is 70 53 01 41 01 ASCIIChar
BaudRate
ASCIIChar
9600
4

MiniSmart II
13
19200
6
38400
7
115200
9
Response Body is 06
Note:
Device will use new baud rate after it responds 0x06.
Get Baud Rate
Command Body is 70 52 01 41
Response Body is 06 70 01 41 01 ASCIIChar

MiniSmart II
14
Get Data Bits
Command Body is 70 52 01 42
Response Body is 06 70 01 42 01 38 (8 bits Data)
Get Parity
Command Body is 70 52 01 43
Response Body is 06 70 01 43 01 30 (None)
Set Stop Bits
Command Body is 70 53 01 45 01 ASCIIChar
StopBits
ASCIIChar
1
1
2
2
Response Body is 06
Get Stop Bits
Command Body is 70 52 01 45
Response Body is 06 70 01 45 01 ASCIIChar
Default RS232 Group
Command Body is 70 53 00
Response Body is 06
Below Setting should be reset to default value:
Function Name
Default Value
Baud Rate
38400
Stop Bits
1
Review RS232 Group
Command Body is 70 52 00
Response Body is 06 70 04 41 01<Baud Rate> 42 01 38 43 01 30 45<Stop Bits>

MiniSmart II
15
Smart Card Group (ICC EMV Level One Task) – Function Command
Get ICC Reader Status
Command Body is 72 46 24
Response Body is 06 + <Reader status> (1 byte)
Bit Position
‘0’
‘1’
0
ICC Power not ready
ICC Powered
1
Card not seated
Card seated
2~7
Power On (Get ATR)
Command Body is 72 46 6E
Response Body is 06 + <ATR String>
Note:
This Command is used to power up the currently selected microprocessor card. It follows
the ISO7816-3 power up sequence and returns the ATR as its response.
Power Off
Command Body is 72 46 4D
Response Body is 06
Exchange APDU Plaintext
Command Body is 72 46 41 <C-APDU>
Response Body is 06 00 <R-APDU>
Note:
If Data encryption Key (ICC DUKPT Key) was not loaded, command supported.
If Data encryption Key (ICC DUKPT Key) Exist, it is Not Supported and response Error
Code (6A 00).
Get KSN
Command Body is 72 46 62 <C-APDU>
Response Body is 06 + <10 bytes KSN> <R-APDU>
Note:
1. If Data encryption Key (ICC DUKPT Key) was not loaded, Unit should response Error
Code (04 00) for this command.

MiniSmart II
16
Get EMV Level One Version Number
Command Body is 72 46 23 01
Response Body is 06<”IFMVx.yy”>.
x.yy is version number. Fist version number is 1.00.
Smart Card Group (ICC EMV Level Two Task) – Function Command
Requires L2 kernel on device.
Setting transaction parameters
1. Send Set Application Data Command
2. Send Set Terminal Data Command
MiniSmart II Support 2C configuration, below are Terminal Data Value for 2C
configuration. Manufacture need set it.
Item
Terminal Data (TLV format)
Definition
1
9F 35 01 21
Terminal Type
2
9F 33 03 60 28 C8
Terminal Capability
3
9F 40 05 F0 00 F0 A0 01
Additional Terminal Capability
4
DF 26 01 01
Terminal Supports CRL
5
DF 10 02 65 6E
Language
6
DF 11 01 00
Not Support Transaction Log
7
DF 27 01 00
Not support Exception File
8
DF EE 15 01 01
Terminal Support ASI
9
DF EE 16 01 00
Terminal Encrypt Mode: 00=DUKPT 01=MK/SK
10
DF EE 17 01 07
Terminal Entry Mode for ICC
11
DF EE 18 01 80
Terminal Encrypt Mode for MSR
12
DF EE 1E 08 D0 DC 20 D0 C4 1E
16 00
Contact Terminal Configuration
13
DF EE 1F 01 80
Issuer Script Limit
14
DF EE 1B 08 30 30 30 31 35 31 30
30
ARC
15
DF EE 20 01 3C
ICC Power on detect waiting time
16
DF EE 21 01 0A
ICC L1 waiting time
17
DF EE 22 03 32 3C 3C
Driver time. byte 1 -> Menu. byte 2 -> Get PIN. byte
3 -> MSR
3. Send Set CA Public Key Command;

MiniSmart II
17
Host
Reader
4. Send Set Certification Revocation List command
Transaction Flow
1. Send Start Transaction Command.
2. Send Authenticate Transaction Command.
3. If received online request from terminal, send Apply Host Response command.
4. When a transaction is completed, interface will output a 06+TLVformat data list, and
transaction result (approve, or decline, or…) will display on the LCD.5. If you want to
review the transaction result you can send Retrieve Transaction Result Command,. It will
output the TLV format data refer to the Option Data list.
Note: To all above commands, if it can return ACK, execute follow steps, otherwise,
repeated it till return ACK.
Retrieve EMV Level Two Version Number command can be sent all the time.
Cancel Transaction command can be sent all the time if you want to terminate a
transaction.
offline
Online
Offline
Online
Start transaction response
Example:06 00 10 00 <TLVs>
If MSR operation , response MSR data, and
transaction is finished
Start transaction command
Example:72 46 05 01……
Authentication transaction command
Example:72 46 05 02……
Authentication response
Example :06 00 03 00 <TLVs>
Apply host command
Example :72 46 05 03……
Apply host response
Example : 06 00 02 00 <TLVs>

MiniSmart II
18
Retrieve Application Data
Command Body is 72 46 01 01 <LenL> <LenH> <5~16 bytes AID>
Where:
<LenL> <LenH> is the length of AID
Response Body is
06 <TagCounterL> <TagCounterH> <TLV1> <TLV2>…<TLVn> or
15<ErrorCode>.
Where:
<TagCounterL> <TagCounterH> is the number of <TLV>
Note:
If AID List / Application Data does not exist, response 15 F2 00.
Remove Application Data
Command Body is 72 46 01 02 <LenL> <LenH> <5~16 bytes AID>
Where:
<LenL> <LenH> is the length of AID
Response Body is 06 or
15<ErrorCode>
Note:
If AID List does not exist, response 15 F2 00.
Set Application Data
Command Body is 72 46 01 03 <LenL> <LenH> <5~16 bytes AID> <TagCounterL>
<TagCounterH> <TLV1> <TLV2>…<TLVn>.
Where:
<TagCounterL> <TagCounterH>is the Number of <TLV>.
<LenL> <LenH> is the length of AID
Response Body is
06 or
15 <ErrorCode>
Note:
If a <TLV> format was error, response 15 - F2 02 -If AID List has full (MAX is 16),
response 15 F2 03
Remove All Application Data
Command Body is 72 46 01 04
Response Body is 06

MiniSmart II
19
Retrieve Terminal Data
Command Body is 72 46 02 01
Response Body is
06 <TagCounterL> <TagCounterH> <TLV1> <TLV2>…<TLVn> or
15<ErrorCode>
Where:
<TagCounterL> <TagCounterH> is the number of <TLV>
If Terminal Data does not exist, response 15 F2 01
Remove Terminal Data
Command Body is 72 46 02 02
Response Body is
06
Set Terminal Data
Command Body is 72 46 02 03 <TagCounterL> <TagCounterH> <TLV1>
<TLV2>…<TLVn>.
Where:
<TagCounterL> <TagCounterH>: the Number of <TLV>.
Response Body is
06 or
15 <ErrorCode>
Note:
If a <TLV> format was error, response 15 F2 02
Retrieve AID List
Command Body is 72 46 03 01
Response Body is 06 <NumberL> <NumberH> <AID Block 1> <AID Block 2> … <AID
Block N>.
Where:
<NumberL> <NumberH> is Number of AID Blocks.
<AID Block> format is <LenL> <LenH> <Several bytes AID>.
Where:
<LenL> <LenH> is Length of AID
Note:
If AID List does not exist, response 15 F2 00