> 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/adk-os-platform/readme/ux302-ux102-user-guidance.md).

# UX302 / UX102 - User Guidance

Hardware, software stack, features, administration, programming, and troubleshooting guidance for the UX302 unattended terminal and UX102/UX112 unattended encrypted pinpads (UEPP).

## Introduction

This document provides user guidance specific to the **UX302** unattended payment terminal and its companion unattended encrypted PIN pad (UEPP) **UX102**. It covers hardware setup, software stack, feature overview, administration, programming aspects, and troubleshooting.

The UX302 is a VOS3-based device exposing the standard Verifone ADK programming interface, fully compatible with other VOS3 products. The UX102 is an unattended EPP connected to the UX302 via USB, providing a secure remote keypad and color display for unattended payment scenarios.

{% hint style="warning" %}
**Compatibility**

The UX102 and UX112 are the successors to the UX100 and UX110. They share the same mounting and industrial design as their predecessors but are **not backwards compatible** with older UX300/UX301 devices or the VOS1/VOS2 software interface.
{% endhint %}

## 1. Hardware Overview and Physical Setup

### 1.1 UX302

The UX302 is the successor to the UX300/UX301, intended as a direct drop-in replacement from a mechanical mounting perspective. It targets unattended scenarios including vending, ticketing, parking, and petrol/fuel dispensing.

**Memory:**

| Component    | Specification |
| ------------ | ------------- |
| Flash memory | 2 GB          |
| RAM          | 512 MB        |

**Interfaces and connectivity:**

| Interface      | Details                                                                       |
| -------------- | ----------------------------------------------------------------------------- |
| Ethernet       | 10/100 Base-T, RJ45 with status LEDs                                          |
| USB Host       | USB Type-A — for UX102/UX112 connection                                       |
| USB OTG        | USB Type-C — host/client (programming, serial, IP-over-USB)                   |
| CTLS antenna   | RJ45/10 data + SMA-F RF connector (for UX402 external antenna)                |
| Power input    | 4-pin Molex, 9–43 V DC (MDB bus voltage compatible)                           |
| Service switch | Internal button for sysmode access; not accessible from outside the enclosure |

**Card readers:**

* Triple-track full-insert MSR
* Full-insert primary smart card reader / PSCR
* Contactless via external UX402 antenna

{% hint style="info" %}
The UX302 has **no built-in display or keypad**. User interaction is exclusively via connected accessories (UX102/UX112) or status LEDs.
{% endhint %}

**Status LEDs** (3 LEDs, same layout as UX300):

| State                     | LED behaviour          |
| ------------------------- | ---------------------- |
| Boot state                | Orange LED on          |
| Fast boot / error         | Red and orange LEDs on |
| Active (normal operation) | Green LED on           |
| Successful transition     | Green flash            |
| Failed transition         | Red flash              |

Applications may override LED state when the device is in the Active state.

### 1.2 UX102 / UX112

The UX102 (keypad with color display) and UX112 (keypad only) are the successors to the UX100 and UX110, sharing the same mounting and industrial design.

**UX102 display:**

| Parameter  | Specification |
| ---------- | ------------- |
| Size       | 2.4" diagonal |
| Resolution | 320 × 240     |

**Keypad** (both UX102 and UX112):

* 10 digit + 4 function + 2 direction keys — same mechanics as UX100/UX110

**Audio:** Buzzer on both models.

### 1.3 Physical Connection and Cabling

The UX102/UX112 connects to the UX302 via a **USB Type-C cable** (USB 2.0 speed). The USB-C connector on the UX102/UX112 uses a **locking screw** retention mechanism for reliable field deployment.

The USB connection carries:

* 5 V power delivery to the UX102/UX112
* Data: secure command channel, PIN forwarding, display rendering (UX102), firmware update traffic, and property/status reporting

The UX302 **USB Host port (Type-A)** is the host for this connection. A USB hub can be used on the UX302 USB Host port if multiple USB accessories need to be connected simultaneously.

## 2. Software Stack

### 2.1 UX302 – VOS3 ADK Releases

The UX302 runs VOS3, Verifone's next-generation embedded Linux platform. UX102/UX112 integration is available from **VOS3\_4.x** onwards.

### 2.2 UX102 – UEPP Firmware Releases

The UX102/UX112 run dedicated UEPP firmware.

| Version   | Release Date | Status                   | Notes                         |
| --------- | ------------ | ------------------------ | ----------------------------- |
| **1.2.1** | 30 Jan 2026  | **Active — recommended** | PCI PTS certified (#4-30585). |

See <https://docs.verifone.com/unattended-pin-pads-release-notes>

## 3. Features Overview

### 3.1 Hot-Plug

The UX302 automatically detects connection and disconnection of the UX102/UX112 via the USB Host port at runtime. Applications are notified through the ADK property service when a UEPP connects or disconnects. No system restart is required. Applications must handle both attached and detached states gracefully.

### 3.2 Auto-Personalization and Key Exchange

On first connection, an automated secure pairing and key exchange sequence is executed:

1. The UX302 authenticates the UX102/UX112 using the pre-loaded Verifone **Pairing warrantied key** (present on both devices from factory)
2. A secure USB channel is established
3. Working keys for PIN transfer encryption are derived and exchanged automatically

No operator intervention is required. This replaces the manual pairing procedure required with the legacy UX100/UX110 devices.

### 3.3 PIN Entry on UX102/UX112

The payment application on the UX302 initiates PIN entry using the **standard ADK SDI API** — identical to local PIN entry on other VOS3 devices. The platform handles UEPP routing transparently:

1. Application calls SDI PIN entry API
2. SDI server forwards the request to the UX102/UX112 via the secure USB channel
3. Cardholder enters PIN on the UX102/UX112 physical keypad
4. PIN block is encrypted on the UEPP secure processor and transferred to SDI
5. Application receives the encrypted PIN block via the standard SDI response

Supported PIN block formats: ISO 9564 Format 0, 1, 3, 4 (AES). Key schemes: TDEA/AES DUKPT and MK/SK. SRED and P2PE support as per VOS3 security specification.

Non-secure keypad input (menu navigation, non-PIN data entry) is forwarded from the UX102/UX112 to the UX302 system keypad service and available via the standard ADK input API.

### 3.4 Remote Display on UX102 (Controlled from UX302)

For the UX102 (display model), the UX302 application can render content on the UEPP's color display:

* Use the ADK GUI display/UI API with the UEPP device target selector
* HTML-based UI rendering (consistent with the VOS3 UI model) is supported
* Display content is transmitted over the secure USB channel

This enables the customer-facing cardholder UI (prompts, instructions, payment flow) to appear on the UEPP while the merchant/operator UI remains on the UX302 or a connected host system.

### 3.5 Tamper

**UX302:** Full VOS3 tamper handling applies — physical tamper detection triggers key deletion, security function blocking, and a tamper state boot. The device can only resume normal operation after reloading warrantied keys from a trusted KLD.

**UX102/UX112:** The UEPP secure processor independently monitors for physical tamper. When a connected UX102/UX112 is in tamper state, this is surfaced in the MAC control panel and ADK property service. Treat UX102 tamper events as PCI incidents requiring device return and replacement.

### 3.6 Power Management

The UX302 currently supports ADK Standby mode; Deep Sleep and Hibernate are still being finalized for this platform.

{% hint style="warning" %}
The UX102/UX112 power mode is managed independently of the UX302. The keypad/display state of the UX102/UX112 during a UX302 low-power mode, and whether a wake event on either device wakes the other, are not yet defined — do not rely on these behaviors. Re-establish the UEPP connection and display state after any UX302 power-mode transition (see 5.2 UEPP-Specific Programming Aspects).
{% endhint %}

## 4. Administration and Maintenance

### 4.1 Sysmode on UX302

Sysmode is accessible via the **service switch** on the back of the UX302 (not accessible from outside the mounting enclosure). Access to sysmode functions is password-protected.

| Panel                             | Function                                                                     |
| --------------------------------- | ---------------------------------------------------------------------------- |
| Security Control Panel (SCP)      | Key loading status, warrantied key versions, tamper log, initial key loading |
| SW Control Panel (SWCP)           | Local SW download/installation from USB drive or connected host PC           |
| Communication Control Panel (CCP) | Network interface configuration (Ethernet, USB)                              |
| Logging Control Panel (LCP)       | Log level configuration and log export for troubleshooting                   |
| Power Control Panel               | Sleep, reboot, shutdown                                                      |

### 4.2 UEPP Status and Properties

When a UX102/UX112 is connected, its properties are available via the VOS3 ADK system property service and the MAC UEPP status panel:

| Property         | Description              |
| ---------------- | ------------------------ |
| UEPP model       | UX102 or UX112           |
| Serial number    | Device serial number     |
| Firmware version | e.g. 1.2.1               |
| PCI version      | e.g. C01.02.02           |
| Tamper state     | OK / Tamper              |
| Connection state | Connected / Disconnected |
| HW ID            | Hardware identifier      |

These properties are also reported to VHQ when the VHQ agent is active on the UX302.

### 4.3 UEPP Firmware Updates

UEPP firmware updates are managed entirely from the UX302 — no direct PC connection to the UX102/UX112 is required in the field:

1. Place the UEPP firmware DL file in the UX302 download area (via USB drive, netloader from host PC, or VHQ remote distribution)
2. The UX302 SW installer detects the UEPP firmware bundle and delivers it to the connected UX102/UX112 over the secure USB channel
3. The UEPP secure processor authenticates the update before installation
4. Progress and result are reported via standard VOS3 installer status

### 4.4 Remote Management via VHQ

With the VHQ agent installed on the UX302, remote management capabilities include:

* Remote SW distribution to UX302, including UEPP firmware DL packages
* Device inventory: UX102 model, serial number, firmware version, PCI version, connection state, tamper status
* Remote log collection

{% hint style="warning" %}
VHQ UEPP status reporting and update support is being finalized. Check the current ADK release notes for VHQ/UEPP integration status.
{% endhint %}

### 4.5 24-Hour Automatic Reboot

The CDD manages the 24-hour automatic reboot on the UX302. After reboot, the UX102/UX112 reconnects automatically via hot-plug detection. No special configuration is required.

### 4.6 Statistics Collection

The UX302 supports collection of operational statistics including: SW/FW/HW version numbers, card insert counts, error counts, wake-up counts, operating time, power-on counter, temperature, SW exceptions, HW alarms, battery state, and communications usage. These statistics are available to applications and to VHQ.

## 5. Programming

### 5.1 General ADK Programming

The UX302 exposes the standard VOS3 ADK programming interface. Applications developed for other VOS3 devices are broadly compatible. Refer to the general ADK programming guide and the platform architecture documentation for details.

### 5.2 UEPP-Specific Programming Aspects

#### UEPP Detection and Property Queries

Register for UEPP connect/disconnect property change notifications via the ADK system property service. Query UEPP properties (model, FW version, tamper state, display dimensions) at connect time. Do not assume a UEPP is always present — handle both attached and detached states.

#### PIN Entry

Use the standard ADK SDI PIN entry API. The SDI server transparently routes PIN entry to the connected UEPP. No direct UEPP addressing is needed from the application.

#### Remote Display (UX102)

Use the ADK display/UI API with the UEPP device target selector to render on the UX102 display (320×240, 30 FPS minimum). HTML-based rendering is supported. **Re-send display content after every UEPP reconnect event** — display state does not persist across disconnections.

#### Non-PIN Keypad Input

Non-secure UEPP keypad input is forwarded to the UX302 system keypad service and available via the standard ADK input API — no special handling is needed for basic keypad forwarding.

#### UEPP Firmware Update

Use the ADK installer API to initiate or monitor UEPP firmware updates. The installer handles delivery to the connected device. Check the installer documentation for the UEPP FW package type handling.

#### Power Management

Use the ADK-PM library for power mode control. UX302 power modes (Standby, Deep Sleep, Hibernate) are controlled independently of the UEPP. The application is responsible for re-initialising the UEPP display and connection state after the UX302 wakes from a power mode where the USB Host was suspended.

## 6. Troubleshooting

### 6.1 Checking for Proper Connection

**Physical checks:**

* Verify the USB-C cable (`CBL179-103-01-A` or equivalent) is firmly seated and the locking screw is engaged at the UX102/UX112 end
* Confirm the cable is connected to the **USB Host (Type-A) port** on the UX302, not the USB OTG (Type-C) port
* Confirm the UX102/UX112 LEDs indicate powered state

**Software checks:**

* In the MAC UEPP status panel: a connected UX102 should show model, serial number, and firmware version
* Via ADK property service: query UEPP connection state — should return `connected` with model and FW version populated
* Check the VOS3 system log for USB enumeration events and UEPP channel setup status

### 6.2 Getting Device Information

Query UEPP properties via the ADK system property service or the MAC control panel. Expected values for a healthy UX102 running current firmware:

| Property         | Expected value |
| ---------------- | -------------- |
| Model            | UX102          |
| FW version       | 1.2.1          |
| PCI version      | C01.02.02      |
| Tamper state     | OK             |
| Connection state | Connected      |

### 6.3 Diagnosis Application

The VOS3 diagnosis application (accessible from the MAC desktop) provides:

* UEPP connection test: verifies USB enumeration and secure channel setup
* UEPP firmware version and PCI version display
* UEPP tamper state check
* LED status verification on UX302
* PIN entry test via UX102/UX112
* Display test via UX102

See the platform diagnosis guide for general VOS3 diagnosis procedures.

### 6.4 Common Issues

| Symptom                                     | Likely cause                                                  | Resolution                                                                              |
| ------------------------------------------- | ------------------------------------------------------------- | --------------------------------------------------------------------------------------- |
| UX102 not detected                          | Wrong USB port, cable fault, or locking screw not engaged     | Use the USB Host (Type-A) port; check cable; engage locking screw                       |
| Detected but secure channel not established | Pairing key mismatch or UEPP FW incompatibility               | Verify UEPP FW is 1.2.1; check warrantied key status in SCP                             |
| PIN not forwarded to UX102                  | UEPP connection dropped                                       | Verify connection state in property service; restart application                        |
| UX102 display blank after reconnect         | Display not re-initialised                                    | Application must re-send display content on UEPP reconnect event                        |
| UEPP FW update fails                        | DL package signing mismatch or wrong model                    | Check VOS3 installer log; verify DL file targets UX102 model                            |
| Display non-functional after FW update      | UEPP FW 1.0.0 used with VOS3 ≥ 4.0.0-RC1                      | Update UEPP FW to 1.2.1                                                                 |
| UX302 does not wake via UX102 key press     | Wake linkage between UX102/UX112 and UX302 is not yet defined | Use timer-based wake-up as a workaround; check the current ADK release notes for status |
| UEPP tamper state shown in SCP              | Physical tamper event detected on UX102                       | Device requires return; reload warrantied keys on UX302                                 |
| MAC desktop shows no UEPP panel             | VOS3 release pre-dates UEPP support                           | Update to VOS3\_4.x or later                                                            |


---

# 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/adk-os-platform/readme/ux302-ux102-user-guidance.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.