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

# Merchant Portal Home page

Once logged in to the Tieto E-commerce Payment Gateway Sandbox, you will land on the Merchant Portal Home Page.

<figure><img src="https://1349856663-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuxLHJOqJIapfeJ1Ei4Hr%2Fuploads%2FFGQjKOpQerWUuOLv5vmn%2Fimage%20(22).png?alt=media&amp;token=9b522341-c7a6-466a-a5ef-39d3f6f6edd2" alt=""><figcaption></figcaption></figure>

This page serves as your main dashboard, offering a clear overview of your test environment activity and performance metrics based on your demo transactions.

The header in the Tieto E-commerce Gateway Sandbox provides essential navigation tools and user context, with certain limitations specific to the sandbox environment.

{% hint style="warning" %}
You will always see “Sandbox Mode” active in the environment switcher. The option to switch to Live Mode is disabled. Additionally, a persistent orange banner is displayed in the header, clearly indicating that you are operating within the sandbox environment.
{% endhint %}

{% hint style="warning" %}
The bell icon for notifications is also present in the header, but it is non-functional in sandbox mode—no alerts or messages will be displayed.
{% endhint %}

{% hint style="info" %}
The language selector is visible, but only English is available for use. Switching languages is disabled in the sandbox.
{% endhint %}

{% hint style="info" %}
Clicking on the user profile icon reveals a dropdown menu where you can view your profile details and log out of your session.
{% 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.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.
