> 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/click-to-pay-merchants/use-cases/onboard-a-merchant.md).

# Onboard a merchant

Merchant aggregators, such as PSPs, can use an API to onboard merchants for Click to Pay.

{% hint style="info" %}
Some payment networks do not provide an onboarding API. You may need a manual onboarding step. Contact your Thales delivery team.
{% endhint %}

## 1. Create a merchant

<figure><img src="/files/aGz5SFREHX3YMk6WPIt1" 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 the merchant name.</td></tr><tr><td>2</td><td>Thales backend creates the merchant and returns a unique identifier (<code>merchantId</code>).</td></tr></tbody></table>

## 2. Register the merchant for Click to Pay

<figure><img src="/files/R9TJDgna3BEIflzk1Qr2" alt=""><figcaption><p>Merchant registration flow in Click to Pay.</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 request to onboard the merchant for Click to Pay.<br><br>The request includes:<br>- merchantId<br>- correlationId<br><br>It also includes payment-network-required parameters, such as:<br>- Supported card brands<br>- Merchant country code<br>- Merchant URI<br>- Acquirer ICA<br>- Acquirer merchant ID</td></tr><tr><td>2</td><td>Thales backend acknowledges the request.</td></tr><tr><td>3</td><td>Thales backend registers the merchant for Click to Pay.</td></tr><tr><td>4</td><td>Thales backend sends a notification to the merchant aggregator/PSP with the onboarding result.</td></tr></tbody></table>


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.payments.thalescloud.io/click-to-pay-merchants/use-cases/onboard-a-merchant.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.