> For the complete documentation index, see [llms.txt](https://doc.api.tieto.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.api.tieto.com/features/sandbox.md). # Sandbox Third-party providers (TPPs) can validate integrations before connecting to production APIs. The platform provides two sandbox environments for registered TPPs: * **Dynamic sandbox** for regulatory and compliance APIs. * **Static sandbox** for premium and aggregation services. ### Premium APIs sandbox The Premium APIs sandbox supports testing of non-regulatory API products. It exposes the same APIs as the production environment while returning predefined static responses. Responses are configurable to model the test cases needed for your integration. The environment is available continuously for bank-service testing. The Platform makes every newly published API available in sandbox automatically. ### PSD2 APIs sandbox The PSD2 sandbox in the Developer Portal supports regulatory API testing. It includes: * Account Information Services * Payment Initiation Services * Funds Confirmation Services Live QWAC and QSealC certificates are not required. Use test regulatory certificates that can downloaded on Developer Portal. The sandbox provides simulated data for two Payment Service Users (PSUs). This includes account information, PSU identifiers, login credentials, account numbers, currencies, and available balances. TPPs can use these consistent datasets to validate account access, payment initiation, and error-handling flows without using customer data or affecting live accounts. This makes integration testing repeatable and enables teams to resolve issues before production onboarding. #### Test Strong Customer Authentication Strong Customer Authentication (SCA) is simulated through a dedicated bank authentication mock screen. Enter the supplied PSU username and password to complete the flow and validate the user experience. --- # 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://doc.api.tieto.com/features/sandbox.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.