> 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/v640-series/v640m/v640m-installation-guide/device-overview.md).

# Device Overview

This chapter provides a brief description of the 640m devices.

The 640m device is a best-in-class, single-screen commerce solution. It is a secure wireless handheld mobile payment device that allows merchants to process credit/debit card transactions anywhere. In combination with Verifone Connect digital services, it offers checkout, payment, and 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 640m device supports Bluetooth BLE, Wi-Fi, and meets PCI (Payment Card Industry)6.1 SRED (Secure Reading and Exchange of Data) and AES (Advanced Encryption Standard Algorithm) DUKPT requirements for maximum security.

The 640m's small and sleek design makes it portable while supporting payment methods - EMV (Europay, MasterCard and Visa Standard) and (Near Field Communication)/CTLS (Contactless), including Apple Pay, Google Pay, and Samsung Pay mobile wallets. The easy to read color touch screen supports all payment related user interactions, including secure PIN (Personal Identification Number) entry.

<figure><img src="/files/eSQ29i2Z3GCpH7R8Zfql" alt="" width="241"><figcaption><p>Figure 1 – 640m Device</p></figcaption></figure>

## Features and Benefits

The 640m device provides smart card (SC) and contactless (CTLS) payment processing with a 4.3-inch (480 x 800) IPS (Inches Per Second) LCD (Liquid Crystal Display) touchscreen.

### BT and Wi-Fi Performance

The dynamic combination of Bluetooth and Wi-Fi provides convenience to wireless payment transactions, and flexible point-of-sale options.

### Application Environment

* There are 2 memory options available: 1GB RAM + 8GB Flash or 2GB RAM + 16GB Flash. The type fitted will depend on the model variant.
* The primary smart card reader and the MSAMs safeguard sensitive financial data and support multiple smart card schemes.
* 640m units are certified for ISO 7816-1 and ISO 7816-3 standards for smart card solutions, and ISO 14443 type A & B and ISO 18092 standards for CTLS operations.
* The VeriShield security architecture supports PCI PTS POI and provides file authentication to prevent execution of unauthorized software on 640m devices.

### Payment On-the-Go

* Accommodates payment types - EMV, Contactless/NFC, and mobile wallets along with a 4.3-inch color touch screen with digital PIN pad and signature capture.

### Performance and Durability

* Secure and powerful processing encrypts and completes transactions quickly.
* High-capacity, lithium-ion rechargeable battery for only (3000 mAh) that easily supports a business day on a single charge most of the times.
* The USB (Universal Serial Bus)-C port allows both product charging as well as connection to accessories, and Android, iOS, and Windows devices.
* IP53 product rating for water & dust ingress.
* The unit is drop tested from a height of 1.2 m onto a solid surface.

### Security

* PCI PTS 6.1
* TLS/SSL protocols
* Direct key injection using industry standard HSMs
* VeriShield Retain
* VeriShield Remote Key
* Verifone Secure Data
* VeriShield Total Protect
* MasterCard TQM
* IPP8 functionality plus multiple AES DUKPT engines
* EMV L1 and L2
* ISO7816-3, ISO7816-10, and EMV 4.3 standards

### Connectivity

**USB host/ device port**

* 1 USB Type-C Receptacle (can be used for charging)
* Support Android UART software debug (TXD, RXD)
* Support Secure Processor UART software debug (TXD0, RXD0)
* Android USB 2.0 High Speed Host/Client Support
* Secure Processor USB 2.0 High Speed Host/Client
* Support 5 V/3000mAh for external USB peripherals
* USB host or device is configured by Software
* The 640m USB-C port is on the right-hand side
* Smart device communication is through USB-C

**Cellular (wireless communication)**

* 4G LTE

**Bluetooth (wireless communication)**

* Bluetooth 4.2 (BLE)
* RF transmitter output power Class 1
* RF receiver GFSK typical -90dBm, ð/4 PSK typical -90dBm, 8-DPSK typical -83dBm

**Wi-Fi (wireless communication)**

* Wi-Fi 2.4GHz / 5GHz dual band, 802.11 a/b/g/n (5GHz support is an option)

### Main Battery

* Nominal capacity/voltage: 3000mAh/5 V

### Ease of Use

* The lightweight, compact, stylish, and ergonomic balance provides a convenient payment experience for the user.
* Easy to hold and has a compact size which makes it portable.
* Capacitive touch-screen UI access for merchant and customer.
* The contactless (CTLS) functionality offers a convenient payment option for consumers.
* EMV card reader ensures a secure payment option.
* Large 4.3-inch LCD touchscreen.


---

# 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/v640-series/v640m/v640m-installation-guide/device-overview.md?ask=<question>&goal=<endgoal>
```

`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.
