> 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/pxxx-series/p400/p400-p400-plus-installation-guide/specifications.md).

# Specifications

This chapter provides details on the power requirements, dimensions, and additional specifications of the P400 device.

## Unit Power Requirement

| Mode                               | Specification |
| ---------------------------------- | ------------- |
| Full capabilities                  | 7-12V DC, 1A  |
| Reduced capabilities (USB powered) | 5V DC, 500 mA |

## Temperature

| Type                  | Range                         |
| --------------------- | ----------------------------- |
| Operating temperature | 0°C to 50°C (32°F to 122°F)   |
| Storage temperature   | -20°C to 60°C (-4°F to 140°F) |

## Humidity

* Relative humidity: 5% to 90% RH non-condensing

## External Dimensions

| Dimension | Value               |
| --------- | ------------------- |
| Length    | 166.70 mm (6.56 in) |
| Width     | 79.60 mm (3.13 in)  |
| Depth     | 42.30 mm (1.67 in)  |

## Weight

* Unit weight: 274 g (9.66 oz)

## Processor

* ARM Cortex A9 32-bit processor

## Display

* 3.5" portrait mode transmissive TFT 320 (RGB) x 480 (HVGA)

## Magnetic Card Reader

* Triple track (tracks 1, 2, 3), high coercivity, bi-directional

## Primary Smart Card

* ISO 7816-3, 1.8V, 3V, 5V
* Synchronous and Asynchronous cards
* EMV approved

## SAM Card Reader

* Two Security Access Modules (SAMs)

## Security

* 3DES (Triple Data Encryption Algorithm) encryption, Master/Session and DUKPT key management
* VeriShield file authentication
* PCI PED 4.0 approved


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.verifone.com/hardware-products/hardware/engage-devices/pxxx-series/p400/p400-p400-plus-installation-guide/specifications.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.