> 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/suitecommerce-in-store-scis.md).

# SuiteCommerce In-Store (SCIS)

Use SensePass EMV PinPads in NetSuite SuiteCommerce In-Store (SCIS). Install the NetSuite ERP bundle first (see **NetSuite ERP**).

### Add a PinPad to SCIS

1. In SensePass Partners (Sandbox: <https://partner.sandbox.sensepass.com>, Production: <https://partner.sensepass.com>), go to **POS / Register** and click **Create POS / Register**.
2. Enter a **POS Name**, set **Pairing Mode** to **QR** and type the tag pairing code (XXX-XXX-XXX), set **Type** to **POS Paired**, and click **Save**.
3. Copy the **Device Identifier** of the new register with the copy icon.
4. Go to **Management** > **EMV Terminals** and click **New**. Enter a **Name**, select the **Device** you created and the PinPad **Type**, and save.
5. In NetSuite, go to **Customization** > **Lists, Records & Fields** > **Record Types**.
6. Open **SCIS Payment Device** and click **List**, then click **New SCIS Payment Device**.
7. Enter:
   * **Name**: the name shown in SCIS
   * **Device ID**: the Device Identifier you copied
   * **Locations**: the location for the device
   * **Supported Payment Method**: leave blank
8. Click **Save**.


---

# 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/suitecommerce-in-store-scis.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.
