> 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/m4xx-series/m400/m400-installation-guide/device-overview.md). # Device Overview A media-capable consumer-facing device that connects to a POS system which allows electronic payment transactions to be processed in multi-lane scenarios. It provides better media capabilities, more reliable hardware, and more efficient processing software. The terminal features a color 5" IPS LCD (Liquid Crystal Display) capacitive touch-screen display, a fast processor, abundant memory, PCI 4.x security, and an integrated contactless module. M400 Wi-Fi/BT supports 802.11 a/b/g/n Wireless Fidelity (Wi-Fi) and Bluetooth (BT), while the M400 BT variant supports Bluetooth (BT) including BLE with iBeacon and Eddystone profiles.

Figure 1: M400 Terminal

## Features and Benefits The terminal focuses on optimizing cost structure and providing better form factor by combining the right features and functions. ### Ease of Use * Large 5" LCD for unlimited application possibilities and easy readability under various lighting conditions. * Touchscreen for icon-based applications or electronic signature capture support. * Intuitive telco-style keypad with colored control keys interchangeably detects key presses from tactile keypad and touchscreen. * Bi-directional magnetic stripe card reader with an extended blade for optimal card reading. * Audio jack to facilitate accessibility for the visually impaired. ### Performance and Durability * Fast transactions due to powerful 1 GHz ARM (Advanced RISC Machine) Cortex A9 processor. * Rounded corners and drop resistant to three feet on the concrete floor to minimize breakage. * 512 MB flash memory and 512 MB SDRAM with removable uSD. ### Security * Incorporates tamper-detection circuitry to resist unauthorized intrusion and supports a broad spectrum of software-based security features. * PCI (Payment Card Industry) 4.x approved for debit and other PIN (Personal Identification Number) based transactions. * EMV (Europay, MasterCard and Visa) Level 1 Type Approval. * Supports reliable security available including SSL, VeriShield file authentication, and VeriShield Protect to help prevent fraud and other intrusions. * With Kensington lock feature resident in the terminal as part of the case. ### 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. * Accepts EMV, NFC, and mag-stripe contactless payments as well as PIN-based transactions. ### Communication Technology * Bluetooth: Simple, plug-and-play installation for locations that need short range wireless capability. Eddystone and iBeacon profiles are also supported. * Wi-Fi: Ideal for retailers that need multiple wireless devices and have an existing IP infrastructure (M400 Wi-Fi-BT only). --- # 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/m4xx-series/m400/m400-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.