> For the complete documentation index, see [llms.txt](https://commanderhelp.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://commanderhelp.verifone.com/pos-help/pos-help/pos-pairing/requirements-to-pair-your-register.md).

# Requirements to Pair your Register

This page gives or shows you the Prerequisites for pairing a POS register

What is the **exact Security Alert / pairing message** shown on the register?

Reply with the exact message you see on your POS/Register, for example:

* `SEC. ALERT – PAIRING`
* `SEC. ALERT – PAIRING REQUIRED`
* `SEC. ALERT – PAIRING INVALID`

***

**Another Scenario: Register was already rebooted (POS Pairing prompt)**

* **When you’ll see this:** After reboot, before pairing is completed.
* **What it means:** The register stays closed until pairing finishes.

**On-screen message**

<figure><img src="https://1678062793-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFYWyfZfb6YnJEuYJDRqw%2Fuploads%2FXrcQHxY5RUHGHUMP6au9%2F3.jpg?alt=media&amp;token=eeb19246-e2cf-431f-8f1e-4e9768c8eb7d" alt=""><figcaption></figcaption></figure>

### Requirements to Pair your Register <a href="#requirements" id="requirements"></a>

**You need the Configuration Client to complete these steps. You can do this in one of two ways:**

1. Use a **second POS (register)** terminal. Alternatively,
2. Use your **Back-office PC**, but the Configuration Client must be installed on it.

{% hint style="warning" %}
If you have only **One register** and **No Back-office PC**, you will need to contact the **Verifone Helpdesk** via **Chat or phone** at **1.800.VERIFONE(837.4366)** for **Pairing your register.**
{% endhint %}


---

# 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://commanderhelp.verifone.com/pos-help/pos-help/pos-pairing/requirements-to-pair-your-register.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.