> 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/ux1-3-4xx-series/ux4xx/ux402-installation-guide/device-overview.md). # Device Overview This chapter provides an overview of UX302 and UX402 devices. Verifone's UX302 is a powerful payment processing device for unattended scenarios. It allows both contact and, with the UX402, contactless payment transactions to be processed. The payment device has the ability to either operate as an independent payment device or connect as a payment device for another system like a vending kiosk or a parking device. It also enables clients to remotely monitor and update their devices using Verifone's estate management solution. ## Features and Benefits The UX302 is Verifone's card reader and main control unit. It creates an economical solution for merchants who are looking to expand their payment acceptance options. ### Ease of Use The following features simplify transactions in various environments: * Designed for indoor and outdoor use. * Various connectivity options are integrated into the device. * The LEDs (Light Emitting Diode) on the UX302 signify device power and status, while the LEDs on the UX402 indicate the progress of CTLS (Contactless) card reads. * Buzzer for audio confirmation of card transactions. ### Compliance * PCI (Payment Card Industry) PTS (PIN Transaction Security) 6.x Approved * EMV (Europay MasterCard and VISA), Level 1 and Level 2 * Compliance with all major card schemes --- # 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/engage-devices/ux1-3-4xx-series/ux4xx/ux402-installation-guide/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.