> 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-nordics/v660p/how-tos/terminal-setup-out-of-box.md).

# Terminal Setup (Out of Box)

Set up your new V660P for the first time — language, network, and Device ID.

{% hint style="info" %}
**Use this when** you're starting your new V660P for the first time.
{% endhint %}

## Before you start

{% hint style="warning" %}

* **Charge the terminal fully** before you set it up.
* Have your **welcome email from Verifone** ready. It contains the **QR code** and **Device ID** you need to activate the terminal.
* If you're using **mobile data**, insert the SIM card first — see [How to Set Up Mobile Data](/support-nordics/v660p/how-tos/how-to-set-up-mobile-data.md).
  {% endhint %}

## Set up the terminal

{% stepper %}
{% step %}

### Turn on the terminal

Hold the **power button** for about **2 seconds** until the start screen appears.
{% endstep %}

{% step %}

### Choose your language

Select your **language and country**, then tap **Next**.

{% hint style="info" %}
Tap the **information icon (ⓘ)** to see a summary of the terminal, such as its serial number and battery level.
{% endhint %}
{% endstep %}

{% step %}

### Connect to the network

Choose your **Wi-Fi network** from the list and enter the Wi-Fi password, then tap **Next**. The terminal connects automatically when the password is correct.

* **Using mobile data (SIM) or a network cable?** You can tap **Next** without choosing a Wi-Fi network.
* **Need a static IP address?** Tap **Advanced Options** to enter it.
  {% endstep %}

{% step %}

### Wait for the network check

The terminal checks its internet connection and the date and time. You don't need to do anything.
{% endstep %}

{% step %}

### Enter the Device ID

Tap **Next**, then choose either:

* **Scan QR Code** — scan the QR code from your welcome email, or
* **Enter Device ID Manually** — type the Device ID from your welcome email and tap **Submit**.
  {% endstep %}

{% step %}

### Wait for the software to install

The terminal checks for, downloads, and installs its software. **Don't do anything until it's finished** — the terminal may restart several times.
{% endstep %}

{% step %}

### Finish setup

When you see **Complete**, tap **OK**. **Connect Express** opens and the terminal is ready to use.
{% endstep %}
{% endstepper %}

{% hint style="warning" %}
**Stuck on "Checking for updates"?** See [Stuck Checking for Updates](/support-nordics/v660p/errors/stuck-checking-for-updates.md).
{% endhint %}

<details>

<summary>Keywords</summary>

Also called: out of box, first-time setup, activate terminal, new terminal, device ID, QR code. Search terms: setup, activation, device ID, QR code, welcome email, Wi-Fi, language, software update.

</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-nordics/v660p/how-tos/terminal-setup-out-of-box.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.