> 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/readme.md).
# Thales D1 Platform
## Thales D1 Platform
Thales D1 is a cloud-native platform empowering you with modern and instant card issuance. Whether you're a bank, fintech, digital wallet provider, or transit operator, Thales D1 makes it easy to deliver real-time and digital-first experiences to your customers. Built on token-centric principles and modular managed services, Thales D1 ensures fast deployment through seamless API integration: keeping you agile in a rapidly evolving digital world
Learn more
{% columns %}
{% column %}
{% endcolumn %}
{% column %}
{% endcolumn %}
{% endcolumns %}
{% columns %}
{% column width="33.33333333333333%" valign="middle" %}
{% endcolumn %}
{% column width="66.66666666666667%" valign="middle" %}
### Connect once, and enable new services easily
Adapt your roadmap with 10+ modular, ready-to-deploy use cases
{% endcolumn %}
{% endcolumns %}
{% columns %}
{% column %}
{% endcolumn %}
{% column %}
{% endcolumn %}
{% endcolumns %}
{% columns %}
{% column width="66.66666666666666%" valign="middle" %}
Faster Time to Market
Launch new payment services faster with a simple API framework
---
# 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/readme.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.
