> 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-full-feature-base/victa-full-feature-base-installation-guide/device-overview.md).

# Device Overview

This chapter provides an overview of the Victa Full Feature Base device.

The Full Feature Base is a highly capable solution built for modern mobile and portable devices such as VP100, VM100 etc. The Victa FF Base supports Ethernet connection for seamless integration with Electronic Cash Registers (ECRs).

There are three separate USB interfaces; USB-A to connect accessories to the base such as scanner. Only peripherals appearing as single virtual serial ports are supported on this port.

USB-C for powering the base via the power supply provided with the terminal, and the secondary USB-B interface that allows serial data connection.

In Bluetooth connection, a dedicated base control channel ensures the operation and remains independent of the handset.

When the terminal is docked, it automatically communicates over USB by default; when undocked, it transitions seamlessly to a Bluetooth PAN connection. Bluetooth support enables Grab-and-Go workflows, allowing the terminal to be removed from the base and remain connected via Bluetooth.

## Features

Following are the supported features:

* **USB-Serial Gadget Support**: Supports USB-Serial gadget mode exclusively.
* **Ethernet Sharing via Pogo Pins**: When the Terminal is docked, the ETH0 interface can activate and shares Ethernet connectivity through pogo pins.
* **Undocked State Handling**: Ethernet interface remains inactive when the Terminal is not docked.
* **Flexible Docking Connectivity**: Handset docking is supported via Bluetooth pairing when undocked, and via pogo-pin connection when docked.

### Compatible Terminals

* VP100
* VM100

### Multiple Bases Support

Up to seven Terminals can be paired to a single Base. A Terminal handset can be paired with up to three Bases.

{% hint style="info" %}
**Note**: Even if paired against multiple Bases, a Terminal can be connected to only a single Base at a time.
{% endhint %}

* **Charging and Communication Dock**
  * Charges the terminal while connected, reducing downtime.
  * Allows simultaneous charging and data communication.
* **Peripheral Support**
  * Ports for connecting peripherals such as ECR, barcode scanners, or printers.
  * Enhances functionality of the payment terminal.
* **Secure Cradle Design**
  * Prevents accidental disconnection or tampering.
* **Compact and Durable**
  * Designed for counter-top use with minimal space requirements.
  * Built for long-term use in busy retail environment.

## Connectivity Options

The Victa Full Feature Base provides multiple ports to connect and power the payment terminal while integrating smoothly into your point-of-sale.

* USB-C Port
* Ethernet Port (LAN)
* USB-A Host Port
* USB-B Device Port

<figure><img src="/files/APxpp10PtwnArtnOl2ex" alt="" width="563"><figcaption></figcaption></figure>


---

# 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-full-feature-base/victa-full-feature-base-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.