> For the complete documentation index, see [llms.txt](https://doc.ecomm.api.tietoevry.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.ecomm.api.tietoevry.com/e-commerce-payment-gateway/sandbox-guide/merchant-portal-home-page/settings.md).

# Settings

The Settings section in the Merchant Portal provides access to all configuration areas related to your business, shops, checkout design, and user access. It is organized into the following key subsections:

### **Business Settings**

This section displays your merchant agreement details and overall business profile.

{% hint style="info" %}
In sandbox mode, this data is pre-filled and read-only, intended for demonstration purposes only.
{% endhint %}

### **Shop Settings**

Here you can manage your individual shops, including:

* Creating up to 5 test shops
* Editing shop information
* Configuring technical parameters
* Managing payment methods, wallets, currencies, and banks

### **Customize Checkout**

Use this section to manage the design and branding of the Hosted Checkout Page individually per shop.

You can configure logo, colors, fonts, button styles and more, and preview both desktop and mobile views.

### **User Management**

Displays the list of all users associated with your merchant account and their assigned roles.

{% hint style="info" %}
In sandbox mode, user invitations are not allowed. You can only view existing users created as part of the test setup.
{% endhint %}


---

# 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://doc.ecomm.api.tietoevry.com/e-commerce-payment-gateway/sandbox-guide/merchant-portal-home-page/settings.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.
