> 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/limitations-and-terms.md). # Limitations and Terms The **Sandbox** is the dedicated test environment of the **SEB Ecommerce Payment Gateway** and is available through the **SEB Merchant Portal**. Merchants use a **single Merchant Portal account** to access both **Sandbox Mode** and **Production Mode**. The active environment can be changed at any time using the environment selector in the Merchant Portal. Sandbox Mode is intended exclusively for development, integration testing, and user acceptance testing (UAT). It is designed to closely mirror the Production environment, allowing merchants to validate their integration before processing live customer transactions. Although Sandbox Mode closely resembles Production, certain functionality, payment methods, external services, and payment processing behaviour may differ from the live environment. {% hint style="info" %} You do not need separate Merchant Portal accounts for Sandbox and Production. The same account provides access to both environments, subject to the services enabled for your merchant account. {% endhint %} *** ## Intended Use Sandbox Mode is intended for: * Application development * Integration testing * User acceptance testing (UAT) * Merchant training * Validation of payment flows before Production activation {% hint style="warning" %} Sandbox Mode must not be used to process live customer transactions and live card data. {% endhint %} *** ## Environment Limitations The following limitations apply when using Sandbox Mode. | Feature | Sandbox | | -------------------------- | ------------- | | Live customer payments | Not available | | Real fund transfers | Not available | | Production banking systems | Not connected | | Payment authorizations | Simulated | | Settlement | Simulated | | Refund processing | Simulated | | Payment notifications | Simulated | | Production credentials | Not supported | | Test credentials | Supported | *** ## Payment Methods Only payment methods enabled for your Sandbox environment are available for testing. The available payment methods depend on: * Your merchant agreement * Enabled services * Sandbox configuration {% hint style="info" %} For evaluation, integration, or project-specific requirements, SEB may enable additional payment methods or functionality in Sandbox Mode as agreed between you and SEB. These capabilities are provided for testing and validation purposes and may differ from the services available in your Production environment. {% endhint %} Refer to Test Payment Methods for the list of supported payment methods and Test Data for available test cards, test banks, and test credentials. *** ## Test Data Use only the test data provided by SEB. This includes: * Test payment methods * Test cards * Test bank accounts * Test credentials * Other test values documented in the [**Test Data**](/guides/sandbox/test-data.md) section Sandbox transactions never reach live banking systems or payment networks. *** ## Personal Data Do not use Sandbox Mode to process or store: * Real customer payment information * Real payment card details * Personally Identifiable Information (PII) * Production credentials {% hint style="warning" %} Always use test data when developing or validating your integration. {% endhint %} *** ## Environment Availability The Sandbox environment may be updated, restarted, or reset as part of routine platform maintenance or service improvements. Merchants should not rely on Sandbox Mode for the long-term storage of: * Test transactions * Configuration data * Test users * Other non-persistent information *** ## Before Requesting Production Activation Before requesting Production activation, ensure that: * Your integration has been successfully validated. * All required payment scenarios have been tested. * Callback and webhook processing has been verified. * Order status updates are functioning correctly. * Sandbox credentials have been replaced with Production credentials. * Your Production configuration has been completed. {% hint style="warning" %} Although Sandbox Mode is designed to closely resemble the Production environment, differences may exist between the two environments. Merchants should always perform end-to-end validation after Production activation before processing live customer transactions. {% 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/limitations-and-terms.md?ask=&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.