> 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/nfc-wallet/es/general/interfaces.md).

# Canales de comunicación del SDK

NFC Wallet utiliza canales de comunicación dedicados entre el SDK de NFC Wallet que se ejecuta en la aplicación de billetera digital y el backend de NFC Wallet.

NFC Wallet admite dos canales de comunicación, ambos totalmente gestionados por el producto:

* **API de Wallet** – APIs utilizadas por el SDK de NFC Wallet para casos de uso como:
  * Inicialización del SDK con Wallet Secure Enrollment
  * Inicio de la inscripción de la tarjeta
  * Recuperación del historial de transacciones
* **Canal seguro** – Un canal de comunicación seguro utilizado para aprovisionar activos sensibles, como el perfil de la tarjeta digital y las claves de pago.

Para admitir casos de uso como eventos de gestión del ciclo de vida (LCM) de la tarjeta digital iniciados por el backend del emisor o el TSP, y notificaciones de transacciones, NFC Wallet también requiere notificaciones push silenciosas.

El backend de NFC Wallet utiliza [Firebase Cloud Messaging (FCM)](https://firebase.google.com/docs/cloud-messaging) para enviar notificaciones push a la aplicación de billetera digital.

El siguiente diagrama ilustra los canales de comunicación compatibles con NFC Wallet:

<figure><img src="https://3188068289-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1qH2BUpGoh4ljBdsqlZq%2Fuploads%2FnTjgGedi0CtxEjMfQPRz%2FSDK%20Communication%20channels.png?alt=media&amp;token=be098f54-e01d-4370-81ff-ab1a2177955f" alt=""><figcaption><p>Resumen de canales de comunicación</p></figcaption></figure>

> Si no se puede usar Firebase Cloud Messaging, el backend de la billetera digital debe admitir la API de Thales Wallet Push Server.


---

# 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/nfc-wallet/es/general/interfaces.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.