> 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/get-started.md).

# Get started

SensePass is a payment platform. Businesses use it to accept card and wallet payments in store, online and by payment link. Partners use it to set up and manage the businesses they work with, and developers connect their systems to it through the SensePass APIs and SDKs.

### Choose your path

| I am...                                                      | Start here                                                                   |
| ------------------------------------------------------------ | ---------------------------------------------------------------------------- |
| A business that accepts payments with SensePass              | The **Merchants** part of the menu: the Merchant Dashboard                   |
| A partner (ISO, reseller or platform) that sets up merchants | The **Partners** part of the menu: SensePass Partners, the partner dashboard |
| A developer connecting a POS, online store or app            | The **Developers** part of the menu: the Transaction API and SDKs            |

Before you go further, read **How SensePass is organized**, **Choose your account structure** and **Sandbox and Production**.


---

# 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/get-started.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.