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

# Sandbox

The **Sandbox** is the dedicated test environment of the **SEB Ecommerce Payment Gateway**. It enables merchants to develop, integrate, and validate their payment solution before processing live customer transactions.

Sandbox Mode closely mirrors the Production environment, allowing merchants to validate payment flows, merchant configuration, and API integrations using test data in a secure environment.

{% hint style="info" %}
No real customer funds are transferred and no live payment transactions are processed in Sandbox Mode.
{% endhint %}

***

### What You Can Do

Use Sandbox Mode to:

#### Integration & Testing

* Develop and validate your payment **integration**.
* Test supported payment methods using dedicated **test data**.
* Validate customer payment journeys.
* Verify callback and webhook processing.
* Test refunds and other supported payment operations.

#### Merchant Configuration

* Create and manage Sandbox Shops.
* Configure supported payment methods.
* Configure callback and return URLs.
* Generate and manage Sandbox API credentials.
* Customize your hosted checkout page.
* Configure merchant and shop settings.

#### Merchant Portal

* Review Sandbox orders and payment details.
* Generate Payment Links and QR Codes.
* Monitor transaction analytics through Dashboards.
* Track your requests in **My Requests**.
* Explore Demo Store.

#### Production Readiness

* Validate your complete merchant configuration.
* Verify operational workflows.
* Prepare your integration for Production activation.

***

## Before You Begin

Before using Sandbox Mode, ensure that:

* Your Merchant Agreement with SEB has been completed.
* Your Merchant Portal account has been activated.
* Sandbox Mode has been enabled for your merchant account.
* You have access to the relevant integration documentation.

{% hint style="info" %}
If you have not yet completed merchant onboarding, please refer to the [**Quick Start**](/getting-started/quickstart.md) guide.
{% endhint %}

***

## Sandbox and Production

The **SEB Merchant Portal** provides access to both **Sandbox Mode** and **Production Mode**.

Use the environment selector in the Merchant Portal to switch between the two environments.

| Sandbox Mode                 | Production Mode            |
| ---------------------------- | -------------------------- |
| Development and testing      | Live payment processing    |
| Test credentials             | Production credentials     |
| Test payment methods         | Live payment methods       |
| Simulated payment processing | Live payment processing    |
| No real customer funds       | Live customer transactions |

{% hint style="info" icon="lightbulb-exclamation-on" %}
Production Mode becomes available only after your integration has been successfully validated and your production environment has been activated by SEB.
{% 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/sandbox.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.