# Callback

The Permanent Address Callback is triggered when a transaction to a permanent address receives 12 confirmations on the blockchain. This ensures that the transaction is securely confirmed.

**Transaction Found with 12 Confirmations**

```json
{
    "statusCode": 200,
    "merchant_id": "a56e0-0a10c-73015-9f330",
    "hash": "o3OsLGIMX3KCRGO4plWNhBJqRAiLDU2/L5i+ymIlcliBVWJ/ca6OSmdTb7UAylXQgfpjXZT5ZUC6faYS2aNaQQ==",
    "data": {
        "symbol": "USDT",
        "from": "0x1111111111111111111111111111111111111111",
        "address": "0x0E595b185E323Fa5019E8D73B2F7A3D0f089b582",
        "block": 7677026,
        "txid": "0x73cedead30e3949d0867986f7049923417dd42ca32872aaece85c41703927773",
        "confirmation": 12,
        "balance": 124.6261,
        "timestamp": 1586350781,
        "risk_level": 1
    }
}
```

\
For the "Permanent Address Callback" section of your API documentation, it's important to clearly describe how the callback mechanism works, especially regarding transaction confirmations for permanent addresses. Here's how you can structure this section:

***

#### Permanent Address Callback

**Brief Description**

The Permanent Address Callback is triggered when a transaction to a permanent address receives 12 confirmations on the blockchain. This ensures that the transaction is securely confirmed.

**Transaction Found with 12 Confirmations**

```json
{
    "statusCode": 200,
    "merchant_id": "a56e0-0a10c-73015-9f330",
    "hash": "o3OsLGIMX3KCRGO4plWNhBJqRAiLDU2/L5i+ymIlcliBVWJ/ca6OSmdTb7UAylXQgfpjXZT5ZUC6faYS2aNaQQ==",
    "data": {
        "symbol": "USDT",
        "from": "0x1111111111111111111111111111111111111111",
        "address": "0x0E595b185E323Fa5019E8D73B2F7A3D0f089b582",
        "block": 7677026,
        "txid": "0x73cedead30e3949d0867986f7049923417dd42ca32872aaece85c41703927773",
        "confirmation": 12,
        "balance": 124.6261,
        "timestamp": 1586350781,
        "risk_level": 1
    }
}
```

**Callback Parameters**

<table><thead><tr><th width="176.33333333333331">Parameter Name</th><th width="142">Type</th><th>Explanation</th></tr></thead><tbody><tr><td>symbol</td><td>string</td><td>Type of token (e.g., 'USDT', 'USDC'', 'tron-usdt', 'tron-usdc').</td></tr><tr><td>from</td><td>string</td><td>The source address from which the tokens are sent.</td></tr><tr><td>address</td><td>string</td><td>The recipient's permanent address.</td></tr><tr><td>block</td><td>string</td><td>The block number on the blockchain where the transaction was included.</td></tr><tr><td>txid</td><td>string</td><td>Blockchain transaction identifier.</td></tr><tr><td>confirmation</td><td>number</td><td>The number of confirmations the transaction has received.</td></tr><tr><td>balance</td><td>decimal</td><td>The amount of tokens received.</td></tr><tr><td>timestamp</td><td>number</td><td>Timestamp of when the transaction was processed.</td></tr><tr><td>risk_level</td><td>number</td><td>0, pending 1 low, 2 high, 3 medium, 4 severe</td></tr></tbody></table>

<br>


---

# 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://hyperhashing.gitbook.io/hyperhashing-api/permanent-address-v1/callback.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.