> 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/lightspeed-vend.md).

# Lightspeed (Vend)

With SensePass as a payment type in Lightspeed (Vend), customers pay a sale by tapping or scanning the SensePass tag at the register.

## Before you start

You need:

* The **location API key** from SensePass Partners. See **Creating API keys** in the Partner Dashboard pages.
* The **pairing code** of the SensePass tag for each register (the code printed under the QR code).

## Add SensePass as a payment type

1. In Lightspeed, go to **Setup** > **Payment Methods**.
2. Click **Add Payment Type** and choose **Other Payment Type**.
3. Enter:
   * **Name**: for example `SensePass`
   * **Outlet**: the outlets where it is available
   * **Gateway**: `https://pos.sensepass.com?apiKey=<LOCATION_API_KEY>`
4. Save.

## Pair each register

1. Start a sale and choose the **SensePass** payment type.
2. The first time only, enter the tag pairing code and click **Pair**.

## Take a payment

1. Ring up the sale and choose the **SensePass** payment type.
2. The customer taps or scans the SensePass tag and pays on their phone.


---

# 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/lightspeed-vend.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.
