> 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/merchant-tokenization/es/tokenizacion-de-red/implement-network-tokenization/onboard-a-merchant.md).

# Incorporar a un comercio

Utilice estas API para incorporar a un comerciante en los TSP de Visa y Mastercard.

{% hint style="warning" %}
Importante

* La incorporación del comerciante es única. No puede actualizar ni eliminar un comerciante después de la incorporación.
* Para Visa, espere de 5 a 7 días después de una notificación de incorporación exitosa antes de comenzar la tokenización. Visa aplica una ventana de validación interna.
  {% endhint %}

## 1. Flujo de creación de comerciante

<figure><img src="https://2211683957-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9XBN1F9dv7Dl1ggilGWC%2Fuploads%2F7eS7zAW98Qxg7NEJ8957%2FFlow%20-%20Merchant%20creation%20flow.svg?alt=media&amp;token=6f98d87a-aa57-4c27-9959-8f72a4681733" alt=""><figcaption><p>Flujo de creación de comerciante</p></figcaption></figure>

<table><thead><tr><th width="100">Paso</th><th>Descripción</th></tr></thead><tbody><tr><td>1</td><td>El agregador/PSP del comerciante envía una solicitud de creación de comerciante con el nombre del comerciante.</td></tr><tr><td>2</td><td>El backend de Thales crea el comerciante en su base de datos y devuelve un identificador único.</td></tr></tbody></table>

### API

* Referencia de la API: [Crear comerciante](broken://pages/a5e42a1537687e84190e4e4a73a0b8c7885fe37e#post-merchants)

## 2. Flujo de registro de comerciante

<figure><img src="https://2211683957-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9XBN1F9dv7Dl1ggilGWC%2Fuploads%2FDJJIsVK6Pd1vMF0aEzZy%2FFlow%20-%20Register%20the%20merchant%20for%20Click%20to%20Pay.svg?alt=media&amp;token=392a95be-0d8d-4fd3-b417-771651f1f183" alt=""><figcaption><p>Flujo de registro de comerciante en la red de pago</p></figcaption></figure>

<table><thead><tr><th width="100">Paso</th><th>Descripción</th></tr></thead><tbody><tr><td>1</td><td>El agregador/PSP del comerciante envía una solicitud de registro por cada red de pago. La solicitud incluye un <code>merchantId</code>, un <code>x-correlation-id</code>, y parámetros específicos de la red de pago.</td></tr><tr><td>2</td><td>El backend de Thales reconoce la solicitud.</td></tr><tr><td>3</td><td>El backend de Thales registra al comerciante en la red de pago.</td></tr><tr><td>4</td><td>El backend de Thales notifica al PSP con el resultado y el Identificador de Solicitante de Token (TRID).</td></tr></tbody></table>

### API

* Referencia de la API: [Actualizar comerciante Mastercard (S-COF)](broken://pages/a5e42a1537687e84190e4e4a73a0b8c7885fe37e#put-merchants-merchantid-mastercard-secure-cof)
* Referencia de la API: [Actualizar comerciante Visa](broken://pages/a5e42a1537687e84190e4e4a73a0b8c7885fe37e#put-merchants-merchantid-visa)
* Referencia de callback: [Notificar actualización de comerciante](broken://pages/e44c6d33ae29e47e7a2a21c4999f841b9bad81a1)


---

# 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/merchant-tokenization/es/tokenizacion-de-red/implement-network-tokenization/onboard-a-merchant.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.