> 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/victa/victa-lane/victa-lane-installation-guide/specifications.md).

# Specifications

This chapter discusses power requirements, dimensions, and other specifications of the Victa Lane device.

| Specification                     | Details                                                                                                               |
| --------------------------------- | --------------------------------------------------------------------------------------------------------------------- |
| **Unit Power Requirement**        | <p>• Input: 100-240V AC<br>• Output: 12V DC/1.5 A</p>                                                                 |
| **Processor**                     | Qualcomm SM6225 Octa-Core (4× Cortex-A73 @ 2.4 GHz, 4× Cortex-A53 @ 1.9 GHz)                                          |
| **Temperature**                   | <p>• Operating Temperature: -5°C to 50°C (23°F to 122°F)<br>• Storage Temperature: -20°C to 60°C (-4°F to 140°F)</p>  |
| **Humidity**                      | 5% – 90% relative humidity (non-condensing)                                                                           |
| **Display**                       | 8-inch (1280X800) HD (High Definition) IPS (In-plane Switching) LCD, Capacitive Touch Screen                          |
| **External Dimensions**           | <p>• Length: 207.95 mm (8.18 in.)<br>• Width: 140.32 mm (5.52 in.)<br>• Depth: 13.7 mm (0.53 in.)</p>                 |
| **Magnetic Card Reader**          | Triple Track (tracks 1, 2, 3), High Coercivity, Bi-Directional                                                        |
| **Primary Smart Card**            | <p>• ISO 7810, 7811 and 7813<br>• Synchronous and Asynchronous Cards</p>                                              |
| **SIM/SAM/eSIM Card Reader**      | One Subscriber Identity Module (SIM), one Security Access Module (SAM), and one eSIM                                  |
| **SD Card Reader**                | One SD Card Slot                                                                                                      |
| **Integrated Contactless Reader** | ISO 14443/4 Types A and B, ISO 18092, EMV                                                                             |
| **Memory**                        | <p>• Flash: 32 GB<br>• RAM: 4 GB</p>                                                                                  |
| **Audio Interface**               | <p>• Supports 3.5 mm Headphone Jack<br>• Built-in Speaker<br>• Built-in Buzzer<br>• Built-in Microphone</p>           |
| **Security**                      | <p>• Complies to PCI-PTS 7.x requirements<br>• Supports regional security requirements<br>• Remote Shim Detection</p> |


---

# 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/victa/victa-lane/victa-lane-installation-guide/specifications.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.