> 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/pairing-message-displayed-on-register.md).
# Pairing Message Displayed on Register
This page explains the Pairing-related Security Alerts shown on the register and which action to take.
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**
{% hint style="info" %}
**NOTE:** If you are a **Circle K** site, please contact [Helpdesk](https://support.verifone.com/s/) as site managers/cashiers do not have security access on Config Client.
{% endhint %}
***
### Message Displayed on Register
**The tabs below display the various Pairing messages shown when pairing is required**
{% tabs fullWidth="true" %}
{% tab title="SEC. ALERT – PAIRING / PAIRING REQUIRED" %}
If you have received one of these two, follow the POS pairing steps on [**How to Pair a Register**](/pos-help/pos-help/pos-pairing/how-to-pair-a-register.md).
* SEC. ALERT – PAIRING
* SEC. ALERT – PAIRING REQUIRED
{% endtab %}
{% tab title="SEC ALERT PAIRING INVALID" %}
If you have received the following message, then follow the steps given below.
* SEC. ALERT- PAIRING INVALID
1. [**Pair the Register**](/pos-help/pos-help/pos-pairing/how-to-pair-a-register.md) if **any** of the following events occurred recently:
* New POS installation
* VRSD/Commander Software Upgrade
* POS software reload
2. **Contact** the **Verifone Helpdesk** via [Helpdesk](https://support.verifone.com/s/) or phone at **1.800.VERIFONE (837.4366)** if **none** of the above happened and:
* The POS was already paired within the last **52 weeks**, or
* You are **not sure** when it was last paired
{% endtab %}
{% tab title="Perform POS Pairing" %}
If you see the following message on your POS,
* Perform POS pairing
POS screen showing Perform POS Pairing
Follow the instruction from **Step 3** on [Steps to Pair a Register](/pos-help/pos-help/pos-pairing/how-to-pair-a-register.md) to complete the pairing process and return to sales screen on the POS/register.
{% endtab %}
{% endtabs %}
{% hint style="info" %}
It is crucial to follow this process exactly to ensure a successful pairing.
{% endhint %}
This guide explains how to securely connect your **Point of Sale (POS)** system to the **Commander** for smooth transaction processing. Follow these steps closely to avoid errors or complications. Use [**How to Pair a Register**](/pos-help/pos-help/pos-pairing/how-to-pair-a-register.md) to complete the pairing process efficiently.
***
### **Examples Screenshots of Pairing Security Alerts that you may see on your POS:**
{% 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 %}
\* To clear these messages, the POS pairing process needs to be completed.
---
# 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/pairing-message-displayed-on-register.md?ask=&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.
