> 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/instant-issuance/instant-issuance-es/implementar-la-emision-por-socios/solicitar-una-tarjeta-fisica.md).

# Solicitar una tarjeta física

## Prerrequisitos

* Incorporación a D1 completada.
* Programa/BIN, productos y plantillas de personalización configurados.
* El backend del emisor integrado con la API de emisión física y capaz de recibir notificaciones de la API de tarjetas.

{% hint style="info" %}
La emisión central produce y envía tarjetas desde un centro de personalización Thales. A diferencia de la emisión instantánea, no utiliza el Agente de Emisión Instantánea de Thales y no proporciona un `persoStation`.
{% endhint %}

## Diagrama de flujo

<figure><img src="https://content.gitbook.com/content/1qJ8OQRIA2FuYOSRgnR2/blobs/JeaPAoy6klQIIC4D2WN9/Flow%20-%20Partner%20issuance.svg" alt=""><figcaption><p>Flujo de emisión central</p></figcaption></figure>

1. El backend del emisor envía una solicitud Produce physical card al backend D1 (API de emisión física).
2. El backend D1 prepara los datos de producción.
3. El backend D1 reenvía los datos de producción al centro de personalización Thales (Thales Shopfloor).
4. El centro de personalización Thales devuelve el estado de producción.
5. El backend D1 notifica al backend del emisor usando Notify card operations (API de tarjetas).

## Diagrama de secuencia

<figure><img src="https://content.gitbook.com/content/1qJ8OQRIA2FuYOSRgnR2/blobs/Bxt7dihJRrnQjxm3nypv/Sequence%20Diagram%20-%20%20Partner%20issuance.svg" alt=""><figcaption><p>Secuencia de emisión central</p></figcaption></figure>


---

# 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/instant-issuance/instant-issuance-es/implementar-la-emision-por-socios/solicitar-una-tarjeta-fisica.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.