> 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/support-us/general-pinpad-support/general-pinpad-help/blank-screen.md).

# Blank Screen

How to troubleshoot a Verifone device with a blank/black screen.

{% hint style="info" %}
**Use this when** the device screen is off or blank and doesn't respond to transaction requests from the POS.
{% endhint %}

## Symptoms

* The device fails to respond to transaction requests from the POS station.
* The terminal screen is off or blank.

## Resolve the issue

* **Tap the screen** to initiate the device if it is in screen-saver mode.
* **Check all cable connections**, including the power cable, and make sure they are securely connected. 
* **Inspect the power cable** for visible damage.
* **Allow the device to restart** and check whether the display returns.

## Still not working? Contact the Helpdesk

If the screen remains blank, **contact the Verifone Helpdesk for additional support**.

{% hint style="info" %}
**Need assistance? Contact Verifone Helpdesk at any time.**

* Use our Chat platform
* Or call 1.800.VERIFONE (837.4366)
  {% endhint %}

<details>

<summary>Keywords</summary>

Also called: black screen, screen off, unresponsive display. Search terms: blank screen, no display.

</details>


---

# 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/support-us/general-pinpad-support/general-pinpad-help/blank-screen.md?ask=<question>&goal=<user_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.