> 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="https://1873847743-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>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="https://1873847743-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>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 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/network-tokenization/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.