> 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/using-sandbox-mode.md). # Using Sandbox Mode The **SEB Merchant Portal** provides access to both **Sandbox Mode** and **Production Mode** through a single portal. After your Merchant Portal account has been activated, you will initially have access to **Sandbox Mode**, where you can develop, configure, integrate, and validate your payment solution using test data. Once you have successfully completed your testing and are ready to process live customer transactions, you can request **Production activation** from SEB (where applicable). After Production access has been enabled, the same Merchant Portal account can be used 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 header. *** ## Switching Environments The Merchant Portal supports two environments: | Environment | Purpose | | ------------------- | ----------------------------------------------------------------- | | **Sandbox Mode** | Development, integration testing, and validation using test data. | | **Production Mode** | Processing live customer transactions. | Use the environment selector in the Merchant Portal header to switch between Sandbox and Production.
{% hint style="info" %} Sandbox and Production are separate environments. Configuration, credentials, and data are not automatically shared between them. {% endhint %} *** ## Getting Started After signing in to the **SEB Merchant Portal** for the first time, you will automatically enter **Sandbox Mode**. Depending on your merchant agreement and the services enabled by SEB, your Sandbox environment may already include one or more pre-configured Sandbox Shops. To verify your configuration: 1. Navigate to **Settings → Shop Settings**. 2. Review the available shops. If a Sandbox Shop has already been configured by SEB, you can immediately begin configuring your integration and testing payment flows. If no Sandbox Shop is available, you can create one as described below. *** ## Creating a Sandbox Shop After signing in to the Merchant Portal, check whether a Sandbox Shop has already been created for your merchant account. You can do this by navigating to either: * **Settings → Business Settings → Shops**, or * **Settings → Shop Settings** If a Sandbox Shop has already been configured by SEB, it will be displayed and you can immediately begin configuring your integration. If no Sandbox Shop is available, create one as follows: 1. Select the **Add New Shop** button. 2. Complete the required information: * **Shop Type** – Select **Sandbox**. Depending on your merchant agreement with SEB, the **Live** shop type may also be available. However, when creating a shop for development and testing, always select **Sandbox**. * **Shop Display Name** * **Home URL** – Enter the complete URL, including the protocol (for example, `https://www.example.com`). * **Products and Services Sold** – Select the category that best describes the products or services provided by your business. The list is based on standard Merchant Category Codes (MCC), for example **Utility Payments**, **Retail**, **Travel**, **Restaurants**, or other applicable business categories. 3. Select the **Add New Shop** button. Sandbox Shop requests are approved automatically. You can monitor the request status under **My Requests**. Once approved, the Sandbox Shop becomes immediately available.
{% hint style="info" %} If the **Live** shop type is available for your merchant account, Production Shop requests are reviewed and approved by SEB before they become available in **Production Mode**. {% endhint %} *** ## Selecting a Sandbox Shop If your merchant account contains multiple Sandbox Shops, use the **Shop selector** in the upper-right corner of the Merchant Portal to select which shop or group of shops you want to work with. The Shop selector allows you to: * **All active shops** – View aggregated information across all active shops. * **All shops** – View information across all available shops. * **Specific shop** – View and work with data for an individual Sandbox Shop. * **Search** – Find a specific shop when multiple shops are available.
When a specific shop is selected, the Merchant Portal displays information and functionality related to that shop, including transactions, configuration, payment methods, and technical information. When **All active shops** or **All shops** is selected, supported Merchant Portal pages, such as the Dashboard, display aggregated information across the applicable shops. {% hint style="warning" %} Before reviewing or changing shop-specific configuration, accessing API credentials, or performing shop-specific operations, always verify that the correct **Sandbox Shop** is selected. {% endhint %} *** ## Managing Your Sandbox Shop To modify the configuration of an existing Sandbox Shop, navigate to **Settings → Shop Settings**, select the required shop, and click **Edit Agreement**. The **Manage Shop Agreement** window allows you to configure your Sandbox Shop through dedicated sections, depending on your merchant agreement and the services enabled by SEB. The available sections include: * **Shop Details** – Manage shop information, business details, and shop settings. * **Payments** – Configure supported payment methods, services, accepted currencies, and digital wallets. * **Bank Payments** – Configure supported countries and participating banks for Pay by Bank. * **Bank Accounts** – View the settlement account assigned to the shop. * **Technical Information** – Configure integration settings, including Home URL, Callback URL, Payment Authorization Type, Payment Capture Delay, and access your Sandbox API credentials. * **Fees** – View the fees configured for the shop. * **Limits** – View the operational limits configured for the shop. Some settings are read-only or may not be available depending on your merchant agreement and assigned user permissions.
After making changes, click **Submit for Approval**. {% hint style="info" %} Changes made to Sandbox Shops are approved automatically and become available immediately. {% endhint %} *** ## Sandbox API Credentials Each Sandbox Shop has its own API credentials. Use them to authenticate your application with the **Sandbox Merchant API**. Sandbox API credentials are generated separately from Production credentials and are unique to each Sandbox Shop. {% hint style="info" %} Sandbox and Production credentials are not interchangeable. Always ensure that your application uses the credentials that correspond to the selected environment. {% endhint %} {% hint style="info" %} Each Sandbox Shop has its own unique API credentials. Use them to authenticate your application with the Merchant API. If your merchant account contains multiple Sandbox Shops, each shop has a separate API Client ID and API Client Secret. Always use the credentials that belong to the Sandbox Shop processing the API requests. Sandbox API credentials are generated separately from Production credentials and are unique to each environment. {% endhint %} *** ### Accessing Sandbox API Credentials To access your Sandbox API credentials: 1. Navigate to **Settings → Shop Settings**. 2. Select the required Sandbox Shop. 3. Open the **Technical Information** section. The **Technical Information** page displays: * Home URL * Callback URL * Payment Authorization Type * Payment Capture Delay * API Client ID * API Client Secret
*** ### API Credentials The following credentials are available for each Sandbox Shop. | Credential | Description | | --------------------- | ----------------------------------------------------------------------------- | | **API Client ID** | Unique identifier used when requesting an OAuth access token. | | **API Client Secret** | Secret key used together with the Client ID to authenticate your application. | From this page you can: * Copy the **API Client ID**. * Reveal or hide the **API Client Secret**. * Copy the **API Client Secret**. * Regenerate the **API Client Secret** if required. These credentials are used to authenticate: * Merchant API * API SDKs * Web Plugins *** ### Updating Technical Information To modify the technical configuration of your Sandbox Shop: 1. Navigate to **Settings → Shop Settings**. 2. Select the required Sandbox Shop. 3. Click **Edit Agreement**. 4. Open the **Technical Information** section. From here you can update: * Home URL * Callback URL * Payment Authorization Type * Payment Capture Delay After making your changes, click **Submit for Approval**. Configuration changes submitted for Sandbox Shops are approved automatically and become available immediately.
{% hint style="info" %} Regenerating the **API Client Secret** invalidates the previous secret. Update your application configuration before making additional API requests. {% endhint %} *** ## Environment Indicator The currently selected environment is always displayed at the top of the **Merchant Portal**. When working in **Sandbox Mode**, an orange notification banner is displayed in the portal header indicating that you are using the Sandbox environment. This banner provides a visual reminder that all actions are performed in the Sandbox environment using test data.
{% hint style="info" %} Before generating API credentials, configuring shops, or reviewing transactions, always verify that you are working in the intended mode. {% endhint %} *** ## Merchant Portal Features in Sandbox Mode Sandbox Mode allows you to validate not only your payment integration but also your operational workflows using simulated transaction data. The same Merchant Portal functionality is available in both Sandbox Mode and Production Mode. The difference is that Sandbox uses test data and simulated transactions, while Production processes live customer payments. *** ### Dashboard The [**Dashboard**](/guides/merchant-portal/monitor-your-business/dashboard.md) provides an overview of your Sandbox activity using simulated transaction data. Depending on the services enabled for your merchant account, the Dashboard may display transaction volumes, approval rates, payment method statistics, refund ratios, and other operational metrics. Dashboard values in Sandbox are generated from test transactions and should be used only for validating reporting and merchant workflows. *** ### Orders The [**Orders**](/guides/merchant-portal/monitor-your-business/orders.md) page displays transactions processed in **Sandbox Mode** and allows you to search, review, and validate payment and order information generated during testing. To access Sandbox orders, navigate to: **Orders** Use the Orders page to: * Search for test transactions using the available search criteria and filters. * Review transaction, payment, customer, and order details. * Verify payment statuses. * Review payment methods and masked payment information. * Find the **Payment ID** for integration validation or troubleshooting. * Review refunds and available payment operations, where applicable. * Download individual order information. * Export order search results to a CSV file, where available.
*** #### **Search and Filter Orders** Use the search and filtering options to locate a specific transaction or narrow the list of displayed Sandbox orders. The main Orders view allows you to filter by: * **Date from / Date to** – Select the period in which the transaction was created. * **Shop** – Select a specific Sandbox Shop or an available multi-shop view. * **Last 4 digits of card / IBAN** – Search using the available masked card or bank account information. Select the **Filter** icon to access additional search criteria. Available filters include: * **Order No** * **Invoice No** * **Status** * **Payment method** * **Fraudulent transactions** * **Amount range** * **Customer full name** * **Customer email** * **Payment Link ID** You can combine multiple criteria to narrow the search results. After entering the required criteria, select **Apply filters**, then **Apply** to update the Orders list. Select **Clear** to remove the applied search criteria and return to the default Orders view. {% hint style="info" %} When investigating a transaction, use the most specific information available. Combining an **Order No**, date range, shop, customer information, Payment Link ID, or masked card/account information can help locate the required transaction more quickly. {% endhint %} *** #### **Reviewing an Order** Select an order from the Orders list to open its details. The order details provide information about the transaction and its current payment status. Depending on the payment method, integration method, and information supplied when the payment was created, the order details may include: * Order number * Creation date and time * Current payment status * Channel * Shop * Purchased items and quantities * Customer name * Customer email * Customer phone number * Payment method * Masked card or account information * Payment ID * Payment date * Order amount and currency * Shipping, taxes, discounts, and other applicable amounts * Total amount * Amount paid by the customer * Refund information, where applicable The information available for individual orders may differ depending on the payment method and the data provided during payment creation. *** #### **Payment ID** The **Payment ID** uniquely identifies the payment within the SEB Ecommerce Payment Gateway. We recommend storing the Payment ID together with your own order reference. Use the Payment ID when: * Matching payments with your merchant orders. * Validating Sandbox test results. * Investigating payment-processing issues. * Reviewing payment information through the applicable API. * Contacting SEB Support about a specific payment. {% hint style="info" %} When contacting SEB Support about a payment, provide the **Payment ID** together with the relevant timestamp and other available transaction information. This helps identify the transaction more efficiently. {% endhint %} *** #### **Refunds** Where applicable, open the **Refunds** tab in the order details to review refund information associated with the selected payment. The available refund information depends on the payment status, payment method, and refund operations already performed. *** #### **Payment Operations** Where supported, the **Actions** menu provides the payment operations currently available for the selected transaction. The available actions depend on: * Current payment status. * Payment method. * Shop configuration. * Services enabled for the shop. * Your Merchant Portal permissions. Depending on the transaction, available operations may include actions such as **capture, cancellation, or refund**. Only operations applicable to the selected transaction are displayed. *** #### **Download Orders** Where available, use **Download** to export transaction information from the Orders page. You can download order information or export the current search results to a **CSV file** for further review. {% hint style="info" %} Downloaded Sandbox information is intended for testing and validation only. {% endhint %} {% hint style="warning" %} Sandbox orders contain **test transactions only**. They do not represent live customer payments, settlements, accounting records, or financial reporting. Do not use Sandbox order exports for Production reconciliation or financial reporting. {% endhint %} *** ### Payment Links The **Payment Links** section allows you to create and manage payment links and QR codes in Sandbox Mode without implementing your own checkout integration. Use Payment Links to: * Create payment links for test payments. * Generate QR codes for customer payment journeys. * Create single or bulk payment requests, where supported. * Use saved payment link templates. * Test invoice payment scenarios. * Configure additional checkout fields displayed to customers. * Search and review previously created payment links. * Download payment link information, where available.
Payment Links are created for a specific **Sandbox Shop**. When reviewing existing links, you can select a specific shop or use the available shop filters to view links across multiple shops. {% hint style="info" %} Payment Links created in **Sandbox Mode** process test transactions only. They do not create live customer payments or transfer real funds. {% endhint %} For detailed information about creating and managing payment links, QR codes, invoices, and additional fields, see [**Payment Links**.](/guides/merchant-portal/accept-payments-without-integration/payment-links-and-qr-codes.md) *** ### My Requests The **My Requests** page allows you to monitor requests submitted through the Merchant Portal. Use this page to review the status of requests such as: * Sandbox Shop creation * Shop configuration changes * Other merchant configuration requests {% hint style="info" %} Requests submitted for Sandbox Shops are approved automatically. Requests related to Production services may require review and approval by SEB. {% endhint %} *** ### Demo Store The **Demo Store** allows you to explore the **Hosted Checkout** customer payment journey without integrating your own application. The Demo Store simulates an ecommerce store where you can select demonstration products, create an order, proceed to Hosted Checkout, and complete a test payment using the payment methods enabled for the selected Sandbox Shop. Use the Demo Store to: * Explore the customer journey from product selection to payment completion. * Select the Sandbox Shop you want to test. * Test the payment methods enabled for the selected Sandbox Shop. * Experience the Hosted Checkout payment flow. * Test different payment scenarios using the values provided in [**Test Data**](/guides/sandbox/test-data.md). * Review the resulting test transactions in **Merchant Portal → Orders**. {% hint style="info" %} The Demo Store is available in **Sandbox Mode only**. When the Merchant Portal is in **Live Mode**, the Demo Store is not displayed in the navigation menu. {% endhint %}
{% hint style="warning" %} **Demo Store is for demonstration and testing only.** * All products, descriptions, prices, images, customer information, and other store content are fictitious. * All payment transactions are simulated and do not represent live customer payments. * No real customer funds are transferred. * No clearing, settlement, accounting records, or financial reporting are generated. * During checkout, use only the test cards, test accounts, and other values provided in [**Test Data**.](/guides/sandbox/test-data.md) * Do not enter real customer information, real payment data, or Production credentials. {% endhint %} The Demo Store is intended to help you understand and explore the SEB-provided Hosted Checkout experience. It does not replace end-to-end testing of your own integration. *** ### Customize Checkout The **Customize Checkout** section allows you to configure and preview the appearance and payment method presentation of the [**Hosted Checkout** ](/integration/hosted-checkout.md)page for each Sandbox Shop. To access checkout customization, navigate to: **Settings → Customize Checkout** Checkout customization is configured **individually for each shop**, allowing you to create and test different checkout experiences for different shops or business needs. Use **Customize Checkout** to configure and validate: * Shop icon and merchant logo * Font * Primary and secondary colours * Colour palette and accessibility contrast * Button shape * Product placeholder icons * Payment method presentation and grouping * Payment method prioritization * Desktop and mobile checkout experience *** **Customize the Appearance** You can adjust the visual appearance of Hosted Checkout to better align it with your merchant branding. Available customization options include: * **Shop icon** – Select the icon used to represent your shop. * **Merchant logo** – Upload your shop or merchant logo. * **Font** – Select the font used in Hosted Checkout. * **Primary colour** – Configure the primary colour used for applicable checkout elements. * **Secondary colour** – Configure the secondary colour used for applicable checkout elements. * **Colour palette** – Review the resulting colour palette. * **Button shape** – Select the preferred button style. * **Placeholder icons** – Select the placeholder used for products where no product image is available. The available customization options may evolve as additional Hosted Checkout functionality is introduced. *** **Accessibility and Colour Contrast** When configuring checkout colours, the Merchant Portal validates applicable colour selections against accessibility contrast requirements. If a selected colour does not provide sufficient contrast, a warning is displayed. Select a darker or otherwise suitable colour before saving the configuration. {% hint style="warning" %} Choose colours that meet the accessibility requirements indicated by the Merchant Portal. Insufficient colour contrast may reduce the readability and accessibility of the Hosted Checkout experience. {% endhint %} *** **Payment Method Presentation** You can configure how the payment methods enabled for the selected shop are presented to customers. Available presentation options include: **No Grouping**\ Displays available payment methods in a single list without prioritization. This can be suitable when only a small number of payment methods are offered or when all methods should have equal visibility. **Group by Type**\ Groups available payment methods into categories to simplify navigation when multiple payment options are available. **Highlight First Payment Method**\ Prioritizes a selected payment method while keeping alternative payment methods available. If the prioritized method is unavailable, the checkout can present another available option. **Highlight Methods Previously Used by User**\ Prioritizes payment methods previously used by the customer, where supported, to simplify repeat payment journeys. The payment methods available for configuration are determined by the services and payment methods enabled for the selected shop. {% hint style="info" %} Some branded payment elements, including **Apple Pay**, **Google Pay**, **Click to Pay**, and other scheme- or wallet-branded payment buttons, are displayed according to the branding and user-interface requirements of their respective providers. These branded elements cannot be independently restyled by the merchant. {% endhint %} *** **Preview Your Checkout** The checkout preview allows you to review the customer experience while configuring your Sandbox Shop. You can switch between **desktop** and **mobile** previews to verify how the checkout will appear on different device types. The preview updates as you change the configuration, allowing you to immediately review: * Branding and colours * Fonts and button styles * Product presentation * Order information * Payment method presentation * Overall checkout layout The preview allows you to evaluate the customer-facing experience without processing a transaction. When you are satisfied with the configuration and no required validation issues remain, select **Save changes** to apply the configuration to the selected Sandbox Shop. *** **Shop and Environment Configuration** Hosted Checkout customization is **shop-specific and environment-specific**. Changes saved in Sandbox Mode apply only to the **selected Sandbox Shop**. If you manage multiple Sandbox Shops, select the correct shop before changing its checkout configuration. {% hint style="warning" %} Changes made to a Sandbox Shop do **not** automatically apply to the corresponding Production Shop. Before processing live transactions, review and configure the Hosted Checkout settings for your Production Shop separately. {% endhint %} *** ### User Management The **User Management** section allows merchant administrators to manage access to the **SEB Merchant Portal**. The availability of this functionality depends on your merchant agreement with SEB. If **User Management** is enabled, you can: * Invite new users to the Merchant Portal. * Manage user roles and permissions. * Review existing users. * Control access to Merchant Portal functionality. User invitations can be sent only to users belonging to the email domain(s) permitted by your merchant agreement. If **User Management** is not enabled for your merchant account, user administration is performed by SEB. In this case, requests to create, modify, or remove users should be submitted through SEB using the agreed support process. {% hint style="info" %} User permissions determine which Merchant Portal features and functions are available to each user in both **Sandbox Mode** and **Production Mode**. {% endhint %} *** ## Before You Continue Before continuing with integration testing, ensure that: * The correct **Sandbox Shop** is selected. * Your **Home URL** and **Callback URL** have been configured. * Your application uses the **API Client ID** and **API Client Secret** for the selected Sandbox Shop. * The required payment methods have been enabled for your Sandbox Shop. * You understand that Sandbox and Production use separate data, credentials, and configuration. You are now ready to begin testing your integration using the Sandbox environment. Continue with: * [**Test Data**](/guides/sandbox/test-data.md) – Test cards, test banks, credentials, and other test values. * [**Test Scenarios**](/guides/sandbox/test-scenarios.md) – Recommended payment scenarios to validate before requesting Production activation. --- # 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/using-sandbox-mode.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.