> 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/business-settings.md).

# Business Settings

The Business Settings section is accessible from the left-hand menu under:

Settings → Business Settings

This area provides a structured view of your organization’s profile and configuration within the sandbox environment. Although most fields are view-only in sandbox mode, it offers a realistic preview of how merchant information is organized and displayed in a live setup.

{% hint style="info" %}
All data shown in sandbox is for demonstration purposes only. In a live environment, the information may differ and include additional fields or regulatory details based on your onboarding and contractual agreements.
{% endhint %}

#### Tabs Available in Business Settings

* General

  Displays your registered business name, legal entity identifier, and onboarding metadata.
* Shops

  Lists all test shops under your business account, including Shop ID, name, and associated environment.
* Contact Information

  Shows your company’s email, phone number, and physical address as provided during sandbox setup.
* Tax Details

  Displays your VAT ID and tax status — for reference only.
* Bank Account

  Displays non-functional placeholder information representing merchant settlement details.

{% hint style="info" %}
*In the production environment, most of these fields are populated during onboarding and may be editable based on your role and integration type.*
{% 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/business-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.
