> 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.md). # Merchant Portal Manage your shops, payment operations, transactions, and account configuration in the SEB Merchant Portal. ## Merchant Portal Overview The **SEB Merchant Portal** is your workspace for managing ecommerce payment operations, shops, and payment services provided through the **SEB Ecommerce Payment Gateway**. Use the Merchant Portal to monitor payment activity, review transactions, create payment requests, manage shop configuration, customize Hosted Checkout, and manage user access where enabled. The functionality available to you depends on: * Your Merchant Agreement with SEB. * Services enabled for your merchant account. * The selected shop. * Whether you are working in Sandbox Mode or Production Mode. * Your assigned user role and permissions. The Merchant Portal is available at: [**https://merchantportal.ecommerce.sebgroup.com**](https://merchantportal.ecommerce.sebgroup.com/) *** ### What You Can Do #### Dashboard Use the **Dashboard** to monitor payment activity and key operational indicators across your shops. Depending on the services and payment methods enabled for your merchant account, the Dashboard may provide information such as: * Processed payment volume. * Transaction counts. * Approval rates. * Refund indicators. * Payment method activity. * Other operational payment metrics. Use the available period and shop selectors to control which data is displayed. The Dashboard is intended for operational monitoring and does not replace settlement, reconciliation, or accounting records. See [**Dashboard**](/guides/merchant-portal/monitor-your-business/dashboard.md). *** #### Orders Use **Orders** to search for and review payments processed through the Payment Gateway. You can: * Search and filter transactions. * Review order and payment details. * Verify payment statuses. * Review customer information, where provided. * Find the Payment ID. * Review refunds and available payment operations. * Download order information or export search results, where available. See [**Orders**](/guides/merchant-portal/monitor-your-business/orders.md). *** #### Payment Links & QR Codes Use **Payment Links & QR Codes** to create payment requests without implementing your own checkout. Depending on the functionality enabled for your merchant account, you can: * Create payment links. * Generate QR codes. * Create reusable payment requests. * Use saved templates. * Search and manage existing payment links. * Download payment link information. See [**Payment Links**](/guides/merchant-portal/accept-payments-without-integration/payment-links-and-qr-codes.md). *** #### Invoices Use **Invoices** to create and manage invoice-based payment requests. Depending on the functionality enabled for your merchant account, invoices may be created individually or in bulk. You can monitor their status and associated payment activity directly from the Merchant Portal. See [**Invoices**](/guides/merchant-portal/accept-payments-without-integration/invoices.md). *** #### Additional Fields Use **Additional Fields** to define additional information that should be requested or displayed as part of supported payment journeys. The available options depend on the payment functionality enabled for your merchant account. See **Additional Fields**. *** #### Customize Checkout Use **Customize Checkout** to configure and preview the customer-facing appearance of Hosted Checkout for each shop. Depending on the available configuration, you can customize: * Shop icon and merchant logo. * Fonts. * Primary and secondary colours. * Button appearance. * Product placeholders. * Payment method presentation and grouping. Desktop and mobile previews allow you to review the customer experience before saving your changes. Checkout customization affects the presentation of Hosted Checkout. It does not change the underlying payment processing, authentication, or payment status logic. See [**Customize Checkout**](/guides/merchant-portal/customize-your-checkout.md). *** #### Shop Settings Use **Shop Settings** to review the configuration of the selected shop. Depending on your agreement and permissions, available information may include: * Shop details. * Payment methods and services. * Bank Payments. * Bank accounts. * Technical information. * API credentials. * Fees. * Limits. Some configuration can be changed directly. Changes to agreement-controlled settings, payment methods, or services may require review and approval by SEB. See [**Shop Settings**](/guides/merchant-portal/manage-your-account/update-your-business-and-shop-information.md). *** #### My Requests Use **My Requests** to monitor requests submitted through the Merchant Portal that require processing or approval. For example, My Requests may contain requests related to: * Shop creation. * Changes to agreement-controlled configuration. * Activation of additional payment methods or services. You can use this section to follow the current status of submitted requests. Where applicable, you will also receive an email when SEB approves or declines a request. *** #### User Management Where **User Management** is enabled for your merchant account, authorized merchant administrators can manage access to the Merchant Portal. Depending on their permissions, administrators can: * Review existing users. * Invite new users. * Manage roles and permissions. * Control access to Merchant Portal functionality. User invitations are limited to the email domain or domains permitted under your merchant agreement. If User Management is not enabled, user administration is handled by SEB according to the agreed process. See [**User Management**](/guides/merchant-portal/manage-your-account/user-management.md). *** ### Sandbox and Production Modes The Merchant Portal provides access to both **Sandbox Mode** and **Production Mode** through a single portal. #### Sandbox Mode Sandbox Mode is used for: * Development and integration testing. * Shop configuration. * Testing payment methods. * Testing payment operations. * Merchant training. * Exploring the Demo Store and Hosted Checkout. Sandbox transactions use test data and have no financial effect. #### Production Mode Production Mode is used for: * Production shop configuration. * Live payment processing. * Reviewing live transactions. * Managing Production payment services and credentials. Use the environment selector in the Merchant Portal header to switch between Sandbox and Production when Production access is available for your merchant account. {% hint style="warning" %} Always verify which environment you are working in before reviewing transactions, using API credentials, or changing shop configuration. Sandbox and Production use separate data, credentials, and configuration. Changes made in Sandbox do not automatically apply to Production. {% endhint %} *** ### Shop Selection If your merchant account contains multiple shops, use the **Shop selector** to control which shop or group of shops you are working with. Depending on the page, you may be able to: * Select a specific shop. * View all active shops. * View all available shops. * Search for a shop. When a specific shop is selected, shop-specific information and configuration are displayed. Supported pages such as the Dashboard may also provide aggregated information across multiple shops. *** ### Important Information #### Operational Data Information displayed in the Dashboard, Orders, Payment Links, and other Merchant Portal functions is provided to support day-to-day payment operations. {% hint style="info" %} Merchant Portal operational information does not replace official settlement, reconciliation, acquiring, or accounting records. For financial reconciliation, use the settlement reports, acquiring statements, or other official reconciliation information provided for your merchant account. {% endhint %} #### Feature Availability The Merchant Portal may look different for different merchants and users. The functionality available to you depends on: * Services included in your Merchant Agreement. * Payment methods and features enabled for your merchant account. * The selected shop. * The active environment. * Your assigned user role and permissions. If a feature described in this documentation is not visible in your Merchant Portal, it may not be enabled for your merchant account or your user may not have permission to access it. *** ### Frequently asked questions
Why can't I see a feature described in the documentation? The functionality available in the Merchant Portal depends on your Merchant Agreement, enabled services, shop configuration, and user permissions.
What is the difference between Sandbox and Live mode? Sandbox is used for testing and validation without processing real financial transactions. Live mode is used for production activity and real customer payments.
Why can't I access another shop? Access to shop data and Portal functions is controlled by your assigned permissions. Users only see the shops and functionality available to their role.
--- # 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.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.