> For the complete documentation index, see [llms.txt](https://docs.velafi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.velafi.com/api-reference/merchant/create-merchant.md).

# Create Merchant

Create a legal individual or business entity (Merchant) to operate under Velafi's compliance framework.

* Submit your detailed merchant information to initiate the KYC/KYB compliance verification process.
* Upon successful verification, the platform will assign a unique Merchant ID (MID) to you or your client.

**Endpoint Information**

* **Request Header**: `X-BH-TOKEN: ******`
* **Request Header**: `Content-Type: application/json`
* **Request Method**: `POST`
* **Request Path**: `/v2/merchants`
* **Authorization Required**: Yes

**Request Parameters**

The request body should include the following fields:**For New Merchant (KYC/KYB)**

```json
{
    "merchantName": "Tom",                // (required, string: Merchant Name (Unique))
    "email": "tom@gmail.com",            // (required, string: Email (Unique))
    "merchantType": "INDIVIDUAL",        // (required, string: Merchant Type [INDIVIDUAL, BUSINESS])
    "callbackUrl": "https://localhost",  // (required, string: URL for KYC/KYB completion callback)
    "languageCode": "en",                // (optional, string: Interface language (en(default)/es/pt/zh))
    "flow": "PROFESSIONALS",             // (optional, KYC flow for INDIVIDUAL only: [PROFESSIONALS(default), CONSUMERS])
    "remark": "test",                    // (optional, string: Remark)
    "industryType": "",                  // (required, enum: payment_psp/fintech/lending/fx_or_otc/e-commerce/gaming_or_entertainment/crypto_or_web3/supply_chain/import_or_export/payroll_or_hr/media_or_advertising/remittance_or_money_transfer/treasury_or_asset_management/wholesale_or_b2b_marketplace/logistics_and_courier/digital_content_or_streaming/travel_or_booking/online_marketplace/investment_and_crowdfunding/real_estate_and_proptech/accounting_or_billing/freelancer_platform/saas_or_api/online_education/outsourcing_agency/other)
    "industryTypeRemark": ""             // (optional, required if industryType = "other")
}

```

**For Unverified Merchant**

```json
{
    "merchantId": 15126673, //(required, number: id of the merchant)
    "callbackUrl": "https://localhost", //(required, string: URL for KYC/KYB completion callback)
    "languageCode": "en" //(optional, string: Interface language (en(default)/es/pt/zh))
}
```

**Response Structure**

```json
{
    "code": 200,
    "msg": "SUCCESS",
    "data": {
        "merchantId": 15126673, //(number: id of the merchant)
        "kycLink": "https://www.velafi.com/verify?velafi_token=abc123" //(string: Link for conducting KYC/KYB verification)
    }
}
```


---

# 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.velafi.com/api-reference/merchant/create-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.