# Deposit
The Deposit tab contains a table with all deposit transactions for the selected project.
Table columns
Each row contains the following information:
* **Project** — the project within which the transaction was carried out.
* **Payment system** — the payment system that was used for the transaction.
* **Currency** — transaction currency.
* **Amount** — transaction amount before commission is applied.
* **Amount after commission** — transaction amount after commission deduction (final amount)
* **Custom user id** — internal unique user identifier.
* **Custom transaction id** — internal unique transaction identifier.
* **Status** — current transaction status.
* **Created at** — date and time of transaction creation.
* **Updated at** — date and time of transaction last update.
* **Activated at** — date and time of deposit activation.
* **Order id** — internal unique order identifier.
* **Data User** — data received in the request.
* **Transaction ID** — unique transaction identifier.
* **Id wallet** — internal unique wallet identifier.
* **Subproject** —the subproject within which the transaction was carried out.
* **Actions** — available actions (e.g., copy row).
> To switch between projects, click your username in the top-right corner, then select the desired project from the dropdown list.
Transaction Statuses and Processing Rules
* **Success** – final status, transaction completed successfully
* **Rejected** – final status, transaction was declined
* Rejected fraud - final status, commited fraud
* Rejected refund - final status, declined refund
* **Failed** – final status, transaction was not completed
* **Pending** – *not* a final status, transaction is still being processed
**Processing rules:**
* A callback is sent only when the transaction reaches a final status: *Success, Rejected (including fraud and refund), Failed*.
* A transaction may remain in Pending for up to 24 hours.
* If payment is not received within this time, the transaction will automatically switch to Failed 24 hours after creation.
### Available actions
**View and search deposits**\
Browse all deposit orders in the project or find specific ones by applying filters.
**Create a lost transaction request**\
You can create a *Lost transaction* request directly from this table in two ways:
* *Option 1:*
1. Select the required order (no more than one) by checking the box in the left column.
2. A **Send to Lost transactions button** will appear above the table. Click it.\
3. Fill in the form and click **Create issue**.\
4. The order will appear in the *Lost transaction* table.
* *Option 2:*
1. In the row with the required order, click the ⋮ (three vertical dots) icon in the Actions column.
2. From the menu, select **Send to Lost transactions**.\
3. Fill in the form and click **Create issue**.
4. The order will appear in the *Lost transaction* table.
**Export data**\
Data export to `.xlsx` format is available in this table.\
Follow the [standard export instructions](https://app.gitbook.com/o/LNbZs3dNMDs1xm16Y9hk/s/4GiUD4nehhLIWqxaI99h/dashboard/interface/transactions#export-data).
---
# 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.a-pay.one/faq/a-pay-merchant-portal/interface/transactions/deposit.md?ask=
```
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.