> 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-data.md). # Test Data ## Test Data The **Sandbox** environment provides dedicated test data for validating your integration with the **SEB Ecommerce Payment Gateway**. Use only the test data documented on this page when developing, integrating, and validating your solution. {% hint style="warning" %} The Sandbox environment is intended exclusively for development, integration testing, and validation purposes. * All payment transactions are simulated. * No real payment authorizations are sent to card schemes, banks, or external payment networks. * No real customer funds are transferred. * No financial settlements, clearing, or accounting records are generated. * Payment responses are returned according to predefined Sandbox scenarios and business rules. * Always use the test cards, test bank accounts, and other test data provided by SEB. * Do not use real customer or payment information in the Sandbox environment. {% endhint %} *** ## Test Data Overview Depending on the services enabled for your Sandbox Shop, test data may be available for: * Payment Cards * Pay by Bank * Apple Pay * Google Pay * Payment Links * Hosted Checkout * Unified Merchant API The available payment methods and test scenarios depend on your merchant agreement and the services enabled for your Sandbox environment. *** ## Sandbox API Credentials Each **Sandbox Shop** has its own unique API credentials. If your merchant account contains multiple Sandbox Shops, every shop has its own: * API Client ID * API Client Secret Always use the credentials assigned to the Sandbox Shop processing your API requests. Sandbox API credentials are generated separately from Production credentials. For more information, see [Using Sandbox Mode](/guides/sandbox/using-sandbox-mode.md) *** ## Payment Cards Use the following Sandbox payment cards to validate your card payment integration. {% hint style="warning" %} These card numbers are intended for **Sandbox Mode only**. They do not represent real payment cards and cannot be used in the Production environment. {% endhint %} Unless otherwise specified: * **Expiry Date:** Any future date * **CVV/CVC:** Any valid 3-digit value * **Cardholder Name:** Any value ### Visa | Card Number | Expected Result | | ------------------ | ------------------------ | | `4622943123144639` | Successful authorization | | `4622943123144647` | Authorization declined | ### Mastercard | Card Number | Expected Result | | ------------------ | ------------------------ | | `5355330000000009` | Successful authorization | | `5148360000000007` | Authorization declined | Use the test cards above to validate: * Successful payments * Failed authorizations * Callback processing * Order status updates Additional scenarios, including EMV® 3-D Secure authentication, captures, reversals, and refunds, are described in [**Test Scenarios**](/guides/sandbox/test-scenarios.md). *** ## Pay by Bank Pay by Bank uses aggregation functionality to connect to target banks. The Sandbox test bank accounts and credentials are provided by the connected banks themselves. In Sandbox mode, Pay by Bank connects to the remote banks sandboxes. Supported Pay by Bank scenarios include: * Successful payments * Failed payments * Customer cancellations * Authentication failures * Refunds (only SEB) Use the Sandbox test bank accounts and credentials to validate Open Banking payment flows.
Swedbank Baltics PSU authentication method: `Smart-ID` PSU credentials: * User ID: `111111` * Personal code: `111111-11111`
SEB Baltics PSU authentication method: `Smart-ID` PSU credentials: * User ID: `ibsUser1`
*** ## Apple Pay Where Apple Pay is enabled for your Sandbox Shop, use the supported Sandbox wallet and test payment methods provided by Apple and SEB. Apple Pay is fully emulated in the Sandbox environment. During checkout, a simulated Apple Pay payment sheet is displayed, allowing you to test your integration using the sandbox test cards without interacting with the live Apple Pay platform. The sandbox experience supports the following test scenarios: * **Apple Pay Checkout** – Complete payments using sandbox test cards enrolled in Apple Pay profile. *** ## Google Pay Where Google Pay is enabled for your Sandbox Shop, use the supported Sandbox wallet and test payment methods provided by SEB. Google Pay is fully emulated in the Sandbox environment. During checkout, a simulated Google Pay payment sheet is displayed, allowing you to test your integration using the sandbox test cards without interacting with the live Google Pay platform. The sandbox payment sheet supports the following test scenarios: * **Stored Card** – Simulates a Google Pay payment using a card stored in the customer's Google Wallet. * **Device Token** – Simulates a Google Pay payment using a tokenized card provisioned to a device. *** ## Click to Pay Where Click to Pay is enabled for your Sandbox Shop, use the supported Sandbox wallet and test payment methods provided by SEB. Click to Pay is fully emulated in the Sandbox environment. Customer registration, card enrollment, and checkout processing are performed entirely within the sandbox and do not interact with the live Click to Pay ecosystem. The sandbox experience supports the following test scenarios: * **Click to Pay Registration** – Create a sandbox Click to Pay profile during checkout. * **Card Enrollment** – Add and manage supported sandbox test cards within your Click to Pay profile. * **Click to Pay Checkout** – Complete payments using cards enrolled in the sandbox Click to Pay profile. *** ## Common Test Values Depending on your integration, you may also require: * Sandbox API endpoint * OAuth authentication * Shop ID * Merchant ID * Callback URL * Home URL Refer to the relevant integration documentation for implementation details. *** {% hint style="warning" %} * Always use Sandbox credentials together with Sandbox endpoints. * Each Sandbox Shop has its own API credentials. * Sandbox and Production credentials are not interchangeable. * Use only the test cards, test bank accounts, and other test data provided by SEB. * Do not enter real customer information into the Sandbox environment. * Test transactions do not generate financial settlements, accounting records, or live customer payments. Additional test payment methods or test scenarios may be enabled for your Sandbox environment by SEB for evaluation or project-specific purposes. Availability depends on your merchant agreement. {% 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-data.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.