> For the complete documentation index, see [llms.txt](https://docs.payments.thalescloud.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.payments.thalescloud.io/secure-card-display/es/integrate-d1-sdk/get-started/mobile-sdk-sandbox.md).

# Entorno de pruebas del SDK móvil

Our issuers have the possibility to use the mobile SDK sandbox for tests during development of their issuer application.

This is typically needed during the early integration phase before PreProd / Production Environment gets ready.

Mobile SDK sandbox allows you to perform D1 API calls using D1 SDK services in order to fine-tune the Application UI/UX in case you are using one of our Secure Card Display or NFC Payment use cases.

## Configuration

In order to use Thales Sample Application please contact to your Thales representative in order to provide complete set of [**configuration parameters**](https://github.com/ThalesGroup/dp-d1-sample-android#configuration) and test **card data** to allow your connectivity towards Mobile SDK Sandbox.

## Supported use cases

* Login
* NFC Payment service
* Secure Card Display service
* Physical Issuance service


---

# 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.payments.thalescloud.io/secure-card-display/es/integrate-d1-sdk/get-started/mobile-sdk-sandbox.md?ask=<question>&goal=<user_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.