> 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/release-notes/es/backend/october-2025/oct-27.md).

# 27 oct.

| Entorno       | Fecha       |
| ------------- | ----------- |
| Preproducción | 27 oct 2025 |
| Producción    | 27 oct 2025 |

Esta versión hace `billingAddress` opcional para Mastercard Click to Pay en APIs específicas. También añade una API para actualizar una solicitud existente de producción de tarjeta física.

### Pagar con un clic

#### Mejoras

* Hacer `billingAddress` opcional para Mastercard en:
  * [Inscripción en Click to Pay](https://thales-dis-dbp.stoplight.io/docs/d1-caas/4ccb39ece8626-click-to-pay-enrol)
  * [Obtener perfiles de consumidores de Click to Pay](https://thales-dis-dbp.stoplight.io/docs/d1-caas/bc98fe23ebdb6-click-to-pay-get-consumer-profiles)
* Mantenga la validación de Visa sin cambios.
* Confirme los subcampos requeridos de Mastercard con su equipo local de Mastercard durante el inicio del proyecto.

### Emisión física

#### Nuevas funciones

* Añadir un [Pull & Change](https://docs.payments.thalescloud.io/central-issuance/es/integrar-la-api-de-d1/referencia-de-la-api-de-d1/api-entrante-a-d1/api-de-pedido-de-tarjeta.md#post-issuers-issuerid-physicalcards-cardid-operations-updateorder) API para actualizar una solicitud existente de producción de tarjeta física.
  * Soporte `CANCELAR`, `ACELERAR`, `REDIRIGIR`y `ACELERAR_Y_REDIGIR` tipos de actualización.
  * Enviar notificaciones de actualización a través de la [API de Notificar Operaciones de Tarjeta](https://docs.payments.thalescloud.io/central-issuance/es/integrar-la-api-de-d1/referencia-de-la-api-de-d1/api-saliente-desde-d1/api-de-tarjeta.md#post-notifications-d1-v2-issuers-issuerid-cards) usando la `UPDATE_ORDER` operación.


---

# 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/release-notes/es/backend/october-2025/oct-27.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.
