# Events

**Events** are system notifications that require your attention or action.

{% hint style="info" %}
Some actions can only be performed by users with the *Owner* and *Admin* roles.
{% endhint %}

## Event list

On this page, you can find a list of all events logged in the system. The number of new notifications is displayed on the counter near the **Events** menu item.

The following information is provided about each event:

**ID**

The unique system identifier of an event.

***

**Created**

The date and time when an event was logged in the system.

***

**Updated**

The date and time when an event was last updated.

***

**Type**

The event type. Refer to the **Event types** section below for details.

***

**Operation ID**

For events related to deposits or payouts, this is the unique operation identifier in the system. This is a link to deposit or payout details.

***

**Action**

The action button(s) applicable for this event type.

## Event types

In the table below, you can find descriptions of all system events.

<table><thead><tr><th width="209">Event type</th><th width="119">Wallet type</th><th>Description</th><th>Actions</th></tr></thead><tbody><tr><td>Callback</td><td><code>E</code>, <code>M</code></td><td>A <a data-footnote-ref href="#user-content-fn-1">callback</a> hasn’t been sent by the system due to some technical reasons.</td><td>Click the <strong>Resend</strong> button to send the callback.</td></tr><tr><td>Payout approve</td><td><code>E</code>, <code>M</code></td><td>A payout was created by a user with the <em>Withdrawals with approval</em> role.</td><td>Approve or cancel the payout.</td></tr><tr><td>Overpaid deposit</td><td><code>M</code></td><td>A deposit with the indicated amount got overpaid.</td><td>Refer to <a href="/pages/lA11nJMITiN6Zr9tEJzM">Unresolved deposits</a> for details.</td></tr><tr><td>Transfer to expired deposit</td><td><code>M</code></td><td>Funds were sent to an expired deposit.</td><td>Refer to <a href="/pages/lA11nJMITiN6Zr9tEJzM">Unresolved deposits</a> for details.</td></tr><tr><td>Insufficient funds on parent wallet</td><td><code>E</code></td><td>Not enough funds on a <a data-footnote-ref href="#user-content-fn-2">parent wallet</a> for accepting tokens to your wallet address.</td><td>Top up the parent wallet and then click the <strong>Retry</strong> button. Refer to <a href="/pages/quynKDFYTVR7Ul8XjAU8">Unconfirmed transfers</a> for details.</td></tr><tr><td>Insufficient funds for payment for a custom token</td><td><code>E</code></td><td>Not enough funds on a <a data-footnote-ref href="#user-content-fn-2">parent wallet</a> to pay a monthly fee for your <a data-footnote-ref href="#user-content-fn-3">custom token</a>.</td><td>Top up the parent wallet and then click the <strong>Retry</strong> button.</td></tr><tr><td>Transfer amount is less than required minimum</td><td><code>E</code>, <code>M</code></td><td>A transfer received with the amount less than <strong>Minimum transfer amount</strong> set for the wallet.</td><td>Refer to <a href="/pages/YAcK2QyPeqVfodnsvSVh">Canceled transfers</a> for details.</td></tr><tr><td>Duplicated blockchain deposit</td><td><code>E</code>, <code>M</code></td><td>A deposit was created in a specific currency and subsequently paid in a different currency, resulting in its duplication on another blockchain. This duplicated deposit lacks the Tracking ID and Callback URL from the original deposit.</td><td>Click the <strong>Edit data</strong> button to add the Tracking ID and Callback URL to the duplicated deposit.</td></tr></tbody></table>

[^1]: A notification sent to a user’s callback URL when a new transaction occurs on the blockchain.

    For more information, see [Key terms](/references/key-terms.md#callback)

[^2]: Enterprise wallet to which a token wallet is linked.

    For more details, see [Key terms](/references/key-terms.md#parent-wallet)

[^3]: A user-created token in certain blockchains.

    For more details, see [Key terms](/references/key-terms.md#custom-token)


---

# 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.coinsbuy.com/user-guide/wallet-management/events.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.