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

# Orders

The Orders section in the Merchant Portal gives you full visibility into all payments initiated through the sandbox, whether via the Demo Store or custom checkout flows. It serves as your transaction log and monitoring console for evaluating test activity.

### What You Can Do

In the Orders view, you can:

* See a list of all your test transactions with:
  * Transaction ID
  * Date and time
  * Payment method used
  * Amount
  * Current status (e.g., Authorized, Captured, Failed)
* Download a report of the transactions found in your search in CSV format. The Download button is located in the top-right corner of the screen.
* Click on any order to open a detailed view, which includes:
  * Full data about particular transaction
  * Download the details of a specific transaction or order. The Download button is located in the top-right corner of the transaction detail screen.
* Filter orders by:
  * Status (e.g., only “Authorized”)
  * Payment method (e.g., only “Card”)
  * Date range
* View which test shop the order was created from

<figure><img src="https://1349856663-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuxLHJOqJIapfeJ1Ei4Hr%2Fuploads%2FDBq194IMhs9WlivQ9gQN%2FScreen%20Recording%202025-07-08_oder.gif?alt=media&amp;token=3df8578f-caca-48fd-8215-9bdcc5a554e5" alt=""><figcaption><p>Orders</p></figcaption></figure>

{% hint style="info" %}

* All transactions shown are mocked and created using sandbox payment flows.
* Status changes (e.g., capture or refund) may appear automatically depending on test flow.
* The Orders view does not generate live alerts or settlement actions.
  {% 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/orders.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.
