> 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.md). # Victa

Product	Documentation	Cover image
Victa Mobile Handheld Android device for mobile checkout.	Victa Mobile	victa mobile.png
Victa Mobile Ruggedized Rugged mobile commerce for demanding environments.	Victa Mobile Ruggedized	Victa-Mobile-Ruggedized.png
Victa Lane Customer-facing payment and engagement device.	Victa Lane	Victa-Lane-8.png
Victa Portable Portable device with printing and scanning.	Victa Portable	victa portable.png
Victa Portable Duo Dual-screen portable device for clear checkout.	Victa Portable Duo	Hero_Victa Portable Duo_r004.724.png
Victa Reader Mobile card reader for Android and iOS.	Victa Reader	Victa Reader.png
Victa Full Feature Base Built for mobile and portable devices.	Victa Full Feature Base	Victa Full Feature Base.png
Victa Register Integrated POS and payment solution.	Victa Register	Victa Register.png
Victa Mini PINpad Compact PINpad for secure contactless payments.	Victa Mini PINpad	Victa-Mini-PIN-pad.png
Victa Mini Compact device for space-constrained checkout.	Victa Mini	victa mini.png
Victa SoftPOS Mobile Handheld device that runs SoftPOS apps.	Victa SoftPOS Mobile	Victa-SoftPOS-Mobile.png
Victa SoftPOS Portable Portable device that runs SoftPOS apps with receipt printing.	Victa SoftPOS Portable	Victa-SoftPOS-Portable.png

\*\*\* --- # 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/victa.md?ask=&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.