> For the complete documentation index, see [llms.txt](https://docs.sensepass.com/sensepay/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sensepass.com/sensepay/transaction-api/terminal-agent/pairing.md).

# Pairing

#### Configuration

1. Double click on "SensePass Configurator" icon on your desktop, if you can't find it - open your browser with this URL: **<http://localhost:3031>**

{% hint style="info" %}
Make sure you are using Chrome or Edge with the latest version installed
{% endhint %}

2. This screen will be shown:

<div align="left"><figure><img src="/files/GM5awq3IsZOQ6se1bCdX" alt="" width="375"><figcaption></figcaption></figure></div>

**Location** - Choose the current location for your POS, adding locations to this list can be performed using the Partners platform

**EMV** - Choose the required pinpad type

**POS Name** - friendly name for the POS that will be shown in the merhcnat dashboard to recognize your payments

**Pairing Code** - the (XXX-XXX-XXX) code that is shown below the QR code on the SensePass tag

Click on the "Continue" button and close the window after the succesful pairing message presented.

**All set !**


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.sensepass.com/sensepay/transaction-api/terminal-agent/pairing.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.