> 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/getting-started/quickstart.md). # Quickstart Apply for ecommerce payments, integrate your checkout, and go live. ## Start Accepting Payments Online Set up payment acceptance in four steps. Prepare your store before applying. This helps shorten onboarding and integration. {% stepper %} {% step %} ### Apply for ecommerce payments [Complete the application](https://www.seb.lv/en/business/payment-collection/e-commerce#appform_ecommerce). Our team will review your request, assess your business, and prepare your merchant agreement. Before applying, make sure your store includes: To help speed up the onboarding process, ensure that your website or online store includes the following information: #### Business Information * Company name * Company registration number * Business address and country * Contact email address * Contact telephone number #### Products and Services * Clear description of the products or services offered * Product or service pricing and currency * Available payment methods #### Customer Information * Terms and Conditions * Privacy Policy * Delivery or service fulfilment information * Returns, cancellations, and refund policy * Warranty information (where applicable) * Customer support contact details, including business hours and time zone #### Checkout Requirements Before processing payments, ensure your website: * Clearly identify the merchant accepting the payment. * Display the payment methods accepted by your business. * Clearly describe the purchasing process. * Inform customers of any applicable shipping costs, taxes, or additional charges. * Operate under the website domain approved in your merchant agreement. * Complete the entire customer checkout journey on the approved website. {% hint style="warning" %} The checkout and payment process must be completed on the website specified in your merchant agreement with SEB. Redirecting customers to websites or sales channels that are not covered by the agreement is not permitted. {% endhint %} #### Payment Acceptance If your website displays the payment methods accepted by your business, use the [official payment brand assets](/payment-methods/payment-method-brand-assets.md) provided by the respective payment schemes or by SEB. Where applicable, clearly display the logos of supported payment methods, for example: * Visa * Mastercard * Apple Pay * Google Pay * Click to Pay * Pay by Bank When Strong Customer Authentication (SCA) is supported through **EMV® 3-D Secure**, use only official branding and trademarks provided by the respective payment schemes. {% hint style="info" %} Official payment method logos and brand assets are available here or the respective payment scheme brand guidelines. Always use the latest approved branding and do not modify payment method logos or trademarks. {% endhint %} {% endstep %} {% step %} ### Sign the agreement Review the offer provided by SEB and sign the **Merchant Agreement** online. Once your agreement has been completed and your Merchant Portal account is ready, you will receive an email containing an **account activation link** and instructions for accessing the **SEB Merchant Portal**. The Merchant Portal is available at: We recommend bookmarking this address for future access. {% hint style="info" %} **Existing merchants moving to the new Payment Gateway** If you are an existing SEB ecommerce merchant being migrated to the new **SEB Ecommerce Payment Gateway**, SEB will contact you as part of the merchant migration process. When your merchant account is prepared in the new Payment Gateway, you will receive an **invitation email**. Follow the link in the email to complete your registration and activate access to the SEB Merchant Portal. Your existing Merchant Agreement with SEB remains in effect unless SEB communicates otherwise. {% endhint %} The **SEB Merchant Portal** is a single portal that provides access to both **Sandbox Mode** and **Live Mode**. The functionality and services available to you depend on your merchant agreement and onboarding status. #### Merchant Portal Use the Merchant Portal to manage your shops and access the payment services and operational functionality enabled for your merchant account. Depending on your agreement and user permissions, you can use the Merchant Portal to: * Manage shop configuration. * Review orders and payment transactions. * Access technical information and API credentials. * Configure supported payment services. * Create Payment Links and QR codes. * Customize Hosted Checkout. * Manage Merchant Portal users, where enabled. #### Sandbox Mode After activating your Merchant Portal account and signing in for the first time, you will enter **Sandbox Mode by default**. Use Sandbox Mode to develop, configure, and validate your payment solution using test data. Depending on the services enabled for your Sandbox Shop, you can: * Create and configure Sandbox Shops. * Obtain Sandbox API credentials. * Develop and test your integration. * Test enabled payment methods. * Validate customer payment journeys. * Test callbacks and payment status handling. * Test supported payment operations. * Use the **Demo Store** to explore the Hosted Checkout payment journey. * Review test transactions in the Merchant Portal. {% hint style="info" %} Sandbox transactions are simulated. No live customer payments are processed and no real customer funds are transferred. For detailed instructions, see [**Using Sandbox Mode**.](/guides/sandbox/using-sandbox-mode.md) {% endhint %} #### Live Mode **Live Mode** is available through the same Merchant Portal when Live access has been enabled by SEB according to your merchant agreement and onboarding status. Use Production Mode to: * Manage your Production Shops. * Configure live payment services. * Obtain Production API credentials. * Review live transactions. * Process live customer payments. When Live Mode is available for your account, use the **environment selector** in the Merchant Portal header to switch between **Sandbox Mode** and **Live Mode.** {% hint style="warning" %} Testing and validation of your integration are your responsibility. Before processing live transactions, ensure that the payment methods, customer journeys, payment status handling, callbacks, order-management logic, and payment operations applicable to your solution have been tested according to your business requirements. {% endhint %} {% hint style="info" %} Sandbox and Live are separate modes. Shops, API credentials, configuration, and transaction data are managed independently and are not automatically shared between environments. {% endhint %} {% endstep %} {% step %} #### Test and Go Live Before processing live customer transactions, complete end-to-end testing in [**Sandbox Mode**](/guides/sandbox.md) and verify that your payment solution works according to your business requirements. #### Complete Your Testing Test all payment methods, customer journeys, and payment operations applicable to your integration. As a minimum, validate: * Successful and declined payments. * Customer cancellations and abandoned payment journeys. * Payment authentication, where applicable. * Callback or webhook processing. * Payment status and order status handling. * Payment amounts and currencies. * Customer return and redirect handling. * Refunds and partial refunds, where applicable. * Authorization, capture, and reversal, where applicable. * Retry and duplicate-processing handling. Use the [**Test Data**](/guides/sandbox/test-data.md) and [**Test Scenarios**](/guides/sandbox/test-scenarios.md) guides to complete your Sandbox validation. {% hint style="warning" %} Testing and validation of your integration are your responsibility. A successful customer return or checkout confirmation alone should not be used to determine whether an order has been paid. Always use the confirmed gateway payment status as the source of truth. {% endhint %} #### Prepare for Live When you have completed your Sandbox testing and are ready to process live transactions: 1. Confirm that **Live Mode** is available for your merchant account. If Production access is not yet enabled, follow the agreed SEB process to request activation. 2. Switch to **Live Mode** using the environment selector in the Merchant Portal. 3. Review your Live Shop configuration. 4. Obtain the API credentials for your Production Shop. 5. Configure your application to use the Production endpoints and credentials. 6. Verify your Production **Home URL** and **Callback URL**. 7. Configure the payment methods and services required for Live. 8. Review your Hosted Checkout customization, where applicable. {% hint style="info" %} Sandbox and Live are separate environments. Sandbox credentials, shops, configuration, and transaction data are not automatically transferred to Production. {% endhint %} #### After Going Live Closely monitor your first live transactions. Verify that: * Payments reach the expected final statuses. * Callback or webhook notifications are processed correctly. * Orders are updated correctly in your system. * Payment amounts and currencies match your orders. * Transactions can be located in **Merchant Portal → Orders**. * Refunds and other operational processes work as expected. Continue monitoring and reconciling payments as part of your regular operational processes. {% endstep %} {% endstepper %} --- # 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/getting-started/quickstart.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.