# How to edit a merchant

You should click on the merchant editing button. After that, a form for merchant editing will open. You can also click on the Settings page to open a form for merchant editing.

Here's a merchant editing form:

![](/files/tVFnnzJYssIJKeIFnNWD)

**Choose Merchant currency** - list for selecting currencies supported by the merchant. If the user has chosen to support a currency that was not previously supported, then clicking on the "Submit" button will create a merchant's default wallet for this currency. For example, when creating a wallet, the user did not select support for ETH, while editing he chose, then in this case, the default wallet of the ETH merchant will be created.

In addition, if you select support for a token, then support for the currency of this token is automatically selected. For example, a user wants to select support for the BUSD token, along with this, support for his currency BNB is selected.

**Miner Fee pays** - the choice of who pays the Miner Fee for sending funds from the client's wallet to the merchant's wallet.

**Merchant Fee** - field for Merchant Fee inputting.

Text field that displays the % of System Fee for each transaction.

**Fee's documentation** - link that opens detailed information about fees.

**Generate new API keys -** get merchant's private and public key. Not available for individual accounts.

**Merchant Name** - merchant name editing.

**Merchant's Network** - choice of merchant's network.

**Company Website** (not used yet)**.**

**Company name** (not used yet)**.**

**Country** (not used yet)**.**

**City** (not used yet)**.**

**Address** (not used yet)**.**

**Public email for merchant's clients** (not used yet)**.**

**Email For Notifications** (not used yet)**.**

**Callback Url -** field for entering a route where callbacks will come after the transaction is confirmed.


---

# 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://cpay-2.gitbook.io/cpay-1/guides/merchants/how-to-edit-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.