User's Manual

PIN Pad 791 Programmer’s Manual (PCI POS-A) UDN PM0103-U Rev. 06

Section 6 – Contact EMV Level 2 transaction messages 2015-04-20

Page69

Uniform Industrial Corp. Proprietary and Confidential Total 342 pages

Message T01 Terminal Configuration Setup

Format: <STX>T01[Pkt No.][Total Pkts]<SUB>[DO]<ETX>[LRC]

Message length: Variable.

Usage: Host can use this command to send terminal configuration data to PIN pad, this

command can be sent many times. PIN pad will save those data inside and apply

those data when do the transaction. PIN pad will send the message T02 (Terminal

Configuration Setup Response) to host.

Message element:

Field Length

Value and description

T01 3 Message ID

Pkt No. 1 Decimal. Packet sequence number (1 ~ 9)(ex. 2)

Total Pkts 1 Decimal. Total packets (1~9)(ex. 8).

<SUB> 1 <1A, Optional, only if [DO] is existed

DO Var. Data Object, format as below

[LRC] 1 Checksum

Data Object Format: each data object is delimited by <SUB>, and each field inside each data

object is delimited by <FS>.

Data Format: (Please also refer to EMV 4.3 BOOK3, section 4.3)

Format

Description

1 a - Alphabetic data (a ~z, A~Z)

2 b - unsigned binary numbers or bit combinations

3 an - Alphanumeric data (a ~z, A~Z, 0~9)

4 ans - Alphanumeric Special data (Characters defined in ISO8859)

5 cn - Compressed numeric data (0~9, left justify, pad hexadecimal ‘F’s. Ex. 12 34 56 12 3F FF)

6 n - Numeric data (0~9, right justify, pad leading hexadecimal zeroes. Ex. 00 00 00 01 23 45)

7 var - Variable data (Any bit combination)

Note. User has to obey the restriction specified in EMV 4.3 BOOK3, Annex A and Appendix D of

this document to load configuration data. PIN pad will check if the length of each

configuration data item is consistent. Any inconsistent data item will make data loading

fail.

Note. If the data format is ‘2’ (binary), ‘5’(compressed numeric), ‘6’(numeric) or ‘7’(variable data),

it can not be allocated in message T01 directly. It should be transferred into hexadecimal

string and then allocated in message T01.