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

# Dashboard

The **Dashboard**, available from **Home** in the Merchant Portal, provides a high-level view of payment activity across your shops.

When you sign in to the Merchant Portal, **Home** is your starting point and displays the Dashboard with key payment activity and operational indicators.

Use the Dashboard to monitor payment performance, identify trends or unusual changes, and determine when individual transactions require further investigation in **Orders**.

Depending on the selected view, you can monitor a specific shop or aggregated payment activity across multiple shops.

{% hint style="info" %}
Dashboard information is intended for operational monitoring and analysis. It does not replace official settlement, reconciliation, acquiring, or accounting records.
{% endhint %}

***

### Monitor payment performance

The Dashboard presents key indicators based on payments processed through the Payment Gateway.

Depending on your configuration, these may include:

* **Total processed volume** — the value of payments processed during the selected period
* **Card transactions** — transaction activity related to card payments
* **Account transactions** — activity related to account-based payment methods
* **Approval rate** — the proportion of payment attempts that were successfully approved
* **Refund ratio** — the relationship between refunded and processed payment activity
* **Click to Pay transactions** — activity processed using Click to Pay

Additional widgets may be available depending on the services configured for your merchant account.

<figure><img src="https://1157570179-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuBDtfypkI85zidcVwaDj%2Fuploads%2Fn0hlgSMYwCRfe5BO7wcx%2FScreen%20Recording%202026-08-11%20at%2018.14.10.gif?alt=media&amp;token=388a3461-cac2-4447-afca-0832ddbf138a" alt=""><figcaption></figcaption></figure>

***

### Choose the period you want to analyse

You can adjust the Dashboard to focus on the period relevant to your analysis.

<figure><img src="https://1157570179-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuBDtfypkI85zidcVwaDj%2Fuploads%2FaeD57PUMKrGV7pO8Mf47%2FScreenshot%202026-08-17%20at%2016.41.11.png?alt=media&amp;token=9347e9b9-36a8-411a-b204-8c8d63068dba" alt=""><figcaption></figcaption></figure>

Depending on the available configuration, you can:

* select a reporting period
* compare it with an earlier period
* change the aggregation interval
* view an individual shop or a consolidated multi-shop view
* filter or segment information by payment method

This can help you distinguish normal day-to-day variation from changes that may require further investigation.

For example, comparing today's approval rate with the previous day can help identify a sudden deterioration in payment performance, while a longer period is more useful for identifying broader trends.

***

### Understand transaction activity

The **Transaction breakdown** gives you a visual overview of payment activity by payment method.

Depending on the payment methods available for your shop, the Dashboard may show activity for cards, account-based payments, or digital wallets such as Apple Pay, Google Pay, PayPal, and Click to Pay.

Use this view to understand which payment methods contribute to your payment activity and whether their usage changes over time.

For transaction-level details, select **View transactions** or continue to [**Orders**](/guides/merchant-portal/monitor-your-business/orders.md).

***

### Monitor transaction statuses

The Dashboard can show how transactions are distributed across different statuses.

This helps you identify whether payment activity is completing as expected or whether there is an increase in unsuccessful or incomplete payment attempts. Supported status information may include states such as authorized, captured, settled, failed, refunded, or cancelled.

The meaning and expected lifecycle of a payment depends on the payment method and payment flow.

For detailed status definitions and recommended merchant actions, see [**Payment Statuses**](/payment-methods/cards/payment-statuses.md).

***

### Understand payment method usage

The [**Payment methods**](/payment-methods/cards.md) view helps you understand how customers choose to pay.

You can use it to compare the relative usage of enabled payment methods and identify changes in customer payment preferences.

Depending on the Dashboard configuration, payment methods may be compared by transaction volume or amount.

***

### Work with multiple shops

If your merchant account contains multiple shops, you may be able to view either:

* aggregated information across all shops you can access, or
* Dashboard data for a specific shop.

The shops available to you depend on your assigned permissions.

When analysing unexpected results, check the selected shop before comparing Dashboard values with your own operational records.

<figure><img src="https://1157570179-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuBDtfypkI85zidcVwaDj%2Fuploads%2Fx289LJZtDKVdeaLMHqrZ%2FScreenshot%202026-08-17%20at%2016.51.55.png?alt=media&amp;token=565f37ad-ba02-4568-b11a-d23f8e902471" alt=""><figcaption></figcaption></figure>

***

### Customize your Dashboard

Where supported, you can customize which Dashboard components are displayed and how they are arranged.

This lets you focus the Dashboard on the information most relevant to your day-to-day operations.

Changing the Dashboard layout affects only how information is presented. It does not change the underlying transaction data or how Dashboard metrics are calculated.

<figure><img src="https://1157570179-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuBDtfypkI85zidcVwaDj%2Fuploads%2FxLArWc8ex9fV8UE6njnD%2FScreen%20Recording%202026-08-11%20at%2018.19.01.gif?alt=media&amp;token=7f1aa4b7-acad-4451-961d-344fc6f21a0f" alt=""><figcaption></figcaption></figure>

***

### Sandbox and Live data

Dashboard data is separated between Sandbox and Live environments.

**Sandbox mode** displays test activity created for integration testing, validation, or training. Sandbox transactions do not represent real financial activity.

**Live mode** displays production payment activity.

<figure><img src="https://1157570179-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuBDtfypkI85zidcVwaDj%2Fuploads%2FXwXredRgGNVxUJ4P9e8g%2FScreen%20Recording%202026-08-17%20at%2016.57.57.gif?alt=media&amp;token=61ec896b-5092-4a5d-874a-68a6556495e3" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Always check the current environment before using Dashboard information for operational analysis.
{% endhint %}

***

### When to use Orders instead

The Dashboard is most useful when you want to understand **what is happening across your payment activity**.

Use [**Orders** ](/guides/merchant-portal/monitor-your-business/orders.md)when you need to understand **what happened to a specific payment**.

For example, go to Orders when you need to:

* find a payment using an order or payment reference
* check the latest payment status
* review transaction history
* investigate a failed or declined payment
* review capture, cancellation, or refund activity
* export transaction-level data

See [**Orders**](/guides/merchant-portal/monitor-your-business/orders.md).

***

### Frequently Asked Questions

<details>

<summary>Why do Dashboard values change after I refresh the page?</summary>

Payment statuses can change as transactions progress through their lifecycle, and Dashboard information may be updated as new transaction or external provider data becomes available.

</details>


---

# 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/dashboard.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.