> For the complete documentation index, see [llms.txt](https://docs.ecommerce.seb.ee/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ecommerce.seb.ee/guides/merchant-portal/monitor-your-business.md).

# Monitor your business

Monitor payment activity, review performance trends, and investigate individual transactions using Dashboard and Orders.

Use the **SEB Merchant Portal** to monitor payment activity, understand operational trends, and investigate individual transactions.

When you sign in to the Merchant Portal, the **Dashboard** is your starting point and provides an aggregated overview of payment activity for the selected shop or shops.

Use the **Dashboard** to monitor overall payment activity and trends. Open **Orders** when you need to find, review, investigate, or manage a specific transaction.

{% hint style="info" %}
The information displayed depends on the selected **environment**, **shop or shops**, available payment data, and the services enabled for your merchant account.
{% endhint %}

***

### Dashboard

Use the [**Dashboard**](/guides/merchant-portal/monitor-your-business/dashboard.md) to monitor payment activity and key operational indicators.

Depending on the services and payment methods enabled for your merchant account, you can monitor information such as:

* Processed payment volume
* Transaction counts and trends
* Approval rates
* Refund indicators
* Payment method activity

Use the available **period** and **shop** selectors to review activity for a specific shop or across multiple shops.

{% content-ref url="/pages/CKtQl7D5b55QAJhv7L8j" %}
[Dashboard](/guides/merchant-portal/monitor-your-business/dashboard.md)
{% endcontent-ref %}

***

### Orders

Use [**Orders**](/guides/merchant-portal/monitor-your-business/orders.md) when you need to find and investigate a specific transaction.

You can:

* Search and filter transactions.
* Verify payment statuses.
* Review payment, order, and customer information.
* Find the Payment ID.
* Review refunds, where applicable.
* Perform supported payment operations, such as capture, cancellation, or refund, where available.
* Download transaction information or export search results.

The available information and operations depend on the payment method, payment status, shop configuration, enabled services, and your user permissions.

{% content-ref url="/pages/A1lP0MvTSWAlvDsZDFgq" %}
[Orders](/guides/merchant-portal/monitor-your-business/orders.md)
{% endcontent-ref %}

***

{% hint style="info" %}
**Operational information**

Dashboard and Orders are intended for monitoring and managing payment activity. They do not replace official settlement, reconciliation, acquiring, or accounting records.

For financial reconciliation, use the applicable settlement reports, acquiring statements, or other official reconciliation information provided for your merchant account.
{% 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://docs.ecommerce.seb.ee/guides/merchant-portal/monitor-your-business.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.