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

# Onboard a merchant

Use these APIs to onboard a merchant for Visa and Mastercard TSPs.

{% hint style="warning" %}
Important

* Merchant onboarding is one-time. You can’t update or delete a merchant after onboarding.
* For Visa, wait 5–7 days after a successful onboarding notification before starting tokenization. Visa applies an internal validation window.
  {% endhint %}

## 1. Merchant creation flow

<figure><img src="/files/si25upp6edeycAMoM9yD" alt=""><figcaption><p>Merchant creation flow</p></figcaption></figure>

<table><thead><tr><th width="100">Step</th><th>Description</th></tr></thead><tbody><tr><td>1</td><td>The merchant aggregator/PSP sends a merchant creation request with merchant name.</td></tr><tr><td>2</td><td>Thales backend creates the merchant in its database and returns an unique identifier.</td></tr></tbody></table>

### API

* API reference: [Create merchant](/merchant-tokenization/backend-integration/apis/server-api/merchant-onboarding.md#post-merchants)

## 2. Merchant registration flow

<figure><img src="/files/3C5zgFcNZXuqvwHSTJgv" alt=""><figcaption><p>Payment network merchant registration flow</p></figcaption></figure>

<table><thead><tr><th width="100">Step</th><th>Description</th></tr></thead><tbody><tr><td>1</td><td>The merchant aggregator/PSP sends a registration request per payment network. The request includes a <code>merchantId</code>, a <code>x-correlation-id</code>, and specific payment network parameters.</td></tr><tr><td>2</td><td>Thales backend acknowledges the request.</td></tr><tr><td>3</td><td>Thales backend registers the merchant with the payment network.</td></tr><tr><td>4</td><td>Thales backend notifies the PSP with the result and the Token Requestor Identifier (TRID).</td></tr></tbody></table>

### API

* API reference: [Update merchant Mastercard (S-COF)](/merchant-tokenization/backend-integration/apis/server-api/merchant-onboarding.md#put-merchants-merchantid-mastercard-secure-cof)
* API reference: [Update merchant Visa](/merchant-tokenization/backend-integration/apis/server-api/merchant-onboarding.md#put-merchants-merchantid-visa)
* Callback reference: [Notify merchant update](/merchant-tokenization/backend-integration/apis/client-api/merchant-onboarding.md)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.payments.thalescloud.io/merchant-tokenization/network-tokenization/implement-network-tokenization/onboard-a-merchant.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.