> For the complete documentation index, see [llms.txt](https://sandbox-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://sandbox-docs.verifone.com/home/copy-of-payware-connect-onboarding/victa-mobile-installation-guide/1.-device-overview.md). # 1. Device Overview The **Victa Mobile** is a next-generation, all-in-one terminal built for exceptional performance. It runs the **Verifone Android Operating System (VAOS)** and **Verifone Operating System 3 (VOS3)**, available in two versions: countertop and PINpad. Key highlights: * Wireless IP connectivity and high-capacity lithium-ion battery * Camera-based barcode scanning and e-receipt options * Operates in extreme conditions — down to **-5°C**, rain-resistant * Supports ECR integration, Wi-Fi, NFC, and Verifone cloud-based solutions * Accessibility features via **Verifone Navigator** for low-vision and blind customers * Remote monitoring and updates via Verifone's estate management platform Accepted payment methods: **Magnetic stripe, EMV chip, NFC/contactless, Apple Pay, Google Pay, Samsung Pay** *** ### Features and Benefits The Victa Mobile is Verifone's card reader with barcode scanning and image capture — an economical all-in-one solution for expanding payment acceptance. #### Ease of Use * **6.7" High-Definition Multi-Touch Display** with capacitive touch technology — readable in any lighting * Icon-based app navigation and electronic signature capture * Integrated magnetic stripe card reader for optimal card reading * **3.5 mm audio jack** for visually impaired accessibility * Accepts mobile wallets and alternative payment methods * Battery-powered for full mobility and portability * Buzzer for audio confirmation of card transactions #### Compliance * **PCI PTS v6.x** including SRED * EMVCo Contact Level 1 and Level 2 * EMVCo Contactless L1 * Global contactless standards: PayPass, PayWave, MIFARE, FeliCa #### Performance and Robustness * **64-bit quad-core ARM Cortex-A53** processor at up to **2 GHz** * Drop-resistant design — withstands drops under **1 m** onto concrete * **4 GB RAM / 32 GB eMMC** storage #### Security Features * Tamper-sensing circuitry for unauthorized intrusion detection * **TLS protocol** support — prevents fraud and intrusions * Master/Session or **DUKPT** key-management methods * **PCI PTS v6.x** compliant for PED devices * ISO and ANSI standards for PIN encryption, key management, and MAC * Verifone **Secure Kit** key-loading software * **Kensington Lock (K-lock)** support for physical security *** ### Contactless Capability * Advanced contactless architecture: **SingleCl**, SoftSAMs, side-by-side application architecture * Dedicated tap zone for optimized contactless performance * Accepts: **EMV, NFC, MIFARE, FeliCa**, and secure PIN-based transactions *** ### Communication Technology * **Bluetooth 5.0** — plug-and-play, supports Eddystone and iBeacon profiles * **Dual-band Wi-Fi** at 2.4 GHz and 5 GHz *** ### Connectivity Options * **Wireless:** 4G LTE, Wi-Fi, Bluetooth * **Wired:** USB-C to USB-A --- # 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://sandbox-docs.verifone.com/home/copy-of-payware-connect-onboarding/victa-mobile-installation-guide/1.-device-overview.md?ask=&goal= ``` `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.