> For the complete documentation index, see [llms.txt](https://docs.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verifone.com/hardware-products/hardware/engage-devices/exxx-series/e235/e235-installation-guide/device-overview.md). # Device Overview This chapter provides an overview of the e235 device: The e235 device is a standalone, mobile wireless handheld payment device, making it easy to process contact and contactless transactions anywhere. It provides mobile payment capabilities via 4G connectivity. It is also a powerful 4G/Bluetooth/Wi-Fi (Wireless Fidelity) dual-band solution featuring advanced communication for a few dropped transactions so merchants can accept payments securely, extending their point-of-sale opportunities. The e235 with physical keypad design accepts all payment methods Magnetic Stripe Reader (MSR), Primary Smart Card Reader (PSCR), Contactless (CTLS), and Wallets. The easy-to-read color screen is fully supported by Verifone's developer toolkit which enables to transform ideas into applications.

Figure 1: e235 Unit

## Features and Benefits The e235 provides the right combination of features and functions including a triple-track magnetic-stripe card reader, smart card reader, integrated (Personal Identification Number) PIN (pad and contactless/NFC (Near Field Communication) support. ### Key Features * 300 MHz A9 processor delivers power and usability in a convenient "hand-over" design. * Offers unsurpassed performance on Europay MasterCard and VISA (EMV) smart card transactions. * Multi-application operating environment. * Security architecture exceeds specifications for PCI (Payment Card Industry)-PTS (PIN Transaction Security) and sophisticated file authentication. * Advanced memory architecture to meet tomorrow's needs. * Multiple connectivity and contactless options. * 32-bit processing and multitasking capabilities. * Drop-resistant design minimizes breakage. ### Triple Radio Performance The dynamic combination of Bluetooth chip, Wi-Fi and powerful 4G radio delivers fast, wireless payment convenience, fewer dropped transactions, and flexible point-of-sale options. ### Modern Application Environment * Reliable operating system and powerful tools to create a richer customer experience. * Common Engage software architecture enables faster and more cost-effective application development. ### Accepts All Forms of Payment On-the-Go Accommodates all payment types - Magstripe, EMV, Contactless/NFC and mobile wallets along with a 2.3-inch color screen. ### Ease of Use * The lightweight, compact, stylish, and ergonomic balance allows convenient device hand-off to the consumer for PIN entry or other inputs. * Horizontal magnetic stripe card reader for optimal card swiping and reading. ### Performance and Durability * Powerful 300 MHz A9 processing completes transactions quickly. * High-capacity lithium-ion battery pack. * The (Universal Serial Bus) USB-C port allows convenient product charging as well as connection to Android and Windows devices. * Rounded corners to minimize breakage and drop-resistant to 3 feet on concrete surfaces. * 512MB Flash, 512MB (Double Data Rate) DDR (Random Access Memory) RAM. ### Security * PCI PTS 6.x approved for debit and other PIN-based transactions. * Tamper-resistant construction, (Secure Socket Layer) SSL protocols * Direct key injection using industry standard (Hardware Security Module) HSMs. * VeriShield Retain * VeriShield Remote Key * Verifone Secure Data * VeriShield Total Protect * MasterCard TQM (Terminal Quality Management) * IPP8 (Internal PIN Pad) functionality plus multiple DUKPT (Derived Unique Key Per Transaction) engines * EMV L1 and L2 * ISO(International Organization for Standardization)7816-3, ISO7816-4 and EMV 4.3 standards ### Contactless Capability Advanced contactless architecture that future-proofs investment with a single contactless interface (SingleCl), SoftSAMs, and side-by-side application architecture. On-screen tap zone for optimized user experience. ### Connectivity **USB host/device port** * UARTUniversal Asynchronous Receiver/Transmitter)0 software debug (TXD0, RXD0) * USB 2.0 high speed * 5V/200mA for external USB peripherals * USB host or device is configured by SW * Type C USB connector on the side * Communication port for the smart device on charge stand (Android and Windows). **Bluetooth (wireless communication)** * Bluetooth 4.1 + EDR (Enhanced Data Rate) compliant * Eddystone + iBeacon * RF (Radio Frequency) transmitter output power Class 1 * RF receiver GFSK typical -90 dBm /4 PSK (Pre-Shared Key) typical -90 dBm, 8D PSK typical -83 dBm **Wi-Fi (wireless communication)** * BT (Bluetooth), Wi-Fi * Wi-Fi dual band supports: * 802.11 a/b/g/n/ac connectivity * 2.4GHz and 5GHz * Auto-band selection **4G (wireless communication)** * GPRS/GSM (General Packet Radio Services/Global System for Mobile Communications) Class 10 * UMTS/HSPA DL 7.2Mbps, UL 5.7Mbps --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.verifone.com/hardware-products/hardware/engage-devices/exxx-series/e235/e235-installation-guide/device-overview.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.