Page 12
Table 7-2. Selectable Configuration of Google Wallet transaction mode........11 Table 7-3. Card Data Output mode for different types of card and reader configurations ..11 Table 7-4. Google Wallet Data Transmission Tag Format............11 UIC Bezel5 Programmer’s Manual Page.12/166 UDN PM098 Rev. 1.0...
LCD refresh is complete. For hardware reset, please hold the reset button for 8 seconds. The reader will reset after the button is released. UIC Bezel5 Programmer’s Manual Page.17/166 UDN PM098 Rev. 1.0...
The contactless smart card payment card reader is mainly used to support the contactless payment operations in the vending machine stations. The reader communicates with a host computer or terminal using a standard RS-232 or USB interface. UIC Bezel5 Programmer’s Manual Page.18/166 UDN PM098 Rev. 1.0...
Self-Arm / Host poll Mode: Under this mode, the reader will read and transmit payment card 1 Payment card – the card with MasterCard PayPass, VISA payWave, ExpressPay, or Discover Zip application. UIC Bezel5 Programmer’s Manual Page.19/166 UDN PM098 Rev. 1.0...
Page 20
Complete, transaction has been completed by the reader and the card can be removed now. Card Remove Warning/Bad card read/Transaction Terminated, if card was not remove, red LED will light on to remind cardholder remove the card. UIC Bezel5 Programmer’s Manual Page.20/166 UDN PM098 Rev. 1.0...
Yes (per merchant request) Table 3-1. Default Configuration settings 2 Payment cards– the card with MasterCard PayPass, VISA payWave, ExpressPay, or Discover Zip application. 3 Please contact UIC support team for more detailed information. UIC Bezel5 Programmer’s Manual Page.26/166 UDN PM098 Rev. 1.0...
<BCC>. The <BCC> is an XOR of the characters (8 bits) in the entire message, including <SOH>. Format: <SOH><ADDRESS><00Hex><COUNT><MESSAGE><BCC> UIC Bezel5 Programmer’s Manual Page.28/166 UDN PM098 Rev. 1.0...
Page 29
For the applications with the short latency requirement, please choose Protocol 2. The reader processes the incoming command right after received a complete packet. If the application requests to exchange the binary data, Protocol 2 is recommended. UIC Bezel5 Programmer’s Manual Page.29/166 UDN PM098 Rev. 1.0...
Page 35
EMV initialization. The controller must be able to handle this kind of process to accept the data from the acquirer. Then converts it to the suitable data format and send to the bezel. UIC Bezel5 Programmer’s Manual Page.35/166 UDN PM098 Rev. 1.0...
‘=’. The transaction data object field is empty if the data object is absent in the card. Moreover, the track 3 data begins with start sentinel and ends with end sentinel. UIC Bezel5 Programmer’s Manual Page.36/166 UDN PM098 Rev. 1.0...
Data objects that have the alphanumeric (an) or alphanumeric special (ans) formats are ASCII encoded, left justified and padded with trailing hexadecimal zeros. UIC Bezel5 Programmer’s Manual Page.39/166 UDN PM098 Rev. 1.0...
The interval between 2 beeps in unit of 10 milliseconds; 00h means 10ms, FFh means 2560ms. Note: If Type parameter is omitted, reader will treat it as the ONE SHORT Beep command. UIC Bezel5 Programmer’s Manual Page.57/166 UDN PM098 Rev. 1.0...
We recommend users to use Protocol 2 (USI2) in their “host-polled” applications. This protocol contains the header, message counter and block check character. It is better than using Protocol 0(USI0) as it can prevent the data to be misinterpreted but requires more redundant bytes. UIC Bezel5 Programmer’s Manual Page.67/166 UDN PM098 Rev. 1.0...
Binary Hex(00h to FFh), please refer to ISO 14443-3 for detailed information. If the [AFI] and [PARAM] fields do not appear in the request command, reader will set the request mode to WUPB automatically. UIC Bezel5 Programmer’s Manual Page.88/166 UDN PM098 Rev. 1.0...
(6AH) – Load MIFARE Key(Supports MIFARE Classic only) Saves up to 5 key sets for MIFARE Classic card application Note: For security reasons, there is no way to retrieve the keys. UIC Bezel5 Programmer’s Manual Page.94/166 UDN PM098 Rev. 1.0...
For the duplicate tags, the reader always overwrites the earlier tag value by the latter tag. The reader accepts the partial data update TLV data. See appendix A for the application terminal default value. UIC Bezel5 Programmer’s Manual Page.101/166 UDN PM098 Rev. 1.0...
4. The encrypted output data of the USB HID report is in binary format. The reader encryption is enabled as default by the factory. It requires an authentication if the user UIC Bezel5 Programmer’s Manual Page.117/166 UDN PM098 Rev. 1.0...
6.3. Operation Flow The reader is in the UIC factory to Creation UIC Factory preload the encryption key. Operation - The system integrator updates the Field Site/ Administration key and load the session ID. Operation – General The merchant operates the reader...
(i.e. slot 1 then slot 2). If slot 1 is active with the key available, the reader will use the key for the data encryption. If slot 1 is inactive (empty or terminated) but slot 2 is active, the UIC Bezel5 Programmer’s Manual Page.121/166 UDN PM098 Rev.
Page 126
0001: Google Wallet available only but neither Google payment MID nor other contactless payment available. 0100: Google Wallet not available but Contactless PayPass available. 0011: Google Wallet is available and the data of Google payment MID is available in track 1 and 2. UIC Bezel5 Programmer’s Manual Page.126/166 UDN PM098 Rev. 1.0...
There is no output data if the CRC of all applications are erroneous. The data sequence for multiple bytes value is in big-endian. For Example, [01 02] = 1 x 256 + 2 = 258. UIC Bezel5 Programmer’s Manual Page.149/166 UDN PM098 Rev. 1.0...
The Loyalty Identifier number is a number assigned by ISIS that can be loaded to the NFC reader. It reserves a maximum of 50 records of the loyalty ID (total bytes should not exceed 256 bytes). UIC Bezel5 Programmer’s Manual Page.163/166 UDN PM098 Rev.
Need help?
Do you have a question about the Bezel 5 and is the answer not in the manual?
Questions and answers