> 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/android-devices/t650-series/t650m/t650m-installation-guide/device-overview.md). # Device Overview The Verifone T650m device is a powerful all-in-one mPOS solution, which allows electronic payment transactions to be processed. This payment processing solution with a fully integrated POS can scan barcodes, QR codes, and products with the help of an integrated camera. It has the ability to run Android applications, like loyalty and inventory. It also enables clients to remotely monitor and update their devices using Verifone's estate management solution. The T650m device supports Bluetooth and Wi-Fi and meets PCI-PTS 6.X SRED requirements for maximum security. The Verifone T650m device supports all payment methods - magnetic stripe, EMV, and NFC/Contactless Reader, including Apple Pay, Google Pay, and Samsung Pay mobile wallets. The easy-to-read color touch screen supports all payment-related user interactions and keypad for secure PIN entry. ## Features and Benefits

Figure 1 – T650m Device

Following are the features and benefits. ### Exceptional 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. * Magnetic stripe card reader for optimal card reading. * Audio jack to facilitate accessibility for the visually impaired. ### Performance and Durability * Fast transactions due to powerful 1.1 GHz ARM Cortex A7 quad-core processor. * Rounded corners and drop resistant to less than 1m on the concrete floor to minimize breakage. * 2GB/16GB, Optional 1GB/8GB, SD card slot that supports up to 32GB SD memory expansion. ### Security * Incorporates tamper-sensing circuitry to detect unauthorized intrusion and supports a broad spectrum of software-based security features. * PCI-PTS 6.X approved for debit and other PIN-based transactions. * EMV Level 1 Type Approval. * Supports reliable security features including TLS, VeriShield file, authentication and VeriShield Protect to help prevent fraud and other intrusions. ### Contactless Capability * Advanced contactless architecture that future-proofs investment with a single contactless interface (SingleCl), SoftSAMs, and side-by-side application architecture. * Dedicated tap zone for optimized user experience. * Accepts EMV, NFC, QR Code 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. * Supports 4G/3G/2G LTE * Dual-band Wi-Fi. ### Connectivity Wired interfaces: * USB port type C --- # 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/android-devices/t650-series/t650m/t650m-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.