VeriFone e355 User And Best Practices Manual
Hide thumbs
Also See for e355:
- User manual (60 pages) ,
- Installation manual (40 pages) ,
- User manual (46 pages)
Related Manuals for VeriFone e355
Summary of Contents for VeriFone e355
- Page 1 User and Best Practices Guide Verifone Part Number DOC087-080-EN-A, Revision A...
- Page 2 Verifone, Inc. The information contained in this document is subject to change without notice. Although Verifone has attempted to ensure the accuracy of the contents of this document, this document may include errors or omissions. The examples and sample programs are for illustration only and may not be suited for your purpose.
-
Page 3: Table Of Contents
Data Flow........ - Page 4 ONTENTS H A P T E R Communication USB ............31 Interfaces USB Host .
- Page 5 Comparison of Key Features ........77 e265 vs. e355...
- Page 6 ONTENTS 355/ 265 U SER AND RACTICES UIDE...
-
Page 7: Preface
Chapter Control and Barcode Applications Chapter Key Features of e265 vs. e355 Related To learn more about the e355 terminal, refer to the following set of documents: Documentation • e355 Quick Installation Guide , VPN DOC087-062-EN • e355 Installation Guide, VPN DOC087-063-EN •... -
Page 8: Conventions And Acronyms
You must install a roll of thermal- book titles or emphasis. sensitive paper in the printer. The courier type face is Courier http://www.verifone.com used while specifying onscreen text, such as text that you would enter at a command prompt, or to provide an URL. -
Page 9: Acronym
Apple’s proprietary mobile operating system for iPhone, iPad, and iPod touch devices Negative acknowledgment, a signal is received with errors PMR-MUX2 Verifone proprietary protocol for communicating with smart devices Smart Device Refers to iPad mini, iPad mini 4, iPod, Android tablet, Windows Tablet, iPhone, Android phone, Windows phone... - Page 10 REFACE Conventions and Acronyms 355/ 265 U SER AND RACTICES UIDE...
-
Page 11: Hapter
POS transaction. In Mobile PINpad mode, the e355 unit and a smart device are used together to complete the POS transaction. The smart device and e355 connection is either wired or wireless. - Page 12 355 D EVICE Device Features Below are the terminal features on the front panel. MAGNETIC STRIPE READER 2D IMAGER LCD DISPLAY BARCODE BUTTON POWER LED INDICATOR SIDE MICRO-USB PORT KEYPAD SMART CARD READER FRAME CONNECTOR Figure 1 Front Panel Features Figure 2 shows the terminal features on the back panel.
-
Page 13: Software Features
Android, and Windows smart devices. Frame detection and configuration happen early on during e355 power-up. This means that users will need to restart e355 when they switch to a different frame configuration. The default frame configuration is Bluetooth, this is when there is no frame detected or error in frame detection occurs. -
Page 14: Bluetooth Support
Wi-Fi. VTM on the Display The e355 VTM is displayed on an LCD display unlike the e315's VTM, which is displayed on a remote PC terminal such as Hyper Terminal. VTM menu layout is similar as e315 and other Verix terminals. New menus such as software versions, barcode diagnostic, contactless diagnostic, and IPP and ADE keys KSI information are added. -
Page 15: Hapter
The e355 operates in Standalone and Mobile PINpad modes. Standalone In this mode, e355 is not attached to a smart device and not docked in modular Architecture frame. The payment application that processes the payment runs on the e355 and the payment transactions are displayed on its LCD display. -
Page 16: Mobile Pinpad Architecture
RCHITECTURE Mobile PINpad Architecture Mobile PINpad In this mode, e355 is attached to a smart device and connected via USB or Architecture Bluetooth interface. Payment application runs on the smart device and it drives the e355 to perform actions of reading card data, taking PIN number, and displaying messages on the LCD screen. -
Page 17: Virtual Communication Ports
COM1E Apple iOS device with Lightning connector uses iAP2 protocol to communicate with e355, and Apple iOS device with 30-pin connector uses iAP1 protocol to communicate with e355. Both iAP1 and iAP2 protocols use the same protocol strings on iOS device. For more information on communicating with accessory using protocol strings, refer to External Accessory Framework on the Apple developer website. -
Page 18: Device Ports
There are no applications using this port. Open and Close Events of Communication Ports The e355 sends a Connect event to its application when application on the smart device opens the port for communication. The e355 sends a Disconnect event to its application when application on smart device closes the communication port. -
Page 19: Open()
"/DEV/COM1B" "/DEV/COM1C" "/DEV/COM1D" "/DEV/COM1E" Use get_port_status() to get the status of the smart device connection. A smart device cannot open a communication port until the e355 application has opened the corresponding device. Prototype Int open(const char *devname, int attributes); Parameters devname Pointer to the null terminated device name string. -
Page 20: Read()
The actual number of bytes copied may be less than the requested count. In e355, the receive data logic drops packets larger than 1024 bytes for iOS devices and 2048 bytes for Android and Windows devices. -
Page 21: Write()
This copies the given data to system transmit buffers for transmission over the communication port. The function may return before the data is actually sent. In e355, the write() function works differently than a standard serial port. The driver assumes that each write contains a whole packet and that a request/reply type of protocol is running on the link that limits the number of outstanding transmit packets in the buffers. -
Page 22: Get_Port_Status()
RCHITECTURE Get_port_status() Get_port_status() Parameters handle The handle returned for the device by the open() call. buffer The 4-byte buffer in which to copy the status information. Return Values Returns 0 if no output is pending, 1 if output is pending, or -1 if an error occurred and errno is set to an error code. -
Page 23: Set_Event_Bit()
RCHITECTURE set_event_bit() set_event_bit() Allows the application to select one of the event bits that would otherwise be unused, and assigns it to a communication port. By default, the communication ports do not generate events. This function allows the communication ports to generate events when data is received. This mechanism is provided when almost all the bits in the event mask have already been allocated. -
Page 24: Iap_Control_Function()
RCHITECTURE iap_control_function() iap_control_function() This allows an application to control the keypad state. The possible functions defined in SDK header, SVC.H, are: • IAP_CONTROL_KEYPAD_SLEEP, turns off the keypad. • IAP_CONTROL_KEYPAD_WAKE, turns the keypad on. • IAP_CONTROL_DISABLE_KEYBEEP, turns off the keypad beeps. •... -
Page 25: Communication Protocols
Apple authentication coprocessor to validate e355 as valid Apple accessory before being able to communicate with iOS device. Frame ID reading selects the iAP1 protocol early on during the e355 power-up or restart. iAP1 is only supported on USB interface and not supported on Bluetooth interface. Maximum message size for read and write operations is 1024 bytes (1012 bytes payload), which is same as iAP2 maximum message size. - Page 26 RCHITECTURE iap_get_keypad_state() • Message-based protocol allows for CRC verification of each message. • Maximum message size is 2048 bytes (2040 bytes for payload). • Applications can write any size data, but must verify the number of bytes written and repeat write until total number of bytes written. Table 9 presents the PMR-MUX2 protocol commands.
- Page 27 RCHITECTURE iap_get_keypad_state() Table 10 presents the PMR-MUX2 status strings. Table 10 PMR-MUX2 Status Strings Message Status String Name Description <0xFF><0x5A>a<num><crc> ACK Indication This Message Status is a method for either end of the link to send and ACK status to the other end. This indicates that the previous message was received properly.
-
Page 28: Software Components
QTE50301-20151006 or WTE50301-20151006. For more information on the Verix Operating System, refer to Verix eVo Volume I: Operating System Programmers Manual - VPN DOC00301. Downloadable drivers Most OS drivers of e355 are downloadable. Following is the list of downloadable drivers: • Bluetooth •... -
Page 29: E355 Data Flow
Bluetooth only. This application provides the user interface for Bluetooth device configuration, pairing and discoverability, and Serial Port Profile (SPP) configuration and link management. e355 Data Flow Figure 7 shows the software components and software layers, and how the software components communicate with each other. - Page 30 RCHITECTURE iap_get_keypad_state() • Channel Application uses the frame ID value to select the appropriate interface (USB/lightning/Bluetooth) and message protocol (iAP1/iAP2/PMR- MUX2). • Channel Application communicates with BT_MGR application via pipe interface for Bluetooth profile connection management. • User Applications like Control Application, Barcode, and mADK/XPI can access virtual COM Ports (COM1A...COM1E) via iAP1/iAP2/PMR-MUX2 protocols.
-
Page 31: Usb Host
The e355 USB host interface is used in Mobile PINpad operation mode for frame ID values iPad mini, iPad mini 4, iPad 2, and iPod 6. The e355 USB host port connects to iOS device through an 8-pin frame connector. -
Page 32: Communication Interfaces
• iAP1 protocol is used over USB host interface. • iAP1 charging command is sent from e355 to iPad 2 to charge at 2.1 A when external AC power is connected to frame. • No barcode trigger buttons on iPad 2 frame. -
Page 33: Usb Device
The USB device interface is used in Mobile PINpad mode for frame ID values Android and Windows. The USB device port connects to Android/Windows device through an 8-pin frame connector. The side Micro-USB is not accessible for USB downloads when e355 is in Android/Windows frame configuration. Android Frame Key Points: •... - Page 34 OMMUNICATION NTERFACES • Communication link will be broken between e355 and Android device when external AC power is connected to frame, link will be re-established after external AC power disconnection. Side Micro-USB Connector Barcode Buttons Frame Connector Gang Charger Pins...
-
Page 35: Bluetooth
NOTE If the device is installed in a frame and then removed the e355 must be restarted to go into Bluetooth communications mode. The Bluetooth device provides low power consumption and operation and is capable of staying paired and connected while in deep sleep mode and waking up to receive data. -
Page 36: Personal Area Network (Pan) Profile
("auto") from NCP. This setting is available under Wi-Fi device driver setup. Low power Wi-Fi modes are supported in e355. This mode is configurable from NCP. Power Mode 2 is default and recommended. An application usually does not directly work with the Wi-Fi driver. -
Page 37: Chapter 4 Power Charging
This charging method is also specific to Mobile PINpad mode and charges one iPod 6 Frame) device at a time. For example, it will charge e355 first and then the smart device second. A Micro-USB charging cable needs to be attached to side Micro-USB port for sequential charging. -
Page 38: Power Sharing
Deep sleep timer (*OFF) expires, but blocked when smart device attached via Lightning/USB or smart device connected to e355 via Bluetooth. Hidden Reset There is a pin-hole button to hard reset e355 device, located near barcode button Button and battery status LED. -
Page 39: Power Modes
The terminal consumes considerably less power than when it is Active Run. The e355 goes into Active Idle state after all the applications are suspended for 20 seconds (default *POW configuration setting). Transition is automatic to next sleep state (snooze or deep sleep). -
Page 40: Power Environment Variables
12 mA, all peripherals are powered down and CPU clock runs at 32 kHz in this state. BT/Wi-Fi data instantly wakes e355 from deep sleep without loss of packets or data. e355 LCD display transitions to dark (appears Off) in deep sleep state. - Page 41 • Contactless device is special case, HW booster architecture is off of battery supply, resulting in current draw from battery even when e355 is powered by external power. •...
-
Page 42: Battery Status Led
The event is generated after the next wake-up and if the battery is discharged to a level that is a multiple of 10. • OS will not notify critical low battery status when e355 is in any sleep mode. Eventually power down will happen. •... -
Page 43: Special Features
The pass-through mode, also referred as data sync mode, allows access to smart Mode devices through the side Micro-USB port of e355. The purpose of this mode is to allow access to the smart device without having to separate e355 and frame from the smart device. -
Page 44: Enabling Pass-Through
Through Specify optional timer value in G18 command (for pass-through) or G61 command (for persistent pass-through). Disconnect the USB cable either from the side Micro-USB port of e355 or the USB port of PC/Mac. 24-Hour Restart As part of PCI PTS4 requirement, the terminal is forced to restart at least once for every 24 hours. -
Page 45: System Mode - Vtm
Entering and e355 OS requires a system password each time you enter VTM, this is to prevent Exiting VTM unauthorized user access to VTM menus. To access the system password screen, simultaneously press the ENTER and 7 keys. - Page 46 The startup screen shows a tamper message when an attempt to break into the system has been made, the message * * T A M P E R * * is displayed in place of the certificate. The e355 will remain in this state until the condition has been remedied.
-
Page 47: Keypad
Keypad To use the VTM menus, user may need to familiarize themselves with the keypad keys. The e355 features a cell phone-type keypad. This means multiple characters are assigned per key and repeated key press allows you access the desired character. -
Page 48: Edit Parameters
This submenu provides the editor for configuration files to add or change configuration parameters. User is prompted to select file group number and configuration file at the beginning. The system configuration parameters of e355 are stored in CONFIG.SYS file and in group 1. -
Page 49: Download
Micro-USB connector type on the other end (P/N:CBL000-049-01-A, shipped along with e355 unit). • TCP/IP download requires FTP client setup in PC and IP address of e355. Please refer to EOS document for proper setup procedure. Serial Download Software packages can be downloaded via COM1 port using serial cables. To download a software package using COM1 port: Press ENTER and 7. - Page 50 963000 Figure 18 e355 and PC Download via Serial (COM1) Port If you are having problems selecting COM1 port on e355, check if configuration variable *DEBUG=1 is set in Edit Parameters, either change *DEBUG value to 4 or delete it.
-
Page 51: Usb Download
Press 2 to select Partial dnld. Press 6 to navigate to next page. Press 2 to select USB Dev port. Verify USB cable connection to e355 and PC. Figure 19 USB Cable Connection to e355 and PC Send the command ddl -p# *UNZIP=NOVA-xx.xx.xx.zip NOVA- xx.xx.xx.zip from PC to start the download process. -
Page 52: Ddl Utility
DDL Utility Direct Download Utility (DDL) is used to transfer files from PC to e355. This Utility tool is available in Verix SDK. It is recommended to add this utility tool to PATH environment variable in PC for convenience of accessing it from any location in PC. -
Page 53: Memory
(which begin with * or #), delete split files (files of resumable download), delete current group files, and delete files in all groups. Terminal Info This submenu displays e355 unit information as follows: • Serial number •... -
Page 54: Icc (Smart Card) Diag
- VTM YSTEM Diags ICC (Smart Card) Checks versions of smart card library and driver, and runs diagnostics on smart Diag card reader. SMART CARD DIAG CUSTOMER SLOT: VoyLib 03.090000 VxOS11 PSCR Build 14 1> CUST SLOT DIAG POWER UP: PASSED SCRLIB 2.16 3/15 2>... -
Page 55: Barcode Diag
- VTM YSTEM Diags Barcode Diag Tests the barcode reader. Firmware version of barcode module is displayed after turning ON the scanner and LEVEL trigger mode is enabled. Press barcode buttons for scanning the barcode. Barcode Diagnostic Barcode Diagnostic Barcode Diagnostic Firmware: PAABL05-004-R00 Firmware: PAABL05-004-R00 1>... -
Page 56: Tamper Log
- VTM YSTEM Diags Tamper Log This option shows the history of tamper events in the unit with date and timestamps. Additional tamper information with hardware register status can be gathered in the log when *DEBUG or *LOG is enabled, and this VTM menu is selected. -
Page 57: Ipp (Debit) Ksn Info
- VTM YSTEM Diags IPP (Debit) KSN Info This option will display KSN information of three DUKPT keys (slot 0, 1, and 2). IPP KSN Info DUKPT 1: NONE DUKPT 2: NONE DUKPT 3: NONE Figure 27 IPP KSN Info Screen ADE KSN Info This option will display KSN information of ten ADE (Account Data Encryption) DUKPT keys (slots 0 to 9). -
Page 58: System Error Log
- VTM YSTEM System Error Log System Error The error log screens display internal diagnostic information about the most recent unrecoverable software error. The following information may need to be provided when reporting a unit problem. VERIX ERROR LOG Type 0 QTE50301 Task GID 46... -
Page 59: Clock
This submenu allows the user to turn ON or OFF the beeper sounds, reduce/ Settings increase the brightness of LCD backlight by 1% at a time, and reduce/increase the contrast of LCD by 1% at a time. Keypad backlight control is not available in e355. VTM CONSOLE MGR VTM CONSOLE MGR 1>... -
Page 60: Change Passwords
Without the password, user cannot enter into VTM. The unit, however, continues to process transactions in normal mode. Please contact your local Verifone representative on recovering lost or forgotten VTM password. Some downloads automatically reset file group access password or VTM entry password when configuration parameters *PW or *SMPW are set in download. -
Page 61: Ipp (Internal Pin Pad) Key Load
This menu will show the status of the RSA private key. The VeriShield Remote Keys (VRK) are signed with RSA public key of the unit. RKL Key Status Public Key name US California San Jose Verifone Production Private key hash 1B651574921C22F8... -
Page 62: Ade Key Load
- VTM YSTEM Key Management ADE Key Load ADE key loading menu has its own unique, numeric-only password that is 7-10 characters long. The default unique password is 1024444 and it is pre-expired, which means that password must be changed before loading ADE key(s). Selecting Reset password menu option will cause ADE keys to be erased and password will reset to default value. -
Page 63: Software Versions
- VTM YSTEM Software Versions Software This submenu displays version information of OS, EOS, Open protocol (OP), Versions drivers, VPI package, BT MGR, Channel App and others. VTM SOFTWARE VERSIONS VTM SOFTWARE VERSIONS VTM SOFTWARE VERSIONS OP Ver 1.2.4.1 CTLS Drvr 01.25.05 OS Ver QTE50301... - Page 64 - VTM YSTEM Software Versions 355/ 265 U SER AND RACTICES UIDE...
-
Page 65: Logging Options
• Connect serial cable from PC to either COM1 or debug port on dongle, and connect dongle to e355 with switch setting UART<->USB set to UART. • Debug port on the dongle requires power, so connect USB power to the dongle when you are using *DEBUG=4. -
Page 66: Log (File Based)
OGGING PTIONS OS Logging Support • Set *DEBUG=1 or 4 in Edit parameters menu and restart e355 unit. Debug Port COM1 Port Figure 38 Debug Port and COM1 Port *LOG (File Based) • Log data will be written to a circular buffer, which is stored in file in flash memory. -
Page 67: Configuration Variables
OGGING PTIONS EOS Log Library Configuration *DEBUGO Variables Presents detailed logging for various OS components such as task scheduler, power manager, device open/close, pipes and Ethernet. This variable logs can result in a high volume of data and must be disabled in production devices. •... -
Page 68: Application Logging Support
RAM memory logging is faster when compared to FLASH (file based) memory logging, and it avoids any read disturbance issues in memory. • RAM memory logs are erased after e355 restart/power cycle. • RAM logs are enabled either by using configuration variable *APPLOG=1 or by sending control command G31 with parameter 01. -
Page 69: Logprintf()
OGGING PTIONS logprintf() logprintf() This is used in writing log messages with severity. Prototype int logprintf (log_severity severity, const char *fmt..) Parameters Severity Any of define values from list: LOG_DEBUG, LOG_INFO, LOG_NOTICE, LOG_WARNING, LOG_ERROR, LOG_CRITICAL, LOG_ALERT, LOG_EMERGENCY Standard C printf format string Return Values Buffer overflow Not enabled... - Page 70 OGGING PTIONS logdump() 355/ 265 U SER AND RACTICES UIDE...
-
Page 71: Software Package
This chapter explains what is included in your software package. Basic Package Basic e355 software is packaged in VPI package format, the package name is called NOVA. VPI package has the advantage of grouping multiple software components into one package and downloading all of them in one step. Customer specific VPI packages are usually built on top of released NOVA packages. -
Page 72: Version Number
This version number is displayed in VTM software versions menu and in settings of Apple iDevice under General> About>Payware Mobile Reader when an Apple iDevice is attached to e355 and in the response of G25 control command. User service API "SVC_INFO_PACKAGE(char *str)" also returns package name and version number. -
Page 73: Configuration
Initiate Full download on E355 via VTM's COM1 or USB Dev port. • Modify download.bat: • p1 for COM1 or assigned communications port. • px for USB Dev where x is the assigned port for E355 device (check device manager). • Run download.bat. 355/ 265 U... - Page 74 OFTWARE ACKAGE Downloading 355/ 265 U SER AND RACTICES UIDE...
-
Page 75: Control And Barcode Applications
Control application is the first application that runs on Mobile PINpad architecture Application and it is set as the value of *GO configuration parameter. For supported commands and their format and response, see e355/e265 PAYware Mobile Reader Control Application Commands Programmers Guide, VPN - DOC087-078-EN. - Page 76 ONTROL AND ARCODE PPLICATIONS Pipe Interface 355/ 265 U SER AND RACTICES UIDE...
-
Page 77: Key Features Of E265 Vs. E355
HAPTER Key Features of e265 vs. e355 The e265 unit is a low-cost device with Bluetooth-only interface. The e355 unit is a flexible payment device, which can operate in standalone mode (POS) or Mobile PINpad mode (mPOS). Table 15 shows the key features of e265 versus e355. -
Page 78: E355/E265 User And Best Practice Guide
Verifone, Inc. 1-800-Verifone www.verifone.com e355/e265 User and Best Practices Guide Verifone Part Number DOC087-080-EN-A, Revision A...