> For the complete documentation index, see [llms.txt](https://docs.a-pay.one/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.a-pay.one/faq/a-pay-merchant-portal/interface/settings/my-projects.md).

# My projects

On this page, you will see cards containing key information about your projects and payment systems.

<details>

<summary>Table columns</summary>

* Name – the project’s title.
* Type – `test` (test project) or `prod` (production project).
* Payment systems – list and details of payment systems connected to the project.
* Technical details – these fields contain a gear icon. Clicking it opens the settings. (See details below.)

</details>

### Available Actions

<details>

<summary>Viewing Payment Methods for Projects</summary>

1. Click on the eye icon in the *Payment systems* column.
2. A table will open with detailed information about the payment systems connected to the project.

Table contains:

* a window for searching a payment system by name. (upper right corner)![](/files/MhZHJuTjokIt4tFN78Fh)
* detailed information about payment systems:
  * **Payment system —** the payment system's name.
  * **Currency —** payment system currency.
  * **Comission percent deposit —** commission amount as a percentage.
  * **Comission fix deposit —** comission amount as a fixed sum.
  * **Comission percent withdrawal —** commission amount as a percentage.
  * **Comission fix withdrawal —** comission amount as a fixed sum.
  * **Comission percent settlement —** commission amount as a percentage.
  * **Comission fix settlement —** comission amount as a fixed sum.
  * **Enabled —** current status of payment system (enabled\disabled)

</details>

<details>

<summary>Generating Project Credentials</summary>

1. Click on the gear icon in the *Technical details* column.\
   ![](/files/iTAgUCj7KoadtCKEzrR0)
2. In the opened window:
   * Left side: current keys.
   * Right side: webhooks.
3. To generate a new key (API key/Access key/Private key), click *Generate new key* next to it and confirm.\
   \
   ![](/files/DBGMhp054X0qj6VVnGYm)

</details>

<details>

<summary><strong>Viewing Webhooks details</strong></summary>

1. Click on the gear icon in the *Technical details* column.\
   ![](/files/iTAgUCj7KoadtCKEzrR0)
2. In the opened window:
   * Left side: current keys.
   * Right side: **webhooks**.
3. You can explore:

   * **ID** (internal unique subproject identifier)
   * **Subproject**
   * **Webhook Deposit Url**
   * **Webhook Withdrawal Url**

</details>


---

# 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.a-pay.one/faq/a-pay-merchant-portal/interface/settings/my-projects.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.
