> 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.md).

# Platforms

SensePass connects to the platforms that merchants already use to sell: ERP systems, e-commerce stores and POS systems. Each page below explains how to install and configure SensePass on one platform.

| Platform                          | Type                  | What you get                                                                                                                               |
| --------------------------------- | --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------ |
| **NetSuite ERP**                  | ERP                   | Payment links, saved cards (tokens), card payments on sales orders, invoices and customer records, refunds, EMV PinPads and SensePass tags |
| **SuiteCommerce**                 | E-commerce (NetSuite) | SensePass at checkout on your SuiteCommerce website                                                                                        |
| **SuiteCommerce In-Store (SCIS)** | POS (NetSuite)        | EMV PinPads in SCIS                                                                                                                        |
| **Shopify**                       | E-commerce            | Card payments at Shopify checkout                                                                                                          |
| **Shopify POS**                   | POS                   | Customers pay a Shopify POS sale with a SensePass tag (NFC or QR)                                                                          |
| **BigCommerce**                   | E-commerce            | SensePass at BigCommerce checkout, with authorization or capture                                                                           |
| **Magento / Adobe Commerce**      | E-commerce            | SensePass payment method at Magento checkout                                                                                               |
| **Lightspeed (Vend)**             | POS                   | SensePass as a payment type; customers pay with a SensePass tag                                                                            |
| **RMH (Retail Management Hero)**  | POS                   | SensePass tender in RMH POS, split tender, card on file, returns and voids                                                                 |
| **Oracle Xstore**                 | POS                   | Customers pay an Xstore sale with a SensePass tag                                                                                          |
| **SensePass KCP adapter**         | Connector             | See the KCP adapter page                                                                                                                   |

## Before you start

Most platforms need values that you create in **SensePass Partners**:

* **API key**: a location API key (Developer > Branch API) or a merchant API key (Developer > Merchant API).
* **Client ID**: for platforms that show the SensePass payment widget in the browser (Developer > Client ID).
* **POS / Register and tag**: for platforms that take in-person payments.

Use **Sandbox** while you set up and test, and switch to **Production** to take live payments. See **Sandbox and Production** in Get started.


---

# 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.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.
