# Merchant Setup

{% hint style="info" %}
**Merchant** is an entity that represents a **store** in our system, it can be your **online goods shop, trading platform, exchange, etc.**&#x20;

To start using merchants, you have to create a [personal account](broken://pages/N1laBDZWOBPFDODYor2S) with 0xpay first.
{% endhint %}

In this section we provide details regarding the available Merchant features, operational workflow and service fees, alongside with info on how to set up your Merchant for integration on your website.

## Creating a Merchant

To start integration, you have to create a merchant at the [merchants' page](https://my.0xpay.app/merchants).

<div align="center"><img src="/files/Kigbf9mBgQZR1SC8bp5I" alt="Merchant creation form"></div>

> Let's describe the fields above:
>
> * **Merchant name** – description field, it can be the shop's name or anything that fits you.
> * **Company name** – regulatory field, this field has to match your company name.
> * **Domain** – used to verify your website, **cannot be changed later**.&#x20;
> * **Email for notifications** - used to notify you about your merchant's activities: replenishments, withdrawal transactions.

{% hint style="warning" %}
The **Domain** field cannot be changed later, so pay attention when entering your website info into it. Also, this domain will be used in [webhook](/public-api/notifications.md) notifiers.
{% endhint %}

## Setting up Merchant

Prior to the integration, you should configure your merchant properly. You can access merchant settings through your [merchant list](https://my.0xpay.app/merchants).

![Settings button on merchants list](/files/jdSCp6BZD66Kw4DodtYn)

## Getting API Key <a href="#api-keys" id="api-keys"></a>

Sending requests to 0xpay API through a merchant requires authorisation with API keys. They are used for two purposes:

* Sending requests to 0xpay API.
* Verifying server-side notifications.

{% hint style="danger" %}
**DO NOT SHARE YOUR API KEYS!** API key grant access to manage funds within your 0xpay Merchant, hence the person with keys may transfer funds to any external addresses.
{% endhint %}

![API Keys tab](/files/S625WJhu80suJnTlbFNe)

> Let's detail the fields above:
>
> * **Merchant ID** – your merchant identifier, which is used in [Merchant API](/public-api/authorization.md) for identification.
> * **Private key** – used for [authorization](broken://pages/fh4Xg0HSUcNld2IRUrKB) in [Merchant API](/public-api/authorization.md).&#x20;

## Receiving notifications

{% hint style="warning" %}
You won't receive any callback notifications until the **Notifications URL** field is set.
{% endhint %}

![Notifications tab](/files/GRaLr5jGR3uTi5DTV57r)

You have to specify the **Notifications URL** to start receiving notifications about your incoming and outgoing payments.


---

# Agent Instructions: 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.0xpay.app/integration-cookbook/getting-started/merchant-setup.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.
