> 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/partners/partner-dashboard/creating-a-merchant.md).

# Creating a merchant

1. In the left menu, click **Merchants**.
2. Click **+ New**. The **Create Merchant** window opens.
3. Fill in the required fields (marked with \*) and any optional fields. See the table below.
4. Click **Save** at the bottom of the window.

<figure><img src="https://3556089516-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MbqMA3Kf8t2xEX9F6y9%2Fuploads%2FYHS27pJJV4BU6vdATnTP%2Fp-create-merchant.png?alt=media" alt="Create Merchant window"><figcaption><p>Create Merchant window</p></figcaption></figure>

| Section            | Required fields                                          | Optional fields                                                                                                                   |
| ------------------ | -------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------- |
| Merchant Details   | License ID, License Name, Display Name, Locale, Category | Phone, Email, Website                                                                                                             |
| Merchant Address   | Street, City, Country                                    | House Number, State, Logo                                                                                                         |
| Merchant Contact   | Name, Phone, Email                                       | -                                                                                                                                 |
| Payment Page Style | -                                                        | Logo Image, Logo Position, Logo Size, Header Text Color, Background Color, Background Repeat, Hide Business Title, SensePass Logo |
| Configuration      | -                                                        | **Skip Approval Page**: the customer does not see the approval (confirmation) screen after the payment.                           |

**The merchant menu**

To work with an existing merchant, find it on the **Merchants** page (use the search box to search by license ID or display name) and click the three-dot menu at the end of its row. The menu has these options: **Edit**, **Locations**, **Payment Methods**, **POS / Register**, **Billing**, **Merchant API** and **Settings**.

<figure><img src="https://3556089516-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MbqMA3Kf8t2xEX9F6y9%2Fuploads%2FCSnKtQM657VvtFSNaSQZ%2Fp-merchant-menu.png?alt=media" alt="Merchants page: the three-dot menu of Demo Coffee Co"><figcaption><p>Merchants page: the three-dot menu of Demo Coffee Co</p></figcaption></figure>


---

# 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/partners/partner-dashboard/creating-a-merchant.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.
