> 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/test-scenarios/demo-store-and-hosted-checkout.md). # Demo Store & Hosted Checkout Explore the SEB-provided customer payment journey before or alongside testing your own integration. The **Demo Store** provides a ready-to-use demonstration environment for exploring the **Hosted Checkout** customer journey in Sandbox Mode. You can use the Demo Store without implementing your own checkout integration. It allows you to create a sample order, continue to Hosted Checkout, select an enabled payment method, complete a simulated payment, and review the resulting transaction in the Merchant Portal. The Demo Store is useful for becoming familiar with the customer payment experience before implementing or validating your own integration. {% hint style="info" %} The Demo Store is provided for demonstration and testing purposes only. All products, descriptions, prices, customer information, and transactions used in the Demo Store are test data and do not represent real commercial activity. Always use the test payment data provided in [**Test Data**.](/guides/sandbox/test-data.md) Do not enter real customer or payment information. {% endhint %} *** ### What You Can Explore Using the Demo Store, you can explore the complete Hosted Checkout journey: 1. Select one or more demonstration products. 2. Review the shopping cart. 3. Proceed to checkout. 4. Enter test customer information. 5. Continue to Hosted Checkout. 6. Select an available payment method. 7. Complete or cancel the payment. 8. Review the payment result. 9. Return to the Demo Store. 10. Locate the resulting transaction in **Merchant Portal → Orders**. {% hint style="info" %} The payment methods available in the Demo Store depend on the payment methods and services enabled for the selected Sandbox Shop. {% endhint %} *** ### Recommended Demo Store Scenarios You do not need to validate every Demo Store function. The Demo Store itself is maintained and tested by SEB. Instead, use it to become familiar with the main customer journeys relevant to your integration. #### Successful Card Payment Complete a card payment using a successful Visa or Mastercard test card. Verify that you can: * Select Card as the payment method. * Enter the test card details. * Complete the EMV® 3-D Secure authentication flow. * View the successful payment confirmation. * Obtain the Payment ID. * Find the transaction in **Merchant Portal → Orders**. Use the applicable card values from [**Test Data**.](/guides/sandbox/test-data.md) *** #### Failed Card Payment Use a [card ](/guides/sandbox/test-data.md#payment-cards)configured to return an unsuccessful authorization. Observe how Hosted Checkout handles the unsuccessful payment and allows the customer to retry or select another payment method. *** #### 3-D Secure Cancellation Start a Card payment and cancel the authentication flow. Observe: * The customer-facing payment result. * The ability to retry the payment. * The resulting payment status. *** #### Pay by Bank Where Pay by Bank is enabled: 1. Select **Bank Account**. 2. Select the required country or region. 3. Select an available test bank. 4. Complete the simulated bank authentication and authorization journey. 5. Return to Hosted Checkout. 6. Review the resulting payment. The authentication journey may differ depending on the selected bank, for examples and description see [payer SCA flows](/guides/sandbox/test-scenarios/demo-store-and-hosted-checkout/pay-by-bank-payer-authentication-sca.md). *** #### Apple Pay Where Apple Pay is enabled and your test environment meets the applicable Apple Pay requirements: * Select Apple Pay. * Complete the Sandbox wallet journey. * Review the payment result. * Locate the resulting transaction in Merchant Portal. *** #### Google Pay Where Google Pay is enabled: * Select Google Pay. * Complete a successful test payment. * Explore an unsuccessful or cancelled payment where supported. * Review the resulting transaction in Merchant Portal. *** #### Click to Pay Where Click to Pay is enabled, use the Demo Store to explore: * Customer recognition and sign-in. * Customer verification. * Selection of a stored card. * Successful payment. * Switching to manual card entry. *** #### Customer Cancellation Start a payment and return to the Demo Store without completing it. Use this scenario to understand how Hosted Checkout presents a cancelled or incomplete customer journey. *** #### Return to Merchant After completing a payment, use **Return to Merchant** or allow the automatic return to complete. {% hint style="info" %} The browser return is part of the customer journey and must not be used as the source of truth for payment fulfilment. Your own integration should rely on the confirmed gateway payment status and callback processing. {% endhint %} *** ### Verify the Transaction in Merchant Portal After completing a Demo Store payment: 1. Open **Merchant Portal** in Sandbox Mode. 2. Navigate to **Orders**. 3. Locate the transaction using the Payment ID or other available search criteria. 4. Review the payment method, amount, and payment status. This allows you to see how transactions generated through Hosted Checkout are represented in the Merchant Portal. *** ### What You Do Not Need to Test You are not expected to perform functional or regression testing of the Demo Store itself. For example, you do not need to validate: * Shopping cart controls. * Product quantity calculations. * Coupon calculations. * Demo product information. * Form layout or UI controls. * Demo Store responsive behaviour. * Internal field validation. {% hint style="info" %} These functions are part of the SEB-provided demonstration environment and are not part of your integration acceptance testing. {% endhint %} *** ### Demo Store vs. Your Integration Successful testing in the Demo Store confirms that you can explore the Sandbox Hosted Checkout journey and the enabled payment methods. It does **not** validate your own integration. Before processing live transactions, you should separately validate your application's: * Payment initiation. * Callback processing. * Payment status handling. * Failed and cancelled payment handling. * Retry and idempotency logic. * Refund processing, where applicable. Continue with **Test Scenarios** to validate your own integration. --- # 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/test-scenarios/demo-store-and-hosted-checkout.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.