> 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-uk/t650/how-tos/how-to-shut-down-the-terminal.md).

# How To Shut Down the Terminal

Manually power off the Trinity (T650) terminal.

{% hint style="info" %}
**Use this when** you need to manually power off the Trinity (T650) terminal.
{% endhint %}

This page explains how to manually shut down the terminal.

## Shut down the terminal

{% stepper %}
{% step %}

### Hold the power button

Hold the start/power button for about 1 second, until a message is displayed on the screen.
{% endstep %}

{% step %}

### Confirm power off

Touch the "Power Off" selection to turn the terminal off.
{% endstep %}
{% endstepper %}

## Guidelines

* Holding the power button for about 3 seconds instead starts the terminal up — only a 1 second hold is needed to bring up the shutdown message.

## FAQ

<details>

<summary>How long do I hold the power button to shut down?</summary>

About 1 second, until the shutdown message appears on screen.

</details>

<details>

<summary>Keywords</summary>

Also called: power off, turn off, manual shutdown. Search terms: shutdown, power button, Trinity, T650.

</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-uk/t650/how-tos/how-to-shut-down-the-terminal.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.
