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

# SuiteCommerce

The **SensePass Payments for SC** bundle adds SensePass to the checkout of your NetSuite SuiteCommerce website.

### Install the bundle

1. In NetSuite, go to **Customization** > **SuiteBundler** > **Search & Install Bundles**.
2. Search for **SensePass Payments for SC**, select it and click **Install**.
3. Confirm the installation. It can take up to 15 minutes. Click **Refresh** to see the status.

### Add your SensePass credentials

1. In the global search, type **SensePass Credentials** and click **New SensePass Credentials**.
2. Enter:
   * **Sandbox**: API URL <https://api.sandbox.sensepass.com/api> and your Sandbox API key from SensePass Partners.
   * **Production**: API URL <https://api.sensepass.com/api> and your Production API key from SensePass Partners.
3. Save the record.

### Add the SensePass logo

1. Download <http://files.sensepass.com/NetSuite/Assets.zip> and unzip it.
2. Go to **Documents** > **Files** > **Live Hosting Files** > **site** (create the **site** folder if it does not exist).
3. Click **Add File** and upload **SensePass\_Logo\_Black.png**.

### Activate the extension

1. Go to **Commerce** > **Extensions** > **Extension Manager**, edit the website and domain, and click **Next**.
2. On the **Extensions** tab, select **SensePass Payments Integration** and click **Activate**. Refresh until the status is **Complete**.
3. Go to **Customization** > **Lists, Records, and Fields** > **Transaction Body Fields** and check that **SensePass Reference Number** exists with: Type **Free-Form Text**, **Store Value** selected, and on the **Applies To** tab, **Sale** and **Display in Website** selected.

### Configure the website

1. Go to **Commerce** > **Websites** > **Configuration**, select the website and domain, and click **Configure**.
2. Open the **Extension** tab > **SensePass Payments** subtab and set:

| Field                                 | Value                                                                                                             |
| ------------------------------------- | ----------------------------------------------------------------------------------------------------------------- |
| SensePass Capture Type                | **Authorize**: capture later, when the cash sale is created. **Manual Capture**: capture at checkout.             |
| SensePass Mode                        | Sandbox or Production                                                                                             |
| SensePass Client ID                   | Your Client ID from SensePass Partners (Developer > Client ID)                                                    |
| True one page checkout                | Select to use one-page checkout                                                                                   |
| SensePass Modal on page               | Select to show the SensePass window on the payment page. If cleared, it opens just before the order is submitted. |
| Hide Non-SensePass Payment Methods    | Select to choose SensePass automatically and hide other payment methods                                           |
| Show Developer Logs                   | Leave cleared (for debugging only)                                                                                |
| Credit Card button color              | Color of the Pay with Credit Card button, as a 6-digit hex code (for example #FF0000)                             |
| SensePass Payment Method Display Text | Text shown when the SensePass window is not on the page                                                           |
| Minimum Order Amount                  | Optional. SensePass is not offered below this amount.                                                             |

3. On the **Advanced** tab > **Custom Fields** subtab, add the internal ID of the **SensePass Reference Number** field to **Field ID**, and save.
4. Go to **Commerce** > **Websites** > **Website List** and edit the website. On the **Shopping** tab, select **Display Purchase Order Field on Payment Info Page** and **Allow Non-Credit Card Payment Methods During Checkout**. Save.

### Add the payment method

1. Go to **Setup** > **Accounting** > **Accounting Lists** > **New** > **Payment Method**.
2. In **Name**, enter **Sensepass** exactly (the name is case sensitive), set **Type** to **Offline**, and select **Display in Website**.
3. On the **Payment Visuals** tab, enter **Web/Standard** in **Flag**, enter /site/SensePass\_Logo\_Black.png, click **Add** and save.

### Update the payment service file

1. Go to **Documents** > **Files** > **File Cabinet** and search for **SensePassPayment.Service.ss**.
2. Download the file from the folder ...SuiteCommerce Standard : extensions : Anchorgroup : SensepassPayments : (version) : services.
3. Edit the file. On the **Permissions** tab, set **Execute as Role** to **CEO** and click **Select All** for **Roles**.
4. Go to Web Site Hosting Files > Live Hosting Files > SSP Applications > NetSuite Inc. - SCS > SuiteCommerce Standard > Services, click **Add File** and upload the file.
5. Set the same permissions on the new file.


---

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