> 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.md). # Test Scenarios Validate your payment integration and customer payment journeys in **Sandbox Mode** before processing live transactions. Use this test plan to verify that your application correctly handles the payment methods and payment scenarios relevant to your integration. Run only the scenarios applicable to the payment methods and functionality enabled for your Sandbox Shop. Use the test cards, test banks, and other values provided in [**Test Data**](/guides/sandbox/test-data.md). {% hint style="info" %} The payment status returned by the SEB Ecommerce Payment Gateway is the source of truth for the payment outcome. Do not fulfil an order based only on the customer returning to your website. {% endhint %} *** ### Before You Start Before running test scenarios: * Select the correct Sandbox Shop. * Verify that the required payment methods are enabled. * Configure the appropriate Sandbox endpoint and API credentials for your integration. * Configure your **Home URL** and **Callback URL**, where applicable. * Use only the test values provided in **Test Data**. * Ensure your application can receive and process payment status updates. For Sandbox configuration, see [**Using Sandbox Mode**](/guides/sandbox/using-sandbox-mode.md). *** ### What Should You Test? The scenarios you should validate depend on the payment methods, integration approach, and functionality enabled for your Sandbox Shop. Use the following matrix as a guide. Test only the scenarios applicable to your configuration.
ScenarioCardsPay by BankApple PayGoogle PayClick to Pay
Successful payment✓✓✓✓✓
Failed payment✓✓Where applicable✓✓
Customer cancellation✓✓✓✓✓
Customer abandonment✓✓✓✓✓
AuthenticationEMV 3DSBank authenticationWalletWallet / 3DSClick to Pay
Payment status verification✓✓✓✓✓
Callback handling✓✓✓✓✓
Retry after failure✓✓✓✓✓
Refund✓Where enabled✓✓✓
Authorization & captureWhere configured—Where applicableWhere applicableWhere applicable
{% hint style="info" %} The exact scenarios available in Sandbox depend on the payment methods, services, and configuration enabled for your Sandbox Shop. {% endhint %} *** ### Test Execution For each test scenario: 1. Initiate the payment using your selected integration method. 2. Complete the customer payment journey using the required test data. 3. Record the **Payment ID** or other applicable payment reference. 4. Verify the final payment status returned by the gateway. 5. Confirm that your application updates the corresponding order correctly. 6. Verify the transaction in **Merchant Portal → Orders**. 7. Retain the Payment ID and expected result with your test evidence. {% hint style="info" %} Sandbox transactions are simulated. Test results validate your integration against predefined Sandbox behaviour and do not represent actual issuer, bank, card scheme, or external payment provider behaviour. {% 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/test-scenarios.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.