> 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/platforms/oracle-xstore.md).

# Oracle Xstore

The SensePass integration for Oracle MICROS Xstore runs as a Windows service next to Xstore and lets customers pay by tapping or scanning the SensePass tag at the register.

## Before you start

You need:

* The SensePass Xstore installation file, which SensePass provides.
* The **pairing code** of the SensePass tag for each register (the code printed under the QR code, for example `123-ABC-456`).

## Install

1. Run the SensePass Xstore setup file.
2. Click **Install**.
3. Select the installation folder.
4. Click **Finish**.
5. Open Windows Services and check that the **SensePass server** service is running.

{% hint style="info" %}
SensePass may give you a "copy only" version of the setup file. In that case, SensePass completes the database setup with you before you pair.
{% endhint %}

## Pair each register

1. In the installation folder, open `XstoreParing.html`.
2. Enter:
   * **EMV**: none
   * **POS Name**: the register name
   * **Pairing Code**: the code under the QR code on the register's SensePass tag
3. Click **Continue**. A message confirms that pairing succeeded.

Repeat for every register.


---

# 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.sensepass.com/sensepay/platforms/oracle-xstore.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.
